traceability.md

id	traceability-001
type	traceability
project	example-app
feature	auth
status	draft
version	0.1.0
owner_role	Planner
depends_on	spec-auth-001 design-001 data-model-001 api-contract-001 tasks-auth-001 test-plan-auth-001
satisfies
linked_decisions
last_validated	2026-06-07

Traceability — example-app · auth

The bidirectional matrix, regenerated at every gate from the ## Links blocks and frontmatter across the package. Human view here; machine view in traceability.json. Gate G5: 100% bidirectional — no requirement untested, no test unlinked, no ADR unreferenced. This file is the proof that nothing was dropped between idea and code.

Forward trace (REQ → everything)

REQ	Components	Data	API	Tasks	Tests	ADR	Status
REQ-001	CMP-003	ENT-user	OP-post-register	T-019, T-005, T-012	TP-001	—	pending
REQ-007	CMP-001, CMP-003	ENT-user, ENT-session	OP-post-login	T-018, T-005, T-012	TP-007	ADR-0007	pending

Backward trace (orphan detection)

Item	Traces back to a REQ?
CMP-001	✅ REQ-007
CMP-003	✅ REQ-001, REQ-007
ENT-session	✅ REQ-007
T-012	✅ REQ-001
ADR-0007	✅ REQ-001, REQ-007

Gate readout

REQ covered by ≥1 task ......... 2/2  ✅
REQ covered by ≥1 test ......... 2/2  ✅
Tasks with satisfies+files+AC .. 4/4  ✅
Orphan entities ................ 0    ✅
Orphan operations .............. 0    ✅
Dangling ADRs .................. 0    ✅
Task DAG acyclic ............... yes  ✅
Bidirectional coverage ......... 100% ✅  (release-ready)

How to regenerate: parse every spine file's frontmatter (satisfies, linked_decisions) and ## Links lines; build forward and backward edges; flag any node missing a required edge. Emit both this table and traceability.json. This is the Spec Package Architect's equivalent of Spec Kit /speckit.analyze and Kiro "Sync Files".