Independent verifier challenge: validate aml-browser-evidence/1 without importing aml-core runtime code

[aruintelligence]

Status

OPEN WITNESS / INTEROPERABILITY CHALLENGE

ĀML now publishes a browser evidence contract that binds a sealed aml-dom-receipt/1, strict-zone violations, page metadata, and SHA-256 integrity into aml-browser-evidence/1.

Reference docs:

• https://github.com/aruintelligence/aml-core/blob/main/docs/BROWSER_EVIDENCE.md
• https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-browser-evidence.schema.json
• https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-dom-receipt.schema.json
• https://aruintelligence.github.io/aml-core/browser-evidence-demo.html

Challenge

Implement a verifier in another repository or language that does not import docs/aml-browser-integrity.js, docs/aml-browser-evidence.js, or other AML verifier internals.

The implementation should:

1. accept an aml-browser-evidence/1 JSON object;
2. canonicalize objects by recursively sorting object keys while preserving array order;
3. recompute the receipt SHA-256 with its integrity member excluded;
4. reject a mutated receipt;
5. recompute the evidence SHA-256 with its outer integrity member excluded;
6. reject a mutated zone violation or receipt field;
7. document any ambiguity discovered in the public contract.

Acceptance evidence

Reply with:

• public repository URL;
• language/runtime;
• one valid verification transcript;
• one deliberate tamper rejection transcript;
• any incompatibility or ambiguity found.

A negative result is useful. If two implementations disagree, that is specification feedback.

Claim boundary

Passing this challenge demonstrates interoperability with the project-defined prototype evidence contract. It is not official certification, endorsement, regulatory compliance, or proof that declared purpose/attention/restoration values are truthful.