veronica
f0d2dd9920
Applies the document contract from
docs/plans/2026-08-20_stack-docs-flatten-and-alignment.md section 3, partially:
`kind` and `status` only. `parent` is deliberately held until the flatten in
section 4 lands, so that 127 documents do not have to be re-pointed by hand
when docs/fleet/NORTH_STAR.yaml moves to docs/NORTH_STAR.yaml.
Scope, measured on origin/next at 63069149:
127 live docs = all *.md under docs/ minus docs/archive/ minus docs/_old_structure/
104 stamped here
19 held operator judgement (plan section 9), worklist in the same PR
3 held the SUPERSEDED TASKS.md stamps, which cite the moving path
1 untouched docs/fleet/FLEET-DOCTRINE.md, already stamped in W1
Kinds applied: 54 guide, 34 record, 9 spec, 6 tracking, 1 projection.
Every row carries a confidence and a one-line rationale in the worklist.
Two collisions with the existing state, both flagged rather than resolved:
1. docs/README.md:150-160 already documents a front-matter convention
(title/type/audience/status/source_of_truth) with its own allowed values.
It is applied to 4 of 127 files. Its `status` vocabulary is
current|draft|deprecated|historical; the new contract's is active|superseded-by.
The key collides. This commit lets the new contract win and rewrites
`status: current` to `status: active` on those 4 files, keeping their other
legacy keys untouched. No code reads any of them: `git grep source_of_truth`
outside docs/ returns nothing. docs/README.md still prescribes the old
convention and is an operator row, so it is not edited here.
2. Two of the plan's 20 operator rows are YAML files, not markdown
(docs/fleet/examples/roster-v2.yaml, docs/openapi-tess.yaml), and the
contract's front-matter form has no defined meaning for a .yaml document.
That gap also applies to docs/fleet/NORTH_STAR.yaml, the source of truth
itself. Raised in the worklist.
A third row from the plan, docs/fleet/north-star.md, no longer exists: W1
renamed it to docs/fleet/FLEET-DOCTRINE.md.
Verification: 104/104 parse with the expected kind and status in front matter;
the check was shown to reject a wrong kind before it was trusted. The diff
removes 4 lines total, all of them `status: current`.
kind, status
| kind | status |
|---|---|
| guide | active |
Documentation Reports
Status: Current evidence index. Reports record reviews, tests, audits, and deferred findings; they are not requirements or operational instructions by themselves.
Use the canonical guide, API contract, source, and tests to determine current behavior. A report retains the scope and verdict of its original review unless a later report explicitly supersedes it.
Documentation evidence
- Documentation catalog and truth audit — migration inventory and static truth assessment.
- Fleet documentation IA closure — active Fleet documentation acceptance evidence; the executable book remains at
docs/fleet/. - Fleet documentation deferrals — explicit holds and deferred live-action boundaries.
- Issue #756 documentation checklist — historical completion checklist for the official Discord plugin workstream.
- Framework consistency audit — 2026-02-17 — historical framework consistency and remediation snapshot.
- Compaction-refresh #830 checklist — historical incomplete-at-snapshot documentation checklist.
Code-review evidence
- Issue #756 independent code review — historical exact-scope review of the official Discord plugin workstream.
- Gateway security-hardening code review — 2026-03-13 — historical no-blocker review snapshot.
Security evidence
- Issue #756 security review — historical security review of Discord ingress, authorization, routing, and residual risks.
QA evidence
- P8-003 performance optimization report — historical implementation evidence; not a current SLO or production benchmark.
- Gateway security-hardening QA report — 2026-03-13 — historical test report with its original live-smoke-test limitation.
Native Kanban/SOT evidence
These reports preserve the review sequence for issue #751. Their GO verdicts apply only to the reviewed historical scope and do not decide current Kanban authority or authorize held KBN-101 database work.
- Initial independent NO-GO — original blocking review.
- Independent re-review GO — follow-up closure review.
- Ultron final GO — historical final-gate record.
- KBN-101 security/architecture review — active review evidence coupled to the held KBN-101 authority surface.
Retention rules
- Preserve report wording and verdicts when migrating historical evidence.
- Keep the reviewed commit, issue, scope, and date visible when present.
- Do not treat an old approval as approval of later code.
- Link each tracked report from this index or an explicitly scoped child index.
- Put current operator procedures in the administrator guide, not in reports.