SHIPPED prototype interoperability surface

ĀML Verifier Contract Snapshot

Independent verifiers should agree on an exact contract, not a vague version label.

Snapshot ID
aml-verifier-contract-2026-09-08-01

Immutable source commit
b1ff5a87c7b19ae6338503a58ab6257a5b2add0b

Canonicalization
sorted-json-v1

Witness artifact
aml-witness-bundle/1

What the snapshot locks

The snapshot binds the exact historical verifier CLI contract, witness/evidence/challenge/attestation schemas, canonicalization profile, vectors, golden witness artifact, conformance-result contract, and black-box harness target.

Reference reproduction

Reference runtimes: JavaScript · Python · Go · HTTP

All are maintained by the AML repository. They demonstrate cross-runtime reproduction but do not count as independent external witnesses.

External verifier count: 0

Challenge it

node scripts/run-verifier-conformance.mjs -- your-verifier

The black-box harness requires:

golden witness   → PASS
tampered receipt → FAIL
tampered challenge → FAIL
expired challenge → FAIL

Verification guide

Machine-readable snapshot

10-minute external verifier path

External verifier challenge

Why the commit matters

CI byte-compares every locked contract path against the immutable source commit. Silent changes to the active snapshot make the build fail. Intended contract changes require a new snapshot rather than redefining the old one.

Claim boundary

This is project-defined interoperability infrastructure. Snapshot agreement, a conformance PASS, or multiple matching verifiers do not establish standards-body approval, certification, institutional independence, official ĀML trademark authorization, policy correctness, or truth of declared interface intent.