Traceability Map

Purpose

Provide a traceability reference that maps DSAMbayes issues and recommendations to implementation status and evidence.

Authoritative data source

The single source of truth for all issue and recommendation status is:

code_review/audit_report/issue_register.csv

This register contains every ENG, INF, and GOV issue and recommendation with columns for status, severity, owner, linked IDs, notes, and a long-form explanation field.

Two stakeholder-facing summary CSVs are published alongside this page under docs/appendices/traceability-data/:

issue_traceability.csv — per-issue status, severity, scope, and evidence anchors.
recommendation_closure_matrix.csv — per-recommendation closure status and linked issues.

These files are derived snapshots. Where they conflict with issue_register.csv, the register takes precedence.

Snapshot metrics (as of 2026-02-28)

Non-GOV issues and recommendations

All ENG and INF issues: closed (including backlog items accepted and closed 2026-02-28)
All ENG and INF recommendations: closed / implemented

GOV issues

GOV-ISSUE-001 through GOV-ISSUE-004: open (governance items; resolution deferred to management review cycle)

How to use this map

Start with an issue ID or recommendation ID.
Open code_review/audit_report/issue_register.csv.
Confirm status in the status column and review linked IDs in linked_ids.
Follow evidence paths referenced in the notes column to code files, tests, and review records.
Use internal engineering documentation for release decision criteria.

Representative mappings

ID	Type	Status	Evidence anchors
`ENG-ISSUE-014`	Issue	`closed`	`R/scale.R`, `tests/testthat/test-scale-guardrails.R`
`INF-ISSUE-006`	Issue	`closed`	`R/diagnostics_report.R`, `tests/testthat/test-diagnostics-report.R`
`INF-REC-004`	Recommendation	`closed`	Holiday/time-components implementation and review references
`ENG-REC-003`	Recommendation	`closed`	Pooled RMSE and scale wiring closure references

Traceability and release approval

Traceability status alone does not authorise a release. Release sign-off still requires:

Mandatory quality gates passed.
Required release evidence bundle complete.
Final decision recorded in sign-off template.