Lorebook — Campaign Threads Tracker (GM Utility) (Gold 2.0)

1. #1THREADS: The Continuity Rule (Nothing Disappears)selective

   Keys: THREADS TRACKER, LONG TERM TRACKING, CAMPAIGN TRACKER, CONTINUITY · Secondary: blowback, clocks, threads, continuity bible

   CONTINUITY RULE Every mission leaves something behind.

   If you can't remember it, remember this:

   • Who is hunting you?
   • What did you burn?
   • What story is the public being told?

   This tracker turns answers into fuel for the next episode.

   CONTINUITY INTEGRATION

   This tracker implements the CONTINUITY system from Phase 1:

   • BODY COUNT: named NPCs killed
   • DEBTS: who you owe, what they want
   • SCARS: lasting injuries or psychological marks
   • BURNED: covers, contacts, assets lost
   • ALLIES: people who survived because of you
   • ENEMIES: people hunting you specifically

   This tracker expands it with:

   • Active Threads (narrative hooks)
   • Global Clocks (pressure clocks)
   • Enemy/Rival Sheet (named consequences)
   • Faction Relationships (trust/hostility)
   • MacGuffin/Program Inventory (where power is)
   • Episode Log (history)

   HANDLER TRUST THREADS

   • Handler relationship changes should be tracked
   • Handler trust shifts create narrative threads
   • Handler betrayal becomes ENEMY
   • Handler support becomes ALLY

   MORAL TRACK THREADS

   • Major moral decisions should be tracked
   • Moral deterioration creates thread: "Compromised for [reason]"
   • Moral recovery creates thread: "Redemption through [action]"

   INTIMACY THREADS

   • Intimate relationships create threads
   • Intimate partner becomes ALLY or ENEMY
   • Intimate partner threatened creates thread
   • Intimate partner betrayal becomes ENEMY thread
2. #2THREADS: Master Thread Board (Fill-In Template)selective

   Keys: TRACKER TEMPLATE, FILL IN TEMPLATE, MASTER THREAD BOARD, THREAD BOARD · Secondary: active threads, heat, hunt, oversight

   MASTER THREAD BOARD (TEMPLATE)

   ACTIVE THREADS (TOP 5)

   1. Thread Name: ____ Linked Faction: ____ Stakes: ____ Status: simmering / active / critical

   2. ---

   3. ---

   4. ---

   5. ---

   GLOBAL CLOCKS (KEEP 2–4)

   • HEAT (0/6): ____
   • HUNT (0/6): ____ (who is hunting)
   • OVERSIGHT (0/6): ____ (who is tightening)
   • MEDIA CYCLE (0/4): ____ (what story is forming)
   • RETALIATION (0/6): ____ (who will strike back)
   • EVIDENCE BURN (0/4): ____ (what proof is at risk)

   RULE If you track too many clocks, you track none. Keep the list short and brutal.

3. #3THREADS: Enemy & Rival Sheet (Named Consequences)selective

   Keys: NAMED ENEMIES, WHO HATES YOU, ENEMY SHEET, RIVALS · Secondary: nemesis, personal enemy

   ENEMY & RIVAL SHEET

   NEMESIS (1)

   • Name/Codename: ____
   • Faction: ____
   • Reason: ____ (what you did)
   • Signature Pressure: HEAT / INTEL / WOUNDS / STRESS / RELATIONSHIP
   • What they want: ____
   • What they will do next: ____

   RIVALS (2–4)

   • Rival: ____ | Hook: ____ | Next move: ____
   • Rival: ____ | Hook: ____ | Next move: ____

   INTIMACY-RELATED ENEMIES

   • Former intimate partner: ____ | Reason: ____ | Threat type: ____
   • Intimate partner's ally: ____ | Reason: ____ | Threat type: ____

   RULE A Nemesis should show up every 2–3 episodes, not every session.

4. #4THREADS: Burned Assets Log (Contacts, Safehouses, Gear, Vehicles)selective

   Keys: SAFEHOUSE LOG, CONTACTS LOG, VEHICLE BURN, GEAR LOSS LOG, BURNED ASSETS · Secondary: degraded, burned, compromised

   BURNED ASSETS LOG

   CONTACTS

   • Name: ____ | Status: safe / burned / dead / flipped | Why: ____

   SAFEHOUSES

   • Location: ____ | Type: official/personal/underground | Status: safe/compromised/burned

   GEAR/TAGS LOST

   • Tag: ____ | How lost: ____ | Replacement cost: favor/debt/oversight

   VEHICLES/ASSETS LOST

   • Asset: ____ | Status: degraded/compromised/burned | Thread created: ____

   INTIMATE CONNECTIONS

   • Partner: ____ | Status: active/severed/compromised | Thread: ____
   • Exposure risk: ____ | Leverage potential: ____

   RULE Every burned asset becomes a location hook or a revenge hook.

5. #5THREADS: Faction Relationship Grid (Simple)selective

   Keys: TRUST, FACTION RELATIONS, HOSTILITY, RELATIONSHIP GRID · Secondary: pmc, cobra, joe, rogue agency

   FACTION RELATION GRID (RATE -2 to +2)

   • G.I. Joe Command: ____
   • Cobra Core: ____
   • Crimson Guard: ____
   • Destro/Iron Grenadiers: ____
   • Rogue Agency Bloc: ____
   • PMCs: ____
   • Organized Crime: ____
   • Media/Investigators: ____
   • NGOs: ____
   • Local Authority (current region): ____

   HANDLER TRUST

   • Handler Name: ____ | Trust Level: 0-6 | Trend: improving/stable/declining
   • Last trust shift: ____ | Reason: ____

   NOTES

   • Who wants a deal? ____
   • Who wants blood? ____

   RULE One faction at +2 and one at -2 is a healthy campaign. Neutral everywhere is boring.

6. #6THREADS: MacGuffin / Program Inventory (Where the Power Is)selective

   Keys: PROOF ARTIFACTS, WHERE IS IT, PROGRAM INVENTORY, MACGUFFIN INVENTORY · Secondary: ownership, status, location

   MACGUFFIN / PROGRAM INVENTORY

   ITEM 1

   • Name: ____
   • Type: proof / prototype / key / sample / person
   • Current Owner: Joe / Cobra / third party / unknown
   • Current Location: ____
   • Why it matters: ____
   • What happens if revealed: ____ (Headlines)

   ITEM 2

   • ---

   ITEM 3

   • ---

   INTIMATE CONNECTIONS AS MACGUFFINS

   • Intimate Partner: ____ | Importance: ANCHOR/leverage/innocent
   • Threatened by: ____ | Protection status: ____

   RULE Keep 3–5 items active. Retire one whenever a new one appears.

7. #7THREADS: Episode Log (One Line Each)selective

   Keys: EPISODE LOG, MISSION HISTORY, WHAT HAPPENED, SESSION LOG · Secondary: cost, headline, codename

   EPISODE LOG (1 LINE EACH)

   • Ep #: Codename — Objective — Result — Cost — Headline

   Example

   • Ep 07: DOCK GHOST — retrieve ledger — success — burned safehouse — "Dockyard fire raises corruption questions"

   INTIMACY LOG (1 line per relationship change)

   • Relationship: ____ | Change: began/deepened/ended/betrayed | Thread: ____

   MORAL TRACK LOG (1 line per major shift)

   • Decision: ____ | Track shift: ____ | Reason: ____

   RULE If you can't summarize an episode in one line, you don't know what mattered.

8. #8THREADS: Advancement & Downtime Notes (Light, Optional)selective

   Keys: ADVANCEMENT NOTES, DOWNTIME NOTES, RECOVERY, UPGRADES · Secondary: safehouse, tags, stress recovery

   ADVANCEMENT & DOWNTIME NOTES (OPTIONAL)

   • New Signature Tag earned: ____
   • Safehouse upgrade: ____
   • Relationship improved/broken: ____
   • Scar gained/healed: ____

   MORAL TRACK STATUS

   • Current level: 0-3 (Idealistic/Worn/Cynical/Broken)
   • Last shift: ____ | Reason: ____

   HANDLER TRUST STATUS

   • Current level: 0-6
   • Last shift: ____ | Reason: ____

   INTIMACY STATUS

   • Active intimate relationship: ____ | Status: stable/compromised/exposed
   • ANCHOR status: ____ | Protection: ____

   RULE Upgrades should create new story obligations (debts, oversight attention, envy).

9. #9THREADS: Operator Quirk Tracking (Optional)selective

   Keys: TRIGGER TRACKING, ANCHOR TRACKING, VICE TRACKING, QUIRK TRACKING, SECRET TRACKING · Secondary: quirk exposure, quirk status

   OPERATOR QUIRK TRACKING (OPTIONAL)

   VICE

   • Type: ____ | Current status: controlled/active/spiraling
   • Last indulgence: ____ | Exposure risk: ____

   ANCHOR

   • Name: ____ | Relationship: ____ | Current status: safe/threatened/compromised
   • Protection level: ____ | Thread: ____

   TRIGGER

   • Type: ____ | Last activation: ____ | Current stability: stable/vulnerable/critical
   • Known by: ____ | Exploitation risk: ____

   SECRET

   • Type: ____ | Current status: protected/compromised/exposed
   • Known by: ____ | Leverage held by: ____

   RULE Quirks should be tracked because they are narrative pressure points.

Showing 9 of 9

1 file

• .jsonjson_lorebookrebuilt

  13.8 KBfirst seen Apr 16, 2026d8f92b29fe171ad1

  Download