Evidence Protection

Evidence becomes useful when another party can inspect and verify it after the original execution has ended.

Evidence package

A protected evidence package can conceptually contain:

evidence/
├── manifest.json
├── artifact.json
├── verification-result.json
├── checksums.sha256
├── signatures/
└── metadata/

The exact DigiEmu Secure package format must be defined by its published contract.

Evidence protection should support:

Historical evidence should not be silently rewritten.

If a corrected artifact is created, the safer model is typically:

Evidence v1
    ↓
Correction / Superseding Evidence
    ↓
Evidence v2

rather than replacing v1 without record.

Transport should not change the evidence being verified.

A recipient should be able to calculate integrity identities independently after receipt.

A verifier should not mutate evidence in order to make verification pass.

Security design should distinguish:

These are related but not identical concerns.