COPS Epsilon Lore
This skill is the retrieval and continuity workflow for the Epsilon/Warden
campaign.
When to use
Use this skill when the request involves any of:
- Groupe Epsilon
- Carol "Warden" Murphy
- LAPD Blues
- roll call scenes
- scenario continuity across the COPS campaign
- writing new scenes, summaries, or analysis that should stay consistent with
the existing campaign arc
Source of truth
The living source of truth is Notion.
The fast local working canon is the lore pack in:
/Users/ludovicfleury/Documents/RPG/lore/README.md
/Users/ludovicfleury/Documents/RPG/lore/chronicle-memory.md
/Users/ludovicfleury/Documents/RPG/lore/scenario-cache.md
/Users/ludovicfleury/Documents/RPG/lore/epsilon-overview.md
/Users/ludovicfleury/Documents/RPG/lore/warden-arc.md
/Users/ludovicfleury/Documents/RPG/lore/lapd-blues-patterns.md
/Users/ludovicfleury/Documents/RPG/lore/scenario-timeline.md
/Users/ludovicfleury/Documents/RPG/lore/political-map.md
Read the local lore pack before doing substantial campaign work. Read Notion as
needed when the user asks for verification, new material, or deeper research.
For live Notion research, use:
/Users/ludovicfleury/.codex/skills/cops-epsilon-lore/references/notion-search-playbook.md
That playbook contains the current workspace map, database routing, query
patterns, and fallback search order.
Reading order
Default order:
chronicle-memory.md
scenario-cache.md
warden-arc.md
epsilon-overview.md
lapd-blues-patterns.md
scenario-timeline.md
political-map.md
If the task is narrowly scene-writing, prioritize:
epsilon-overview.md
lapd-blues-patterns.md
warden-arc.md
If the task is plot evolution or continuity checking, prioritize:
chronicle-memory.md
scenario-cache.md
scenario-timeline.md
warden-arc.md
political-map.md
If the task needs live Notion retrieval, read notion-search-playbook.md
before searching so the lookup starts in the right database.
Interpretation rules
- Prefer chronology over isolated scene impressions.
- Do not flatten Warden into either a martyr or a mastermind. Keep her
politically constrained, operationally strong, and emotionally contained.
- Treat
LAPD Blues as ensemble-state scenes.
- Treat
roll call as leadership, pressure, and politics scenes.
- Preserve the campaign's texture: institutional fatigue, dark humor, loyalty,
underfunding, gray-zone pragmatism.
- Epsilon is under-valued, not weak.
- For Notion research, prefer the most specific collection first instead of
broad workspace search.
- Use
MJ as the database map, Groupe Epsilon as the main faction anchor, and
scenario pages as the main evidence for plot evolution.
- If newer Notion material conflicts with the lore pack, flag the conflict and
update the relevant lore file instead of improvising around it silently.
- If the user gives table-confirmed continuity updates that are not yet cleanly
reflected in Notion, update
chronicle-memory.md.
- If the same scenario material is repeatedly needed, prefer
scenario-cache.md
plus incremental refresh instead of re-reading the whole chain every time.
Output guidance
When summarizing:
- separate character arc, group identity, and institutional pressure when useful
- synthesize across scenarios instead of over-indexing on one page
When writing new scenes:
- keep pair dynamics and room texture specific
- start concrete and bodily, not abstract
- let humor carry stress instead of removing it
When reviewing a new scenario idea:
- check Warden's goal
- check what the institution wants
- check what Epsilon needs
- look for tension between those three
When researching in Notion:
- say which source tier you are using when it matters: local lore, live page, or
inference
- fetch anchor pages before synthesizing across multiple weak search hits
- use SQL database queries only when ordinary search is noisy or incomplete
Maintenance
When new analysis materially improves the local canon:
- update the relevant file in
/Users/ludovicfleury/Documents/RPG/lore/
- keep changes concise and synthesis-oriented
- avoid duplicating the same point across several files
Useful split:
- live table-confirmed memory and corrections ->
chronicle-memory.md
- processed scenario retrieval checkpoints ->
scenario-cache.md
- stable group identity ->
epsilon-overview.md
- evolving Warden interpretation ->
warden-arc.md
- scene grammar ->
lapd-blues-patterns.md
- date-based campaign evolution ->
scenario-timeline.md
- institutions, rivals, allies, and pressure systems ->
political-map.md
1---2name: cops-epsilon-lore3description: Use when working on the COPS campaign centered on Groupe Epsilon, Warden, LAPD Blues, roll call scenes, or related scenario continuity. Read the local lore pack first, preserve chronology and tone, and update the canon when new Notion findings materially change the understanding.4---56# COPS Epsilon Lore78This skill is the retrieval and continuity workflow for the Epsilon/Warden9campaign.1011## When to use1213Use this skill when the request involves any of:1415- Groupe Epsilon16- Carol "Warden" Murphy17- LAPD Blues18- roll call scenes19- scenario continuity across the COPS campaign20- writing new scenes, summaries, or analysis that should stay consistent with21 the existing campaign arc2223## Source of truth2425The living source of truth is Notion.2627The fast local working canon is the lore pack in:2829- `/Users/ludovicfleury/Documents/RPG/lore/README.md`30- `/Users/ludovicfleury/Documents/RPG/lore/chronicle-memory.md`31- `/Users/ludovicfleury/Documents/RPG/lore/scenario-cache.md`32- `/Users/ludovicfleury/Documents/RPG/lore/epsilon-overview.md`33- `/Users/ludovicfleury/Documents/RPG/lore/warden-arc.md`34- `/Users/ludovicfleury/Documents/RPG/lore/lapd-blues-patterns.md`35- `/Users/ludovicfleury/Documents/RPG/lore/scenario-timeline.md`36- `/Users/ludovicfleury/Documents/RPG/lore/political-map.md`3738Read the local lore pack before doing substantial campaign work. Read Notion as39needed when the user asks for verification, new material, or deeper research.4041For live Notion research, use:4243- `/Users/ludovicfleury/.codex/skills/cops-epsilon-lore/references/notion-search-playbook.md`4445That playbook contains the current workspace map, database routing, query46patterns, and fallback search order.4748## Reading order4950Default order:51521. `chronicle-memory.md`532. `scenario-cache.md`543. `warden-arc.md`554. `epsilon-overview.md`565. `lapd-blues-patterns.md`576. `scenario-timeline.md`587. `political-map.md`5960If the task is narrowly scene-writing, prioritize:61621. `epsilon-overview.md`632. `lapd-blues-patterns.md`643. `warden-arc.md`6566If the task is plot evolution or continuity checking, prioritize:67681. `chronicle-memory.md`692. `scenario-cache.md`703. `scenario-timeline.md`714. `warden-arc.md`725. `political-map.md`7374If the task needs live Notion retrieval, read `notion-search-playbook.md`75before searching so the lookup starts in the right database.7677## Interpretation rules7879- Prefer chronology over isolated scene impressions.80- Do not flatten Warden into either a martyr or a mastermind. Keep her81 politically constrained, operationally strong, and emotionally contained.82- Treat `LAPD Blues` as ensemble-state scenes.83- Treat `roll call` as leadership, pressure, and politics scenes.84- Preserve the campaign's texture: institutional fatigue, dark humor, loyalty,85 underfunding, gray-zone pragmatism.86- Epsilon is under-valued, not weak.87- For Notion research, prefer the most specific collection first instead of88 broad workspace search.89- Use `MJ` as the database map, `Groupe Epsilon` as the main faction anchor, and90 scenario pages as the main evidence for plot evolution.91- If newer Notion material conflicts with the lore pack, flag the conflict and92 update the relevant lore file instead of improvising around it silently.93- If the user gives table-confirmed continuity updates that are not yet cleanly94 reflected in Notion, update `chronicle-memory.md`.95- If the same scenario material is repeatedly needed, prefer `scenario-cache.md`96 plus incremental refresh instead of re-reading the whole chain every time.9798## Output guidance99100When summarizing:101102- separate character arc, group identity, and institutional pressure when useful103- synthesize across scenarios instead of over-indexing on one page104105When writing new scenes:106107- keep pair dynamics and room texture specific108- start concrete and bodily, not abstract109- let humor carry stress instead of removing it110111When reviewing a new scenario idea:112113- check Warden's goal114- check what the institution wants115- check what Epsilon needs116- look for tension between those three117118When researching in Notion:119120- say which source tier you are using when it matters: local lore, live page, or121 inference122- fetch anchor pages before synthesizing across multiple weak search hits123- use SQL database queries only when ordinary search is noisy or incomplete124125## Maintenance126127When new analysis materially improves the local canon:128129- update the relevant file in `/Users/ludovicfleury/Documents/RPG/lore/`130- keep changes concise and synthesis-oriented131- avoid duplicating the same point across several files132133Useful split:134135- live table-confirmed memory and corrections -> `chronicle-memory.md`136- processed scenario retrieval checkpoints -> `scenario-cache.md`137- stable group identity -> `epsilon-overview.md`138- evolving Warden interpretation -> `warden-arc.md`139- scene grammar -> `lapd-blues-patterns.md`140- date-based campaign evolution -> `scenario-timeline.md`141- institutions, rivals, allies, and pressure systems -> `political-map.md`