Schemas & Contracts
DigiEmu Core uses explicit machine-readable contracts so that verification behavior can be integrated without depending on human-readable CLI output.
Contract categories
Section titled “Contract categories”Snapshot contract
Section titled “Snapshot contract”Defines the deterministic state captured by Core.
Bundle contract
Section titled “Bundle contract”Defines the portable artifact that preserves snapshot state and associated evidence.
Verification contract
Section titled “Verification contract”Defines how a preserved bundle is independently checked.
Replay contract
Section titled “Replay contract”Defines reconstruction behavior for preserved state.
Result contract
Section titled “Result contract”Defines machine-readable verification output consumed by other systems.
Verification result
Section titled “Verification result”Typical verification information includes:
okrefexpectedgothash_algcanonical_scopetracemessage
Why contracts matter
Section titled “Why contracts matter”Stable contracts allow DigiEmu Core to be used by:
- shell scripts
- CI pipelines
- desktop applications
- governance systems
- audit tooling
- backend services
- independent verification tools
without parsing presentation-oriented text.
Compatibility principle
Section titled “Compatibility principle”Human-readable output can evolve.
Machine-readable contracts require much stronger compatibility discipline.
That distinction allows the CLI experience to improve while preserving automation and verification integrations.
Integration pattern
Section titled “Integration pattern”Application ↓Core CLI / Interface ↓Machine-readable Result ↓Consumer ├── CI ├── Arca ├── Audit Tool ├── Governance Layer └── External VerifierContinue with CLI Contract →.