# Cops Memory Updater

> Use when the user gives corrective continuity feedback, table outcomes, arrests, deaths, closures, relationship shifts, or pressure changes that should persist in the long COPS chronicle memory even if Notion is not updated yet.

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

---


# COPS Memory Updater

This skill updates the local living memory of the COPS chronicle.

Use it when the user tells you what really happened in play and that knowledge
should persist across later recap, pressure mapping, scenario inspiration, or
scene writing.

The file to maintain is:

- `/Users/ludovicfleury/Documents/RPG/lore/chronicle-memory.md`

You may also need to maintain:

- `/Users/ludovicfleury/Documents/RPG/lore/scenario-cache.md`

## When to use

Use this skill when the user gives any of:

- table outcomes
- corrections to a recap
- `actually this NPC did X`
- `this case was closed`
- `these people were arrested`
- `this character died`
- `this faction lost leverage`
- `remember that from now on...`

## Update workflow

### 1. Normalize the update

Extract:

- what changed
- when it changed
- who it affects
- whether it is confirmed fact or still uncertain

### 2. Patch the memory file

Update the most relevant sections in `chronicle-memory.md`:

- `Latest Playable Point`
- `Confirmed Table Outcomes`
- `Case And Faction Status`
- `NPC Pressure Changes`
- `Important Small Details`
- `Open Questions / Needs Verification`

Keep entries short, factual, and easy to reuse.

If the user correction also clarifies what the latest processed scenario state
is, update `scenario-cache.md` too.

### 3. Preserve source clarity

If the information comes directly from the user as table truth, record it as
current truth for active continuity.

If the information is uncertain or disputed, put it under:

- `Open Questions / Needs Verification`

### 4. Keep it campaign-specific

Do not genericize the update.
Write it in terms of this long chronicle and what changes from now on.

### 5. Support incremental continuity

When a correction confirms that a scenario was already processed and only its
outcome changed, do not force a full scenario re-pull later.

Instead:

- update `chronicle-memory.md`
- update `scenario-cache.md` if the checkpoint or continuity note should change
- let later skills reuse that local state unless a fresh Notion pull is needed

## Output guidance

After updating the file, briefly tell the user:

- what was added or changed
- which continuity layer it will now affect

## Guardrails

- Do not overwrite confirmed facts casually.
- Do not turn one update into a long report.
- Do not lose the difference between a closed case, a public appearance of
  closure, and a politically buried problem.
- Do not forget that tiny details can matter more than headline events later.

Think of this skill as:

user correction in,
living chronicle memory updated.