df-context-storelisted

# df-context-store — plant the inner-loop substrate (DF Stage 0.5) Goal: give the repo a **persistent, in-repo, read-first agent substrate** so analysis is done once and reused, hand-offs can't silently degrade, and nothing ships unverified. This is the inner-loop complement to the heavy DF build stages — the build injects rigor at the seams; this is what *lives in the repo* and binds every future session. It runs between Stage 0 (Frame) and Stage 1 (PO), and again on demand to refresh. Template (source of truth): the `substrate-template/` directory bundled alongside this skill (`skills/df-context-store/substrate-template/`). ## Procedure 1. **Emit the payload.** Copy `substrate-template/dotclaude/` into the target repo as `.claude/` (agents + context store + `hooks/` + `contract-check` + `commit-sync` + `AGENT-CONTRACTS.md`). Don't overwrite an existing populated store — merge. 2. **Populate from source, don't invent.** - `.claude/context/SERVICE-MAP.md` — the structural map (services/db/queue/API + flows), generated from the real codebase (use `service-mapper`). - `.claude/context/DATA-FLOW.md` — the data-transform view: data nodes (schema/origin/**authority**/class), the transform graph (`pure|effect`), and the validation rules (`LOCAL` reject / `GLOBAL` reconcile). Populate nodes + authority from source; leave rules you can't yet cite as marked skeletons. - Leave `FINDINGS.md`/`DECISIONS.md` as clean skeletons that accumulate as the