Framework overview
Open formats · Test kitv0.1 · Draft for public comment · OCC-E-021 · 2 Oct 2026

Agent Record conformance test kit

Anyone who writes or reads OCC Agent Records needs to agree on what a well-formed record is. This kit gives you 20 fictional test records with the expected verdict for each, the profile rules behind them, and a checker that runs in your browser. Use it to test your own tooling, or to check a record before you publish it.

Test vectors

Run the vectors

Each vector is a complete record with one thing changed. A checker passes a vector when its verdict matches expect and it reports the listed code. Codes starting schema: are JSON Schema 2020-12 keywords; OCC-R codes are the profile rules below.

IDCaseExpectCodeResult
V01Full recordThe published example with every optional block filled.valid–not run
V02Minimal recordOnly required fields; optional blocks removed.valid–not run
V03Record with a disclosed incidentAn incident coded under the Incident & Disclosure protocol.valid–not run
V04Withdrawn evidence stays listedWithdrawn evidence is recorded, not erased.valid–not run
V05Missing principalEvery record says on whose behalf the agent acts.invalidschema:requirednot run
V06Unknown authority ceilingThe ceiling uses one of the seven named levels.invalidschema:enumnot run
V07Horizon out of rangeAIH-12 runs from H1 to H12.invalidschema:patternnot run
V08Date in the wrong formatDates are written YYYY-MM-DD.invalidschema:formatnot run
V09Impossible calendar date30 February does not exist.invalidschema:formatnot run
V10Malformed evidence digestA digest is sha256: followed by 64 lowercase hex characters.invalidschema:patternnot run
V11Wrong record versionThis kit checks version 0.1.invalidschema:constnot run
V12Declared authority as free textDeclared and effective authority are lists, so they can be compared line by line.invalidschema:typenot run
V13Threshold does not match horizonAn H5 agent is checked against T5 and E5.invalidOCC-R1not run
V14Reassessment date before issueA record cannot fall due before it exists.invalidOCC-R2not run
V15Evidence withdrawn before it was producedDates must run forwards.invalidOCC-R3not run
V16Incident detected before it occurredDates must run forwards.invalidOCC-R4not run
V17Incident severity outside S1–S4Severity uses the protocol scale.invalidschema:enumnot run
V18Unknown field inside OECD codingThe OECD block is closed so codes stay comparable.invalidschema:additionalnot run
V19Threshold not met, no gaps listedWell formed, but a reader cannot see what is missing. Raises a warning.validOCC-R5not run
V20GUARD level without a declarationWell formed, but the claim cannot be followed. Raises a warning.validOCC-R8not run
Download vectors.json

Free to use under the same terms as the OCC schemas. Every record uses example.org and invented names.

Profile rules

What the schema cannot say

The Agent Record schema and the Incident schema fix the shape of a record. These rules cover relationships between fields. Errors make a record not well formed; warnings flag something a reader will struggle to follow.

CodeLevelRule
OCC-R1errorThe AIT-12 threshold and AIE-12 profile carry the same number as the AIH-12 horizon (H5 → T5 → E5).
OCC-R2errorreassess_by is later than issued.
OCC-R3errorEvidence cannot be withdrawn before the date it was produced.
OCC-R4errorAn incident cannot be detected before it occurred.
OCC-R5warningIf the AIT-12 status is not "meets", the gaps are listed.
OCC-R6warningThe mandate has not already expired on the issue date.
OCC-R7warningThe revocation test date is not later than the issue date.
OCC-R8warningA GUARD level of GUARD 1 or above points to its F-ACT declaration.
OCC-R9warningrecord_id is a URL or URN, so others can cite it.
OCC-R10warningEvidence whose valid_until is before the issue date is stale and should be refreshed or withdrawn.
Checker

Check a record

Fetch a listed public record by its reference, or paste one. To check the register’s signature as well, use Verify a signed record.

Runs in your browser. Nothing you paste is sent anywhere.

Limits

What passing means

Well formed, not true
A record that passes is well formed and internally consistent. The kit does not check that the agent exists, that the operator is who it says, that the evidence is real or that the agent is safe or lawful. It is not certification, approval or endorsement, and passing gives no right to any mark. The kit tests record files, not AI systems or release pipelines.

Building the kit turned up ten schema errors in our own fictional example record, which have been corrected. If you find a vector you disagree with, raise it in the public review.