# Cops Epsilon Lore

> 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.

- Skill: `ludofleury/cops-epsilon-lore` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add ludofleury/cops-epsilon-lore`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ludofleury/cops-epsilon-lore/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: ludofleury (https://skillmd.com/u/ludofleury)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/ludofleury/cops-epsilon-lore

---


# 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:

1. `chronicle-memory.md`
2. `scenario-cache.md`
3. `warden-arc.md`
4. `epsilon-overview.md`
5. `lapd-blues-patterns.md`
6. `scenario-timeline.md`
7. `political-map.md`

If the task is narrowly scene-writing, prioritize:

1. `epsilon-overview.md`
2. `lapd-blues-patterns.md`
3. `warden-arc.md`

If the task is plot evolution or continuity checking, prioritize:

1. `chronicle-memory.md`
2. `scenario-cache.md`
3. `scenario-timeline.md`
4. `warden-arc.md`
5. `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`