Spec & process
Whether the spec-driven workflow is real rather than aspirational: RFC-2119 requirements exist, every one is tracked in the traceability matrix, and the verify gate mechanically enforces the link between specs, matrix, and tests on every commit.
5.0 / 510 of 10 weighted points earned — snapshot of 2026-08-04
traceability-passesweight 4 ptsearned 4 / 4
Measures: npm run check:traceability exits 0
Why this weight: The core guarantee: the whole spec system is only trustworthy while the checker passes, so drift between specs, matrix, and test tags outweighs every other signal here.
zero-untrackedweight 2 ptsearned 2 / 2
Measures: no requirement left untracked
Why this weight: Untracked entries are acknowledged debt that hides real status; serious, but a narrower signal than the checker passing outright.
verify-runs-traceabilityweight 2 ptsearned 2 / 2
Measures: the local/CI gate runs check:traceability
Why this weight: Enforcement placement: a checker that passes today is worth little unless the shared gate forces it on every commit for any agent or human.
constitution-presentweight 1 ptearned 1 / 1
Measures: .specify/memory/constitution.md exists
Why this weight: Presence of the governing document matters, but presence alone proves little about practice — minimal weight.
specs-presentweight 1 ptearned 1 / 1
Measures: ≥ 10 requirement spec files
Why this weight: A crude floor on corpus size so the other checks cannot be satisfied by a near-empty specs/ directory; deliberately the weakest signal.