Adversarial contract migration challenge: find a way future AML could rewrite old evidence

[aruintelligence]

Status

OPEN ADVERSARIAL REVIEW CHALLENGE

AML now publishes an immutable verifier contract snapshot plus explicit contract-evolution machinery.

Current snapshot:

• aml-verifier-contract-2026-09-08-01
• source commit b1ff5a87c7b19ae6338503a58ab6257a5b2add0b
• current migration count: 0

Evolution page:
https://aruintelligence.github.io/aml-core/contract-evolution.html

Machine surfaces:

• catalog: https://github.com/aruintelligence/aml-core/blob/main/protocol/verification-contract-catalog.json
• lineage: https://github.com/aruintelligence/aml-core/blob/main/protocol/verification-contract-lineage.json
• migration schema: https://github.com/aruintelligence/aml-core/blob/main/protocol/aml-verification-contract-migration.schema.json
• historical verification rule: https://github.com/aruintelligence/aml-core/blob/main/docs/HISTORICAL_VERIFICATION.md

Challenge

Find a realistic future verifier change where this migration model could allow an old artifact to be silently reinterpreted or falsely presented as compatible.

Useful attack areas:

1. canonical JSON changes;
2. signature encoding changes;
3. challenge freshness semantics;
4. schema field defaults;
5. optional fields becoming required;
6. changed error handling;
7. removed locked paths;
8. adapters that alter historical meaning;
9. implementation claims targeting the wrong snapshot;
10. ambiguous compatibility classifications.

Required submission

Publish:

• the hypothetical or real contract change;
• old behavior;
• proposed new behavior;
• expected classification: backward-compatible / conditionally-compatible / breaking;
• how an old artifact should verify historically;
• the exact ambiguity or exploit you found.

Negative results are welcome. A finding that forces AML to version a future contract more carefully is a successful result.

Boundary

Migration classification is project-defined interoperability metadata. It is not standards-body certification, regulatory approval, trademark authorization, or proof that the underlying interface declarations are objectively true.