Conformance & Traceability
How Alexandria proves the 81 requirements and 76 of the 77 catalog codes of specification v0.3.0, replays scenario F6 and generates the traceability matrix.
Conformance & Traceability
1. Coverage
| Dimension | Coverage | Where |
|---|---|---|
| Normative requirements | 81 / 81 | REQ-SYS (10), REQ-HUB (31), REQ-CLI (34), REQ-DOC (6), listed in spec/requirements.tsv. Each has at least one test named TestT_<AREA>_<NNN>_…. |
| Catalog codes | 76 / 77 | One minimal negative case per code in conformance/ (TestN_EveryReachableCode). |
| Scenario F6 | all rows | TestE2E_F6 runs the four real binaries; make demo prints the table. |
| Determinism | — | conformance/determinism_test.go checks that equal inputs give equal decisions (REQ-SYS-001). |
The single uncovered code is VERDICT_SHACL_WARNING: the PoC evaluator does not execute SHACL (DP-7), so a warning-severity finding cannot occur. This is recorded in OPEN_QUESTIONS.md.
2. Running It
make conformance # go test ./conformance/...
make e2e # TestE2E_F6 only, verbose
make demo # the four binaries and the F6 verdict table
make trace # regenerate and verify TRACEABILITY.mdT-* tests live next to the code they exercise; conformance/ holds the cross-cutting ones: the negative corpus, the determinism check and the end-to-end scenario.
3. Scenario F6
F6 follows one namespace over two and a half months:
1.0.0is published (initial) and takes effect after the propagation window.2.0.0(breaking) removes a policy action and opens a grace window.- During the grace window, a message valid only under
1.0.0is forwarded with aVHub-Verdictwarning that names the sunset instant. - After
enforced_fromplus the lease margin, the same message is rejected. - An agreement captured under
1.0.0keeps admitting transfers until1.0.0is revoked and the revocation takes effect.
All processes read the same file clock (-clock-file), so the whole timeline replays in seconds and gives the same table on every run.
4. Traceability Matrix
make trace runs conformance/trace, which regenerates TRACEABILITY.md and fails unless:
- every requirement maps to at least one module and one
T-*test, - every production package declares the requirements it implements, and
- every reachable catalog code has its negative case.
Packages declare their requirements in the two-line header comment of each file, which is where the generator reads them.
5. Specification Documents
| Path | Content |
|---|---|
spec/schemas/ | Normative JSON Schemas of Appendix A (listing, record, client configuration, verdict event, rules, manifest) and the A.5 context. |
spec/examples/ | Example documents validated by the tests. |
spec/requirements.tsv | The requirement list. |
internal/core/codes/catalog.tsv | The code catalog. |
conformance/vectors/eddsa-jcs-2022/ | The W3C test vector for the cryptosuite. |
DECISIONS.md, OPEN_QUESTIONS.md | PoC decisions and specification observations. |