Orchestrata Ultimate › Plans › evidence › d2-traceability

D2 Evidence Pack — Traceability Quintuple Collapse

Source: plans/evidence/d2-traceability.md at 8a2cb42ad · last changed 2026-07-27 · first committed 2026-07-05 · 90 lines.

Prose pending.

Plan text

D2 Evidence Pack — Traceability Quintuple Collapse

Source: auditor agent W3.E2 (2026-07-06), verified with corrections by the orchestrator (see "Verification notes"). Decision: plan §D, D2. Blocks W3.2.

Verification notes (orchestrator)

1. API inventory

Module Lines Key exports
core/base/traces.py 72 traces() decorator + id-pattern validation. Zero imports — layer-0. Docstring: built to eliminate layer-0 upward imports. 444/671 modules import it.
core/traceability/__init__.py 511 REDEFINES traces() (114–156); TraceInfo/ValidationReport, collect_traces, generate_rtm (347, JSON list), generate_rtm_markdown (392), validate_traces (466)
core/traceability_utils.py 514 Docstring claims "zero orchestrata imports — copied into generated project workspaces". REDEFINES traces(); own Requirement/UserStory/RTMReport; scan_traces (326), generate_rtm (357), save_rtm
core/tracing/traceability.py ~331 Pre-port residue (docstring references monorepo orchestrata.core.traceability; "Armada" typo). REDEFINES traces(); generate_rtm (167), generate_rtm_markdown (212, corrupted header line 231)
verification/traceability.py 612 "Migrated from spike/traceability.py". Only one of the 5 that imports the canonical decorator (from ...core.base.traces import traces, line 25). Same Requirement/RTMReport shape as traceability_utils. scan_traces (398), generate_rtm (439), save_rtm (526)

2. Twin analysis — generate_rtm_markdown

core/traceability/__init__.py:392 vs core/tracing/traceability.py:212: 71-line bodies, byte-identical except one line — the corrupted Arabic header (above). Copy-paste twins with one-sided corruption.

3. Consumer map (import-line evidence)

4. Risks (verified subset)

  1. 3-way REQ/US regex divergence across the redefined traces() decorators — an id can validate under one module and be orphaned by another's scanner. (Directly relevant to RTM correctness; verify exact patterns during W3.2.)
  2. Corrupted RTM header in a production path (§2).
  3. Self-tracing noise: verification/traceability.py decorates ~10 of its own symbols with the same REQ-097-001 tuple → duplicate-location noise per scan.
  4. Contract violation: traceability_utils used as a production library.

5. Recommendation (auditor, orchestrator-endorsed)