Packages

development-driven-specs — the dds toolchain (protocol 2) as a Mix task. A thin shim over the bundled instruments (Python, stdlib); never a port.

Current section

Files

Jump to
dds priv toolchain migrations 0.7.0.md
Raw

priv/toolchain/migrations/0.7.0.md

# 0.7.0 — residuals: the ledger of known gaps
## 1. Extract residuals from `Current state` prose
For each `docs/risks/*.md`: the ⚠ items, `Open:` fragments, and
"still open" clauses in **Current state** are residual-shaped. Move
each into a structured `## Residuals` section (shape:
`risks-README.md`): mint a corpus-unique `res.<slug>` id, set state
(`open`, or `accepted <date> (<by-or-adr>)` where an ADR already
ratifies living with it — e.g. gaps bounded by an
`Accepted (interim, …)` decision), write the one-sentence gap, and add
the witness `[file | "verbatim quote"]` from the code the prose cites
(quote it VERBATIM — the check verifies it). Leave a `see res.<id>`
reference behind wherever the same gap is described in another file
(ADR premises, other risks) instead of the duplicated prose.
Do not invent residuals the prose does not carry; do not drop any ⚠
item silently — one line each, or ask.
## 2. Run `/dds-check`
Malformed lines, duplicate ids, and dead quotes surface immediately;
fix before committing. Expect previously-nagging background findings
to re-report as `[known: res.<id>]`.