Write lore the AI can wake up cleanly.
Use one Canon Anchor for one stable fact. Keep it short, named and easy to trigger.
Quick rules
One card, one job
Do not bury a whole setting bible in one entry. Split people, places, ranks, rules and secrets into separate anchors.
Use specific keywords
Names, surnames, factions, ranks, places, objects and unique phrases work better than generic words.
Write as fact
Use clear present-tense canon. Avoid instructions like "remember that" or long prose.
Stay compact
Free entries allow 300 characters, Plus 350 and Pro 400. Older longer cards still load, but new cards should stay lean.
Location
Use for places with rules, ownership or atmosphere
Template
Lore Type: Location
Lore Name: [Place name]
Trigger Keywords: [place], [district], [owner], [room], [local nickname]
Canon Entry: [Place] is [what it is], controlled by [person/group]. It matters because [rule, secret, danger or function]. [One sensory or social detail that affects scenes.]Example
Lore Type: Location
Lore Name: Velvet Lounge
Trigger Keywords: Velvet Lounge, club, Junpei Kuroda, Yokohama nightlife
Canon Entry: Velvet Lounge is Junpei Kuroda's private club and information hub. Staff report unusual guests to him first. Public charm is expected downstairs; serious deals happen in the locked upper rooms.Faction, Family or Group
Use for hierarchy, loyalty and power structure
Template
Lore Type: Faction
Lore Name: [Group name]
Trigger Keywords: [group], [leader], [rank], [base], [rival group]
Canon Entry: [Group] is [identity/function]. [Leader] controls [domain]. [Named ranks or members] handle [duties]. Their public rule is [visible code]; their private pressure is [secret/conflict].Example
Lore Type: Faction
Lore Name: Yamada-gumi Inner Circle
Trigger Keywords: Yamada-gumi, inner circle, Kai Sato, Axel Takahashi, shateigashira
Canon Entry: The Yamada-gumi inner circle answers to Hiro Yamada. Kai Sato and Axel Takahashi are shateigashira and trusted lieutenants, not outsiders. They enforce Hiro's orders and protect his private interests.Character Canon Anchor
Use for character-specific facts not already clear on the sheet
Template
Lore Type: Custom or Character
Lore Name: [Character] - [Fact]
Trigger Keywords: [full name], [surname], [alias], [linked person/place]
Canon Entry: [Character] is/has/knows [stable fact]. This affects scenes by [behaviour, limitation, fear, duty or relationship]. They should not be written as [common wrong version].Example
Lore Type: Custom
Lore Name: Junpei Kuroda - Role
Trigger Keywords: Junpei Kuroda, Kuroda, Velvet Lounge, club manager
Canon Entry: Junpei Kuroda manages Velvet Lounge and gathers information through its staff, clients and private rooms. He is not Yamada-gumi leadership and should not be written as Hiro's internal lieutenant.Relationship or Hierarchy
Use for ranks, family ties, alliances and rivalries
Template
Lore Type: Faction / Family / Group
Lore Name: [Relationship map name]
Trigger Keywords: [family/group], [rank], [person A], [person B], [relationship term]
Canon Entry: [Person A] is [role/relationship] to [Person B]. [Person B] is [role/relationship] to [Person C]. This hierarchy means [who can command, protect, overrule or betray whom].Example
Lore Type: Faction
Lore Name: Yamada Command Chain
Trigger Keywords: Yamada command, oyabun, wakagashira, shateigashira, Hiro, Kai, Axel
Canon Entry: Hiro Yamada is the Yamada-gumi heir and command center. Kai Sato and Axel Takahashi serve as shateigashira under Hiro. Orders involving them should treat them as Hiro's trusted lieutenants.Item or Object
Use for objects that change choices or reveal information
Template
Lore Type: Item
Lore Name: [Object name]
Trigger Keywords: [object], [owner], [location], [symbol], [secret]
Canon Entry: [Object] belongs to [person/group] and is used for [purpose]. It reveals [fact] only if [condition]. It should not be treated as [wrong ability/ownership].Example
Lore Type: Item
Lore Name: Sealed Registry Ledger
Trigger Keywords: registry ledger, seal, council record, Yamada archive
Canon Entry: The sealed registry ledger records formal Yamada household decisions. Only Soichiro's office and authorised witnesses can alter it. A missing seal means the decision is disputed, not erased.Rule, Tradition or Law
Use for world rules the AI must not improvise around
Template
Lore Type: Custom
Lore Name: [Rule name]
Trigger Keywords: [rule], [ceremony], [rank], [place], [phrase used in scenes]
Canon Entry: In [setting/group], [rule] works like this: [clear rule]. It applies when [condition]. Breaking it causes [consequence]. It does not mean [common misunderstanding].Example
Lore Type: Custom
Lore Name: Witness Seal Rule
Trigger Keywords: witness seal, registry, council, formal claim
Canon Entry: A formal household claim requires named witnesses and a valid seal. If a required witness is absent, the record can be challenged. Outsiders may observe but cannot replace internal witnesses.Secret or Reveal
Use for hidden truths and who knows them
Template
Lore Type: Custom
Lore Name: [Secret name]
Trigger Keywords: [secret], [evidence], [knower], [victim], [place/object]
Canon Entry: [Truth] is true, but only [characters/groups] know it at the start. [Evidence] can expose it. Characters without a knowledge path should not act as if they know.Example
Lore Type: Custom
Lore Name: Kuroda Photo Leverage
Trigger Keywords: photographs, Kuroda leverage, compromising images, Junpei, Soichiro
Canon Entry: The compromising photographs are leverage against Kelly and Hiro. Soichiro and Junpei know they exist. Characters should not mention the photos unless they witnessed them or were told by a credible source.Event Card
Use for short story directives, not scripted scenes
Template
Lore Type: Event
Lore Name: [Event name]
Repeat: One-off or Recurring
Lead-up: Off or On
Aftermath: Off or On
Event Timestamp: [optional exact or approximate time]
Lead-up Starts: [only if Lead-up is On]
Lead-up Directive: [brief preparation, pressure or foreshadowing]
Trigger: [when this becomes possible]
Directive: [what the AI should make true in the scene]
End: [what resolves, cancels or changes the event]
Aftermath Directive: [only if Aftermath is On]One-off example
Lore Type: Event
Lore Name: Registry Witness Deadline
Repeat: One-off
Lead-up: On
Aftermath: On
Event Timestamp: Wednesday morning
Lead-up Starts: Morning of
Lead-up Directive: Household staff prepare registry documents and observers gather. Do not begin the signing yet.
Trigger: The household prepares the registry signing and Hiro has not secured his witnesses.
Directive: Soichiro pressures the council to proceed without Hiro's verification.
End: Hiro produces valid witnesses or the signing is formally delayed.
Aftermath Directive: The delay increases pressure on Hiro and makes the council question his control.Recurring example
Lore Type: Event
Lore Name: Nightly Patrol Sweep
Repeat: Recurring
Lead-up: Off
Aftermath: Off
Event Timestamp: Every night after curfew
Trigger: The player moves through restricted corridors after curfew.
Directive: Patrols tighten, guards check rooms and unlocked routes become risky.
End: The player reaches a safe room, curfew ends, or the patrol passes.Common mistakes
Too broad
A card named "All clan politics" will blur. Split it into command chain, rival faction, witness rule and current dispute.
Weak triggers
Words like family, city, secret or danger are too generic. Use names, ranks, aliases and exact places.
Mixed time
Stable canon belongs in Canon Anchors. Future developments belong in Event Cards. Past chat outcomes belong in Memory Cards.
Character sheet duplicate
If it is core personality, put it on the character. Use anchors for relationships, roles, rules and facts that need retrieval.