Traceability Map

Purpose

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

Tracked data source

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

These files are the repository’s tracked release reference. The fuller audit register is historical private material and may exist locally under .planning/archive/code_review/audit_report/; it is not available in every clone and does not override current source, tests, or these shipped snapshots.

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

  1. Start with an issue ID or recommendation ID.
  2. Open the relevant CSV under docs/appendices/traceability-data/.
  3. Confirm status and review its evidence anchors.
  4. Follow those anchors to current code files, tests, and documentation.
  5. 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:

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