veronica
37cd00e60d
ci/woodpecker/pr/ci Pipeline failed
Records what the stamping pass applied, what it held and why, and the two places where the contract contradicts itself or the repository: - docs/native-kanban-sot/TASKS.md declares itself a build plan; the contract says TASKS.md is tracking and never a spec. - docs/requirements/native-kanban-sot.md is hand-authored prose canon; plan section 5.2 calls that source-of-truth, the contract table requires source-of-truth to be machine-readable. - docs/README.md already documents a competing front-matter convention on a colliding status key, applied to 4 files, with no code consumer. - The contract has no defined form for a .yaml document, including docs/fleet/NORTH_STAR.yaml itself.
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.