Build · Create · Engineering
Requirements traceability matrix
A matrix linking every requirement to its tests (and back), with computed orphans and a coverage percentage that clears your bar.
You receive: A structured traceability matrix (JSON) that passes the bidirectional-link, orphan, and coverage checks.
Part of Ship MVP
Example
A sample of what this play produces. Your result is generated for your inputs.
Title
Requirements traceability matrix: STUD platform release gate
Requirements
- Id
- REQ-GATE-01
- Priority
- high
- Text
- A pull request to main settles only when the cred-free gate (judge tiers, voice lint, unit tests, lint, tokens, typecheck, schema drift, build) is green.
- Linked Tests
- TST-GATE-SYNC
- TST-GATE-DRIFT
- Id
- REQ-JUDGE-01
- Priority
- high
- Text
- Every deliverable passes its play's acceptance check before it lands in the workspace.
- Linked Tests
- TST-JUDGE-MACHINE
- TST-JUDGE-ISOLATION
- Id
- REQ-JUDGE-02
- Priority
- high
- Text
- The judge harness runs submissions process-isolated with a hard timeout per task.
- Linked Tests
- TST-JUDGE-ISOLATION
- Id
- REQ-CATALOG-01
- Priority
- high
- Text
- Every catalog play seeds with a valid intake schema, an acceptance template, and settlement terms.
- Linked Tests
- TST-SEED-SHAPE
- TST-SEED-SYNC
- Id
- REQ-FACTS-01
- Priority
- medium
- Text
- A workspace fact stated once prefills every later play intake that declares the matching key.
- Linked Tests
- TST-INTAKE-PREFILL
- Id
- REQ-VOICE-01
- Priority
- medium
- Text
- User-facing copy contains no em dashes and uses the D-023 play/run vocabulary.
- Linked Tests
- TST-VOICE-LINT
- Id
- REQ-TOKENS-01
- Priority
- medium
- Text
- UI styles resolve from design tokens only; design-tokens.json and globals.css stay 1:1.
- Linked Tests
- TST-TOKENS-CHECK
- Id
- REQ-DEPLOY-01
- Priority
- low
- Text
- A production deploy applies committed schema migrations and the catalog sync before new code serves.
- Linked Tests
- TST-DEPLOY-MIGRATE
Tests
- Id
- TST-GATE-SYNC
- Suite
- platform/src/gate-local-sync.test.ts
- Linked Requirements
- REQ-GATE-01
- Id
- TST-GATE-DRIFT
- Suite
- scripts/check-schema-drift.mjs (gate step)
- Linked Requirements
- REQ-GATE-01
- Id
- TST-JUDGE-MACHINE
- Suite
- judge/tests/test_machine_tier.py
- Linked Requirements
- REQ-JUDGE-01
- Id
- TST-JUDGE-ISOLATION
- Suite
- judge/tests/test_isolation.py
- Linked Requirements
- REQ-JUDGE-01
- REQ-JUDGE-02
- Id
- TST-SEED-SHAPE
- Suite
- platform/src/db/dev-seed.test.ts
- Linked Requirements
- REQ-CATALOG-01
- Id
- TST-SEED-SYNC
- Suite
- scripts/sync-catalog.mts (dry-run diff check)
- Linked Requirements
- REQ-CATALOG-01
- Id
- TST-INTAKE-PREFILL
- Suite
- platform/src/app/plays intake prefill spec
- Linked Requirements
- REQ-FACTS-01
- Id
- TST-VOICE-LINT
- Suite
- scripts/voice-lint (gate step)
- Linked Requirements
- REQ-VOICE-01
- Id
- TST-TOKENS-CHECK
- Suite
- tokens:check + lint:tokens (gate steps)
- Linked Requirements
- REQ-TOKENS-01
- Id
- TST-DEPLOY-MIGRATE
- Suite
- scripts/deploy-migrate.mts smoke
- Linked Requirements
- REQ-DEPLOY-01
Orphans
Summary
- Requirements
- 8
- Tests
- 10
- Covered Requirements
- 8
- Coverage Pct
- 100
- Note
- Every requirement traces to at least one automated check and every check traces back; coverage 100% clears the 90% minimum.
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the submitted matrix (JSON) is internally consistent: requirement and test ids are unique, every link resolves and is bidirectional, priorities are in the allowed set, the asserted orphan lists and coverage percentage are recomputed and must match, and coverage clears your minimum. STUD does NOT judge whether the tests actually exercise the requirements or whether the requirements are correct; it checks the links and the arithmetic.
Get early access to STUD the day it goes live.