Specification — wf-07-01¶
US-07-01-02 — Review Evidence Chains through Trace Matrices¶
As an auditor, I want to export a trace matrix, so that I can review evidence chains such as requirements to tests and user stories to requirements in a reproducible tabular form.
US-07-01-03 — Generate Audit Evidence Bundles by Scope¶
As an auditor, I want to generate an evidence bundle for a chosen requirement or story scope, so that audits can review a reproducible package of requirements, implementation evidence, and verification links.
US-07-01-04 — Review Trace Graphs as Audit Evidence¶
As an auditor, I want to scan traceability information, so that evidence chains between requirements, implementation, and verification can be reviewed reproducibly.
REQ-00-00-00-03 — Machine-Readable Diagnostics¶
When arqix emits a diagnostic, arqix SHALL provide it in a documented machine-readable format.
Coverage: verified.
REQ-00-00-00-06 — Effective Configuration as Baseline¶
The arqix CLI SHALL resolve every command against the effective configuration.
Coverage: verified.
US-07-01-05 — Filter Traceability Reports for Audit Review¶
As an auditor, I want filtered traceability report views, so that I can focus on high-risk gaps without manually reshaping raw exports.
US-07-01-06 — Export Deterministic Trace and Coverage Evidence¶
As an auditor, I want trace graphs, matrices, and coverage reports to be deterministic, so that audit evidence remains stable across repeated runs and review packages stay comparable.
REQ-00-00-00-03 — Machine-Readable Diagnostics¶
When arqix emits a diagnostic, arqix SHALL provide it in a documented machine-readable format.
Coverage: verified.
REQ-00-00-00-06 — Effective Configuration as Baseline¶
The arqix CLI SHALL resolve every command against the effective configuration.
Coverage: verified.
US-07-01-08 — Export the Normative-Statement Classification¶
As an assessor, I want every requirement's normative-sentence classification exported as data, so that the requirement language itself — modality, EARS pattern, subject — becomes reviewable and queryable evidence instead of living only inside the checker.
REQ-07-01-08-01 — Export the Sentence Classification as CSV¶
When arqix report statements runs, arqix SHALL print every requirement's normative-sentence classification as a CSV row carrying the requirement id, the kind, the modality, the EARS pattern, and the subject.
Coverage: verified.
REQ-07-01-08-02 — Gate the Committed Statement Export for Freshness¶
When arqix report snapshot --check runs, arqix SHALL report a committed normative-statement export whose content differs from the regenerated classification.
Coverage: verified.
US-07-01-09 — Report the Codebase Size by Component¶
As an assessor, I want the codebase size reported by component, so that question Q-09 of the report catalog has a generated, always-current answer.
REQ-07-01-09-01 — Generate the Lines-of-Code Unit¶
When arqix report snapshot runs, arqix SHALL regenerate a lines-of-code unit counting the repository's Rust source files per component.
Coverage: verified.
US-07-01-10 — Report the Test-Suite Code Coverage¶
As an assessor, I want the test suite's code coverage reported as a unit, so that question Q-10 of the report catalog has a generated answer next to the requirement-coverage scoreboard.
REQ-07-01-10-01 — Render the Test-Coverage Unit from a Summary¶
When arqix report coverage runs with a coverage summary file, arqix SHALL render the test-coverage unit from the summary's totals and per-file rows.
Coverage: verified.