docs(requirements): re-express against intent sources and record unstated obligations

[gvsambhu]

What this changes

36 → 51 requirements. The set is re-expressed against the intent sources rather than transcribed from a single one. No obligation changed, and nothing shipped becomes non-conformant.

Why

The published set was produced by transcribing the project plan's requirements section. A transcription inherits its source's structure and cannot notice what was never on it — so it carried the plan's shape and its gaps unchanged, including the absence of any requirement for the README's own stated thesis.

The three classes of change

Grouping and form. Nine capability sections replace a split that was release markers wearing capability labels. Front matter the standard expects and the document lacked — purpose, scope, glossary, assumptions, out-of-scope. Compound statements split into a requirement plus acceptance criteria, so obligations that were previously asserted can now be tested. Release markers moved out of the statements into a status table that doubles as the numeric index.

Recorded intent — 15 requirements. Capabilities that were always intended and never written down. Most consequentially, the three negative guarantees the architecture actually rests on:

• FR-31 — no source file is ever silently dropped
• FR-36 — no source feature is ever silently dropped from rendered output
• FR-34 — LLM output must not affect the deterministic artefact

The last is the README's stated point of view and had no requirement in any prior list.

Verified status. Every status claim is checked against the code rather than inferred. Five requirements that read as shipped now read as partial, each naming the specific acceptance criterion not yet met — FR-3 AC-1, FR-13 AC-2, FR-18 AC-1, NFR-4 AC-3, NFR-5 AC-2. One that read as partial is in fact shipped: FR-7c's second corpus was deferred by design, not missed.

Compatibility

• Identifiers unchanged and unrenumbered; new ones start at FR-40 and NFR-6
• Retired NFR-1 keeps its number, so existing references still resolve
• Requirements continue to cite no ADRs — traceability still runs one way

Closes two open design-review findings

Both were resolved by wording rather than by a separate decision, and are called out here so they are ratified rather than left to lapse:

• ADR-018 review fix(dc1): development-review remediation (golden harness, parser/graph fixes, codegen pin) #4 — NFR-4's v1/v1.1 scope. NFR-4 now reads "each shipped render target", under which the Go deferral is not a gap. Matches ADR-018's own reasoning.
• ADR-014 review — FR-15's path-format drift note. FR-15 no longer names a path, so there is nothing left to drift from.

Not in this PR

7 ADR amendments, 1 new ADR (output-path safety), and 9 code fixes are tracked separately. Five of the code fixes are unblocked today.

🤖 Generated with Claude Code