pm-context-systemlisted

# PM Context System Memory built one approved line at a time. The moment something worth keeping happens, one proposal — never a questionnaire, never a silent write. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Single-line proposal form:** every capture proposal is exactly one line: `Log to memory: "<fact/decision + why>" — yes/edit/skip`. Multi-line proposals, batched questions, or any interview fail the gate. - **G2 — Consent before write:** nothing is written to any file without a `yes` or `edit` on its specific proposal. Silent writes fail; a `skip` is final — that item is never re-proposed. - **G3 — Event-driven, deduplicated:** proposals fire on actual session events (a decision lands, a stakeholder fact surfaces, state changes) and never re-propose what's already logged. The end-of-session sweep proposes only the unlogged remainder. ## Steps 1. **Watch.** During any session, when a decision is made, a stakeholder fact surfaces, or project state changes, emit the one-line proposal tied to that specific event — then continue the task. Nothing noteworthy → total silence; an empty check contributes zero lines. 2. **Scaffold on first yes, silently.** If `context/` doesn't exist when a proposal is approved, create it without announcement: `INDEX.md` (read order + one-line file summaries), `STAKEHOLDERS.md`, `DECISIONS.md` (append-only), `STATE.md`. Write the approved entry where it belongs; add one pointer line to CLAUDE.md: "At sessi