Secure Architecture
Secure separates protected evidence from the application that originally produced it.
Conceptual architecture
Section titled “Conceptual architecture”Application ↓Explicit State ↓┌─────────────────────────────┐│ SECURE BOUNDARY ││ ││ Canonicalization ││ Integrity Identity ││ Evidence Record ││ Signature / Attestation ││ Verification Rules │└─────────────────────────────┘ ↓Portable Evidence ↓Independent VerifierPrinciple 1 — Explicit state
Section titled “Principle 1 — Explicit state”Integrity-sensitive operations should depend on explicit inputs rather than hidden mutable state.
Principle 2 — Stable representation
Section titled “Principle 2 — Stable representation”Hashing and signing require a precisely defined representation.
Otherwise two implementations may hash semantically identical data differently.
Principle 3 — Separation
Section titled “Principle 3 — Separation”The system creating evidence should not be the only system capable of verifying it.
Principle 4 — Fail closed
Section titled “Principle 4 — Fail closed”Where integrity is required, an ambiguous or incomplete verification result should not silently become PASS.
Principle 5 — Evidence preservation
Section titled “Principle 5 — Evidence preservation”Verification artifacts should remain inspectable after the original application session has ended.
Continue with Integrity Model →.