Conformance
Conformance determines whether an implementation or artifact satisfies an explicit verification contract.
A conformance definition may include
Section titled “A conformance definition may include”- required fields
- schemas
- canonicalization rules
- verification behavior
- failure behavior
- replay expectations
- integrity requirements
Why explicit contracts matter
Section titled “Why explicit contracts matter”Without an explicit contract, two implementations may both claim to verify the same artifact while applying different rules.
Conformance turns verification behavior into something that can itself be tested.
Technology-specific contracts
Section titled “Technology-specific contracts”Individual DigiEmu technologies may define their own schemas, CLI contracts or verification rules.
This cross-technology section describes the shared principles rather than replacing those technology-specific contracts.