← ClaudeAtlas

reconcilelisted

Use after /audit resolved the RV ledger and wrote the reconciliation brief — you are the sole explicit writer of reconciled truth. Consume the RV + brief, write changes through two surfaces (direct edit for per-slice artefacts, REV for governance/spec), and hand off a resolved outcome to /close. Routed to from /audit.
davidlee/doctrine · ★ 1 · DevOps & Infrastructure · score 69
Install: claude install-skill davidlee/doctrine
# Reconcile You are the **sole explicit writer** of reconciled truth — the writer half of the `audit → reconcile → close` seam (ADR-003 §7; ADR-009 §1). Audit identifies what changed and assembles the reconciliation brief; you consume it, write the changes, and record what was done. Close confirms the outcome before the terminal transition. You write to **two surfaces** with different mechanisms (D2): | Surface | Mechanism | |---|---| | **Per-slice artefacts** (`design.md`, `slice-NNN.md`) | Direct edit with user agreement | | **Governance/spec truth** (ADRs, specs, requirements, policies, standards) | REV kind (`doctrine revision`) — typed `[[change]]` rows, approval checkpoint, apply path | Project-local documentation outside `.doctrine/` is **not** a doctrine feature category — edit it directly like any project file, same as per-slice artefacts. A single reconcile pass may use both surfaces — e.g. update `design.md` directly *and* author a REV for an ADR amendment. Where each change lands is driven by the reconciliation brief, not guessed. > **A brief item can name a surface you don't write.** `plan.toml` criteria > (`EN-/EX-/VT-`, `PHASE-NN`) are immutable-append (boot rule) — not a reconcile > surface. If a brief item asks you to edit a plan criterion, do not; hand it back > to `/audit` or `/consult` as a design/plan escalation. And a conformance / > "spurious undelivered" item is fixed by the **selector registry** (`doctrine > slice selector rm`/`add`) — the load-