/learn, Knowledge Compiler

Orientation

Use when: You have a completed campaign or evolve cycle and want to compile its findings into the project's growing knowledge wiki, so future sessions start smarter, not from scratch.

Don't use when: You want a structured incident analysis first (use /postmortem, run it before /learn); you haven't finished any campaigns (nothing to compile); you want a context transfer only (use /session-handoff).

Key difference from appending: /learn doesn't create isolated per-campaign files. It integrates new findings into existing wiki pages, updating evidence lists, raising confidence where a pattern is confirmed again, and flagging contradictions. A wiki is a compiler; a log is an interpreter.

Invocation Forms

/learn, most recently completed campaign
/learn {slug}, specific campaign by slug
/learn {file-path}, specific campaign file path
/learn --from-evolve {target}, compile from /evolve pattern library
/learn --from-evolve {target} --cycle {n}, specific evolve cycle only
/learn --lint, lint-only pass (no new extraction)
/learn --compile, re-compile staging area into wiki (no new extraction)
/learn --memory, compile semantic memory blocks from planning artifacts
/learn --doc-sync, process doc-sync queue into .planning/doc-sync/latest.md

Inputs

1. A campaign slug, file path, evolve target, or "most recent" resolution
2. Corresponding postmortem in .planning/postmortems/ (optional)
3. .planning/telemetry/audit.jsonl filtered to this campaign (optional)
4. For --from-evolve: .planning/evolve/{target}/pattern-library.md

Protocol

Step 1: RESOLVE TARGET