Background
We already have a local traceability coverage checker that evaluates requirement evidence metrics (code links, test links, fully linked requirements, testcase linkage).
To support project-wide adoption, this checker should be integrated into docs-as-code in a controlled, low-risk rollout.
Goal
Introduce the checker as an official docs-as-code capability and run it in CI in reporting mode first, before strict gating.
Scope
Add the traceability coverage checker script to docs-as-code as maintained project functionality.
Ensure it can read generated needs.json in CI environments.
Add a CI step that always publishes the metric summary (reporting mode, non-blocking).
Document exact metric definitions and calculation scope in docs-as-code documentation.
Keep thresholds configurable by parameters, defaulting to non-blocking behavior for rollout.
Acceptance Criteria
Checker is part of the repository and executable via documented command.
CI runs checker and surfaces summary output on every relevant pipeline run.
Pipeline does not fail solely because of threshold misses in initial rollout mode.
Documentation explains each metric and input assumptions clearly.
A follow-up path to strict threshold gating is documented.
Out of Scope
New metamodel semantics or new cross-need link types.
Mandatory hard fail policy for all repos immediately.
Full AoU and architecture traceability enforcement.
Dependencies
Background
We already have a local traceability coverage checker that evaluates requirement evidence metrics (code links, test links, fully linked requirements, testcase linkage).
To support project-wide adoption, this checker should be integrated into docs-as-code in a controlled, low-risk rollout.
Goal
Introduce the checker as an official docs-as-code capability and run it in CI in reporting mode first, before strict gating.
Scope
Add the traceability coverage checker script to docs-as-code as maintained project functionality.
Ensure it can read generated needs.json in CI environments.
Add a CI step that always publishes the metric summary (reporting mode, non-blocking).
Document exact metric definitions and calculation scope in docs-as-code documentation.
Keep thresholds configurable by parameters, defaulting to non-blocking behavior for rollout.
Acceptance Criteria
Checker is part of the repository and executable via documented command.
CI runs checker and surfaces summary output on every relevant pipeline run.
Pipeline does not fail solely because of threshold misses in initial rollout mode.
Documentation explains each metric and input assumptions clearly.
A follow-up path to strict threshold gating is documented.
Out of Scope
New metamodel semantics or new cross-need link types.
Mandatory hard fail policy for all repos immediately.
Full AoU and architecture traceability enforcement.
Dependencies