External immutable-snapshot challenge: implement aml-verifier-contract-2026-09-08-01

[aruintelligence]

Status

OPEN EXTERNAL INTEROPERABILITY CHALLENGE

AML now publishes an immutable verifier contract snapshot:

• snapshot id: aml-verifier-contract-2026-09-08-01
• source commit: b1ff5a87c7b19ae6338503a58ab6257a5b2add0b
• snapshot manifest: https://github.com/aruintelligence/aml-core/blob/main/protocol/verification-contract-v1.json
• human-readable page: https://aruintelligence.github.io/aml-core/verifier-contract.html

Challenge

Implement this exact snapshot in a repository maintained outside aruintelligence/aml-core.

Do not target a vague label such as "latest AML verifier v1." Bind your implementation to the exact snapshot ID and immutable source commit above.

Required evidence

Publish:

1. public source repository;
2. aml-verifier-implementation-claim/1 JSON;
3. runtime and version;
4. black-box conformance command;
5. aml-verifier-conformance-result/1 JSON;
6. PASS/FAIL for the golden vector;
7. receipt-mutation result;
8. challenge-mutation result;
9. expired-challenge result;
10. any disagreement with the snapshot or reference implementations.

Fast path

Verification entry:
https://github.com/aruintelligence/aml-core/blob/main/VERIFY.md

10-minute guide:
https://github.com/aruintelligence/aml-core/blob/main/docs/EXTERNAL_VERIFIER_10_MINUTES.md

Starter kit:
https://github.com/aruintelligence/aml-core/tree/main/starters/verifier

Black-box harness:

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

Important

Negative results are welcome. A disagreement is valuable protocol evidence.

An implementation claim is a declaration of target compatibility. A conformance result is observed executable behavior. A witness record requires reproducible public outside evidence. None of these objects is standards-body certification, official AML trademark authorization, proof of organizational independence, regulatory compliance, or proof that declared interface intent/scores are objectively true.