External verifier quorum challenge: produce a public aml-verification-report/1

[aruintelligence]

Status

OPEN EXTERNAL WITNESS / INTEROPERABILITY CHALLENGE

The next milestone cannot be satisfied by more in-repository reference implementations.

ĀML now publishes a deliberately narrow outside-verifier path:

• aml-witness-bundle/1
• aml-verification-report/1
• aml-verifier-manifest/1
• aml-verification-quorum/1
• aml-signed-verification-report/1
• aml-signed-verification-quorum/1
• protocol/aml-verifier-cli.md
• a black-box conformance harness
• JavaScript, Python, and Go reference verification paths
• a public WITNESSES.json registry that intentionally starts at zero external witnesses

Fast path

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

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

Black-box harness:

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

Your verifier must accept:

your-verifier --now 2030-01-01T00:05:00Z bundle.json

and emit JSON containing:

{"valid":true,"reason":"YOUR_REASON"}

Challenge

Implement or operate a verifier outside aruintelligence/aml-core and publish a machine-readable aml-verification-report/1 over the canonical golden witness vector:
https://github.com/aruintelligence/aml-core/blob/main/independent/python/witness-vector.json

The harness requires:

1. golden vector -> PASS;
2. tampered receipt purpose -> FAIL;
3. tampered challenge -> FAIL;
4. expired challenge -> FAIL.

Reference implementations for comparison only:

• Python: https://github.com/aruintelligence/aml-core/blob/main/independent/python/verify_witness.py
• Go: https://github.com/aruintelligence/aml-core/blob/main/independent/go/main.go
• verifier matrix: https://github.com/aruintelligence/aml-core/blob/main/docs/VERIFIER_MATRIX.md

Public contracts:

• https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-verifier-cli.md
• https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-verification-report.schema.json
• https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-verifier-manifest.schema.json
• https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-verification-quorum.schema.json
• https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-verifier-conformance-result.schema.json
• https://github.com/aruintelligence/aml-core/blob/main/protocol/sorted-json-v1.md

Acceptance evidence

Reply with:

1. public source/repository URL;
2. verifier/runtime name and version;
3. exact artifact hash you verified;
4. your aml-verification-report/1 JSON;
5. black-box harness output;
6. PASS or FAIL result;
7. one deliberate mutation and the result;
8. any disagreement with the reference implementations.

Negative results are welcome.

Witness registry

If the evidence is publicly reproducible and maintained outside this repository, it can be proposed for the machine-readable WITNESSES.json registry.

Claim boundary

A witness record is evidence of a reported external reproduction. It is not official certification, standards-body approval, regulatory compliance, proof of verifier independence beyond the supplied public evidence, trademark authorization, or proof that AML's declared inputs are objectively true.