Files

T

veronica f0d2dd9920 docs(W4): stamp kind and status front matter on 104 live documents

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`.

2026-08-20 19:30:25 -05:00

3.9 KiB

Raw Blame History

kind, status

kind	status
record	active

VERDICT: GO

Native Kanban/SOT canon independent re-review 2

Independent read-only re-review of the complete updated staged canon. Prior proposal-audit blocker is closed; no KCR-001–016 regression or new blocker found.

Prior blocker closure

contracts/kanban-schema.v1.ts:836-837 declares the required unique task_events(workspace_id,id) key before proposal declaration.
contracts/kanban-schema.v1.ts:885-894 adds both composite proposal audit FKs—submission and accepted-command event—to that exact workspace-aware key with RESTRICT.
Declaration/migration order is executable and explicit in SHARED-CONTRACT.md:79-91: events/key first, proposal table second, both FKs third/fourth, then command enablement. This avoids forward-reference/circular-DDL ambiguity.
Submission/acceptance semantics are frozen in SHARED-CONTRACT.md:87-91: preallocate proposal ID; create exact change_proposal.submitted event and proposal in one transaction; on acceptance lock proposal/target, execute the normal command, and bind only a same-workspace/target event with submission causation and payload.changeProposalId equal to the locked proposal.
Required missing, foreign-workspace, unrelated-proposal, unrelated-target, and unrelated-command negatives are explicit in REQUIREMENTS.md REQ-SOT-004 and SHARED-CONTRACT.md:121; KBN-100/110/140 own migration, service, and integration evidence.

KCR closure matrix

KCR	Status
001 health/proof	CLOSED
002 error discrimination	CLOSED
003 approval/assignment binding	CLOSED
004 monotonic fencing/composites	CLOSED
005 tenant-safe relations	CLOSED
006 outage proposal persistence/commands/audit binding	CLOSED
007 dependency/API freeze sequencing	CLOSED
008 concrete N-1 map	CLOSED
009 dependency uniqueness	CLOSED
010 project congruence	CLOSED
011 immutable audit retention	CLOSED
012 retry/quarantine/vocabulary	CLOSED
013 archive/tags target semantics	CLOSED
014 recovery validator/owner slice	CLOSED
015 pure Coordinator split	CLOSED
016 health code/state pairing	CLOSED

Fixed invariants remain consistent: PostgreSQL is sole writable SOT; writes require transaction-local proof and fail closed; exports never import sources; notes are attributable proposals only; Coordinator has no scope/gate/certify/merge authority; Certifier has no merge authority.

Reproducible validation evidence

Executed read-only with current-stack config/toolchain /src/mosaic-mono-v1:

./node_modules/.bin/prettier --config /src/mosaic-mono-v1/.prettierrc --check <all 9 publication artifacts>
PASS: All matched files use Prettier code style.

strict TypeScript --noEmit --strict --skipLibCheck --target ES2022 --module NodeNext --moduleResolution NodeNext <four contract copies with current Drizzle node_modules resolution>
PASS

cascade/TODO/TBD/stale-hold grep plus composite-FK/semantic-marker invariant checks
PASS

The TypeScript check used a disposable copy under /home/hermes/agent-work solely to provide external-file NodeNext dependency resolution; the reviewed staging artifacts were not modified.

Residual findings

None blocking. Implementation must execute the frozen KBN-100/KBN-110/KBN-140 proposal-event-chain tests and SecReview evidence before feature release, as already required by the canon.

No artifact source repository, branch, PR, or provider state was modified.

3.9 KiB Raw Blame History Unescape Escape