task-traceability

Task Traceability — Foundational Layer

Traceability is not optional. It is the foundation that makes the Plan→Build→Verify→Review→Accept chain auditable, handoffs reliable, and sign-off meaningful. Every link must produce a traceable record. A single broken link breaks the entire chain.

The Universal Five-Step Pattern

Every role in the chain follows the same five-step pattern, applied to its specific context:

Step 1: Trace (追溯)
  └── Identify all upstream requirements and artifacts you must reference

Step 2: Execute (执行)
  └── Do the work, following the traced requirements

Step 3: Map (映射)
  └── Link every output back to a specific upstream requirement

Step 4: Evidence (举证)
  └── Provide proof that each mapping is correct and complete

Step 5: Record (记录)
  └── Persist the traceability record so downstream roles can pick up the chain

Why five steps? Without Trace, you don't know what to do. Without Map, nobody knows why you did it. Without Evidence, your output is unverifiable. Without Record, the next link starts blind.

Why Every Link Matters

Plan ──→ Build ──→ Verify ──→ Review ──→ Accept
  │         │         │          │           │
  │         │         │          │           └── Break here → sign-off is unverifiable
  │         │         │          └── Break here → audit trail is incomplete
  │         │         └── Break here → verification is untrustworthy
  │         └── Break here → implementation is untraceable
  └── Break here → entire chain starts without a foundation

A chain is only as strong as its weakest link. Traceability must be enforced at every link.

Role-Specific Application

Plan — Blueprint Traceability

Plan is the chain's foundation. If blueprint traceability is broken, every downstream link is working from ambiguity.

Step	Action
Trace	Read the original requirement. Extract business goals, constraints, scope boundaries, and success criteria.
Execute	Design the blueprint: architecture, interfaces, data flow. Break into ordered Build steps, each with completion criteria.
Map	Every Build step must trace back to a specific requirement. Every completion criterion must be objectively verifiable.
Evidence	Self-check: can a Builder start from this blueprint alone? Are edge cases covered? Are interfaces unambiguous?
Record	Write the blueprint document. Push tasks to the orchestrator queue. Store the blueprint in shared context (set-context). Notify Leader.