veronica
ff40794bfe
ci/woodpecker/pr/ci Pipeline was successful
fred withdrew decision F after re-measuring channel-protocol.md with a control: zero uppercase RFC2119 terms, seven lowercase 'must' all disclaiming authority, under a banner refusing requirements status. F rested on 'the doc graph outranks the page's own banner', which contradicts decision D, 'kind follows content'. D is the rule; F was its counterexample. Neither rescue (vision's adjective edit on the citing docs, or a banner edit) was taken: a kind that survives only by editing the evidence around it is not a classification. Q1 answered: docs/README.md prescribes the contract, so by D its content is a spec, and by B it is the source of truth for that contract. A plan never outranks the artifact it planned, so the flatten plan's stale 7-value enum is corrected there rather than competing here. 128 live docs = 108 stamped + 16 operator-held + 3 supersede deferrals + 1 generated.
kind, status
| kind | status |
|---|---|
| guide | active |
Documentation Plans
Status: Current artifact index. Plans record approved intent and execution approach; they are not current product behavior or operational authority.
Documentation migration plans
- Information architecture design — approved audience books, artifact boundaries, source-of-truth rules, and migration model.
- Documentation structure README implementation — completed implementation plan for the documentation contract and atlas.
- Documentation catalog and truth audit — audit method, evidence statuses, deliverables, and acceptance criteria.
After a plan is delivered, update the canonical guide, contract, decision, or index. Do not cite a plan as proof that intended behavior shipped.