Compound

---
name: compound
description: >
  At the end of a session, suggest the key essential items to add or fine-tune in the writer's
  context — turning corrections, "I'd never say that" moments, drifts, and new angles into durable,
  approved updates to the Brief and Voice Profile (in place). Keeps the context improving with use,
  with near-zero authoring burden. Use at session end, or for "update my context", "what did we learn",
  "compound this session", "should anything go into the brief/voice profile".
---

# Compound (step 11) — context improves with use

A session-end ritual: capture what was learned and fold the essentials back into the canonical
context.

## Reads / writes
Reads the session + `newsletter-context/newsletter-brief.md` + `newsletter-context/voice-profile.md`. **Writes edits in place** to those
files (routed by section) + a changelog entry. Nowhere else — the kit reads those files, so that's
where a learning takes effect.

## Procedure
1. **Scan** the session for durable signal: corrections, "I'd never say that", a recurring new
   topic/motif, a voice rule that kept firing, a drift/pivot, a new boundary, a shifted objective.
2. **Filter to the 3–5 essentials** that *generalize* beyond this one piece. One-offs don't qualify.
3. **Route:** subject/topics/objectives/tensions/vocabulary → Brief · voice rules/"never"/naturalness → Voice Profile.
4. **Propose a short list; the writer approves/edits/rejects each** (the gate). Never silent.
5. **Apply in place** + append a one-line changelog (date · what · why · session). Bump "Last confirmed" if identity changed.

## Anti-bloat (critical)
Prefer **sharpening an existing rule** to adding a new one; merge overlaps; skip one-offs. If a file
nears its size budget, run **`prune`** first.

## Boundary
Suggests and applies *approved* context edits — it does not change the writer's published work.

---
_**Language:** if the newsletter isn't in English, converse with the writer — and write outputs — in the newsletter's language._