Problem
spec/interface/interface-001-codegen-api.md declares five acceptance criteria
(interface-001-AC-1 through interface-001-AC-5) that are verified by real automated
tests in tests/interface_001.rs, which run on every cargo test in make ci. Their
correct verification method is Test (TC-028).
The active spec-artifacts-process module declares matrix-mining archetypes for FR,
NFR, StR, TestMatrix, SuiteRegistry and Inspections, but none for interface
documents. quire coverage therefore cannot mine interface-001-codegen-api.md at all:
interface-001-AC-1 through interface-001-AC-5 resolve to no declared row for any
archetype to check, and the ## Interface Requirement Coverage row in
spec/test-matrix.md is never cross-checked against this file's acceptance-criteria
table. A ✅ Covered status there is a status the gate can never contradict — not
because the criteria are actually unverifiable by tooling, but because no archetype
exists to let quire coverage see them at all.
One symptom: the /// Trace: interface-001-AC-N, TC-028 lines in
tests/interface_001.rs produce dangling-trace warnings under quire coverage --strict,
because the AC ids they cite resolve to nothing minable. Those warnings are intentional
and should stay visible — they are the honest marker of this gap — rather than being
silenced by cutting the AC ids from the Trace: lines or by mislabeling the criteria as
Inspection (human attestation) when a machine test already verifies them on every
cargo test.
Fix
Add an interface archetype to spec-artifacts-process that mines an interface
document's acceptance-criteria table the way the existing archetypes mine FR/NFR/StR
criteria tables, so quire coverage can resolve interface-001-AC-1 through
interface-001-AC-5 as declared rows and cross-check them against
spec/test-matrix.md's ## Interface Requirement Coverage section and against the
Trace: lines in tests/interface_001.rs.
References
spec/interface/interface-001-codegen-api.md — Open items
spec/test-matrix.md — ## Interface Requirement Coverage
tests/interface_001.rs
Problem
spec/interface/interface-001-codegen-api.mddeclares five acceptance criteria(
interface-001-AC-1throughinterface-001-AC-5) that are verified by real automatedtests in
tests/interface_001.rs, which run on everycargo testinmake ci. Theircorrect verification method is
Test (TC-028).The active
spec-artifacts-processmodule declares matrix-mining archetypes forFR,NFR,StR,TestMatrix,SuiteRegistryandInspections, but none forinterfacedocuments.
quire coveragetherefore cannot mineinterface-001-codegen-api.mdat all:interface-001-AC-1throughinterface-001-AC-5resolve to no declared row for anyarchetype to check, and the
## Interface Requirement Coveragerow inspec/test-matrix.mdis never cross-checked against this file's acceptance-criteriatable. A
✅ Coveredstatus there is a status the gate can never contradict — notbecause the criteria are actually unverifiable by tooling, but because no archetype
exists to let
quire coveragesee them at all.One symptom: the
/// Trace: interface-001-AC-N, TC-028lines intests/interface_001.rsproduce dangling-trace warnings underquire coverage --strict,because the AC ids they cite resolve to nothing minable. Those warnings are intentional
and should stay visible — they are the honest marker of this gap — rather than being
silenced by cutting the AC ids from the
Trace:lines or by mislabeling the criteria asInspection(human attestation) when a machine test already verifies them on everycargo test.Fix
Add an
interfacearchetype tospec-artifacts-processthat mines an interfacedocument's acceptance-criteria table the way the existing archetypes mine FR/NFR/StR
criteria tables, so
quire coveragecan resolveinterface-001-AC-1throughinterface-001-AC-5as declared rows and cross-check them againstspec/test-matrix.md's## Interface Requirement Coveragesection and against theTrace:lines intests/interface_001.rs.References
spec/interface/interface-001-codegen-api.md— Open itemsspec/test-matrix.md—## Interface Requirement Coveragetests/interface_001.rs