Alexandria
API & Development

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

DimensionCoverageWhere
Normative requirements81 / 81REQ-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 codes76 / 77One minimal negative case per code in conformance/ (TestN_EveryReachableCode).
Scenario F6all rowsTestE2E_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.md

T-* 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. 1.0.0 is published (initial) and takes effect after the propagation window.
  2. 2.0.0 (breaking) removes a policy action and opens a grace window.
  3. During the grace window, a message valid only under 1.0.0 is forwarded with a VHub-Verdict warning that names the sunset instant.
  4. After enforced_from plus the lease margin, the same message is rejected.
  5. An agreement captured under 1.0.0 keeps admitting transfers until 1.0.0 is 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

PathContent
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.tsvThe requirement list.
internal/core/codes/catalog.tsvThe code catalog.
conformance/vectors/eddsa-jcs-2022/The W3C test vector for the cryptosuite.
DECISIONS.md, OPEN_QUESTIONS.mdPoC decisions and specification observations.

On this page