Factions and lore

Factions

Factions live at factions/<folder>/faction.json and may represent institutions, families, movements or informal alliances.

{
  "id": "observatory-trust",
  "name": "Blackwater Observatory Trust",
  "summary": "The body that controls access to the observatory.",
  "description": "Publicly charitable and privately divided.",
  "values": ["scientific prestige", "secrecy"],
  "structure": "A board chaired by the town magistrate.",
  "start": {
    "public_state": "Preparing its centenary exhibition.",
    "inner_state": "Trying to suppress records of the 1891 incident.",
    "goals": [{"id": "contain-records", "name": "Contain the records", "plan": "Recover missing files."}]
  }
}

Characters may belong to zero or more factions. Membership has its own role, rank and status. Faction-to-faction relationships are directional, like character relationships. Goals belong to the faction rather than being duplicated across members.

Lore

Lore entries hold canonical setting facts that are not better represented as an entity or event. Each entry has a stable key, title, kind, summary, body, subjects, related entries and optional sources.

Characters do not automatically know canonical lore, unless an entry says so. An entry's scope is listed (the default in a world's own files): a knowledge.lore edge, or a name in the entry's known_by (character ids, names or aliases of the world), grants access to it. An entry whose scope is everyone is common knowledge that every character can recall; known_by is then not allowed. The GM may search all lore; character recall is restricted to the entries a character knows. Entries brought in from a lorebook are everyone unless they say otherwise.

Use separate entries for facts that may be learned independently. Link their subjects to characters, locations, items or factions so retrieval can find relevant material.