Rulebook

ADCR 0.1.0

Every file of version 0.1.0 of ADCR, the AI Decision Check Record, as published. This address is the value of the rulebook field in a record written under this version, and it is never overwritten.

Stability: development. Cite it as ADCR 0.1.0, classes <list>. What it is and how to use it: the Rulebook page.

The Markdown files link to each other in the layout of the zip, where the schemas sit under schema/. On this site each schema is at the address its own $id names, listed below.

The Rulebook and its schemas

spec/

The Rulebook to read in the browser, rendered from SPEC.md, with a link for every rule.

adcr-0.1.0.pdf

The same text as a PDF, printed from that page.

SPEC.md

The Rulebook source, in Markdown: every rule, the crosswalk to the law and the audit standards, the interpretation guide and Annex C.

GOVERNANCE.md

Working group, scope, decision process and the route towards a formal standard.

README.md

What the Rulebook is for, in one page.

LICENSE-SPEC.md

Community Specification License 1.0, for the text.

LICENSE-CODE.txt

Apache License 2.0, for the schemas, vectors and verifier.

NOTICE.md

Licences and attribution.

NOTICES.md

decision-record.schema.json

JSON Schema for one record.

export.schema.json

JSON Schema for an export.

producer-profile.schema.json

JSON Schema for the producer profile.

adcr-0.1.0.zip

All of these files in the repository layout.

The verifier and the test vectors

conformance/PROFILE.md

The suites a verifier runs, the rules each one exercises and the verdicts.

conformance/COVERAGE.md

Every rule that carries a MUST, the cases that exercise it, and the parts only the producer can attest. Also the citations checked against the Official Journal.

conformance/adcr_verify.py

The reference verifier. Python 3 standard library, plus OpenSSL for the token signature.

conformance/run_vectors.py

Runs every published vector and reports pass or fail per case.

conformance/generate_vectors.py

Regenerates the vectors from fixed inputs and the committed tokens.

conformance/make_test_authority.py

Creates the test timestamp authority the vector tokens come from.

conformance/vectors/README.md

What each vector case proves and how to regenerate it.

Each suite's expected.json names every case with its expected verdict and findings; the cases sit beside it under cases/, and all of them are in the zip.

record_v1/expected.jsonRequired fields, number form, content-free and person-safe records, keyed commitments, locators, decisions, fallbacks, failures, classification, legal holds.
law_v1/expected.jsonRule references, ELI and national provisions, checked and caller-asserted provisions, rule set digests.
chain_v1/expected.jsonThe write-time chain: edits, removals, insertions, broken links, unchained and pre-chain rows, backdating.
anchor_v1/expected.jsonAnchor statements and every RFC 3161 token step, and the refused verdict without trust anchors.
oversight_v1/expected.jsonHuman oversight records, the proposal and final action pair, dual verification, oversight evaluation.
rights_v1/expected.jsonDecisions about a person: legal basis, decision mode, notice, explanation inputs, contests, notices, incidents.
export_v1/expected.jsonThe envelope: required fields, signatures, summaries that must match the records, content-free exports.
profile_v1/expected.jsonThe producer profile, and an export that disagrees with it.
interactions_v1/expected.jsonTwo failure axes in one export (advisory).
keys/trust-anchors.pemThe test trust anchor to pin with --trust-anchors. Test material only.

The text is licensed under the Community Specification License 1.0; the schemas, the vectors and the verifier under Apache-2.0.