Documented relationship
A harness test is connected to a requirement in the crosswalk. This is a research mapping, not a result for any target.
What this reference is for
Use this guide to distinguish a documented requirement relationship from a recorded test run and from independent review. Those are different states of evidence. Treating them as interchangeable is how a useful crosswalk turns into an unsupported readiness claim.
Repository snapshot
603unique test IDs reported by the repository count script
4wire protocols represented: MCP, A2A, L402, and x402
19 / 20testable 2026-Q1/Q2 requirements with a documented mapping
Q3currency delta reviewed July 16, 2026, with code-generation scope still pending
Claims model
Three states that should not be collapsed
Recorded observation
A stated target and pinned revision were run with retained inputs, environment details, timestamps, and output.
External judgment
A qualified party assessed the retained evidence and its applicability to the target and relevant standard version.
Practical workflow
From a requirement to reviewable evidence
Select
Identify the requirement and the applicable AIUC-1 version.
Choose
Select mapped tests and define the authorized target and scope.
Pin
Record the harness revision, dependencies, and invocation.
Retain
Keep inputs, outputs, environment details, and null or negative results.
Review
Seek independent assessment before making a third-party or conformity claim.
Evidence taxonomy
Match the language to the retained evidence
E1Observation
E2Runtime characterization
E3Enforcement
E4Persistence and replay resistance
E5Isolation and security boundary
A lower evidence class does not support language reserved for a higher one. A mapping alone is E1-level material, not evidence that a test passed or a control enforced a policy.
Primary artifacts
AIUC-1 crosswalk
Requirement-to-test relationships and current claim boundaries.
Test inventory
Module-by-module inventory and the reproducible count command.
Quick start
Installation and bounded execution guidance.
Evidence-class taxonomy
Permitted language and the evidence each claim class requires.
Release history
Versioned releases for pinning and reproducibility.
Q3 currency note
Known changes, pending scope decisions, and citation limits.
Boundary
This is a noncommercial research reference. The harness and crosswalk can support evidence collection relevant to a readiness review. They do not certify a system, determine compliance, or substitute for independent assessment of the specific target and standard version.