Architecture

Status
Draft
Audience
System designers, Integrators

Reference architecture for CPHAR deployments — seal device, registry, verifier, oracle layer, and audit interface.

A CPHAR deployment is composed of five logical components. They can be implemented as separate services or co-located, but the trust boundaries between them should be explicit and documented.

Components

Seal device Cryptographic seal
Tamper-responsive hardware. Holds the non-exportable signing key. Records firmware measurement. Destroys or disables the key on tamper detection.
Registry Append-only seal registry
Records seal identities, lot commitments, manufacturer attestation, firmware measurement, status, and revocation. Publishes content-addressed snapshots.
Verifier Challenge-response verifier
Issues random nonces, validates SealAttestation messages, checks registry status, enforces freshness windows, evaluates claim constraints.
Oracle layer Inspection oracle
Bridges the human inspection process to the registry. Submits inspection records under audit controls and binds lot commitments to seal identities.
Audit interface Auditor read API
Read-only interface giving auditors registry inclusion proofs, attestation history, revocation events, and snapshot transparency-log proofs.

Detailed pages for each component will live under /docs/architecture/. This index will then function as the navigation root.