Status
OPEN INTEROPERABILITY / WITNESS CHALLENGE
ĀML now ships the same aml-witness-bundle/1 verification contract across:
- browser/WebCrypto;
- Node/WebCrypto tests;
- a dependency-free Python verifier;
- the reference HTTP service.
Golden vector:
https://github.com/aruintelligence/aml-core/blob/main/independent/python/witness-vector.json
Public contracts:
Challenge
Implement verification in a third language/runtime (for example Rust, Go, Java, Swift, C#, Ruby, PHP, Kotlin, or another independent JavaScript implementation) without importing AML verifier internals.
Your verifier should:
- reproduce the published receipt SHA-256;
- reproduce the browser-evidence SHA-256;
- reproduce the public-JWK fingerprint;
- verify the P-256 ECDSA/SHA-256 signature;
- reproduce the whole witness-bundle SHA-256;
- accept the golden vector at
2030-01-01T00:05:00Z;
- reject a deliberately mutated purpose/decision;
- report any ambiguity in canonicalization or signature encoding.
Acceptance evidence
Reply with:
- public repository URL;
- language/runtime and version;
- PASS transcript for the golden vector;
- FAIL transcript for a deliberate mutation;
- any mismatch or ambiguity found.
A disagreement is useful specification feedback.
Claim boundary
The in-repo Python verifier is not counted as an external witness. A third-party reproduction would be external evidence of interoperability with this project-defined prototype contract; it would not constitute official certification, standards-body approval, regulatory compliance, or proof that declared AML meaning/scores are truthful.
Status
OPEN INTEROPERABILITY / WITNESS CHALLENGE
ĀML now ships the same
aml-witness-bundle/1verification contract across:Golden vector:
https://github.com/aruintelligence/aml-core/blob/main/independent/python/witness-vector.json
Public contracts:
Challenge
Implement verification in a third language/runtime (for example Rust, Go, Java, Swift, C#, Ruby, PHP, Kotlin, or another independent JavaScript implementation) without importing AML verifier internals.
Your verifier should:
2030-01-01T00:05:00Z;Acceptance evidence
Reply with:
A disagreement is useful specification feedback.
Claim boundary
The in-repo Python verifier is not counted as an external witness. A third-party reproduction would be external evidence of interoperability with this project-defined prototype contract; it would not constitute official certification, standards-body approval, regulatory compliance, or proof that declared AML meaning/scores are truthful.