Skip to main content

Key Concepts

Architecture

ConceptDescription
Control PlaneSaaS layer — manages configuration, policy, and evidence. Never in the delivery path.
Data PlaneEdge infrastructure — ingesters, egresses, bridges that route events.
Edge PlaneCustomer-managed clusters running zen-agent and zen-egress.

Delivery Paths

PathDescriptionEvidence
DirectIngester → public targetPROOF-001, 003, 004
RelayIngester → egress (mTLS) → NAT/firewalled targetPROOF-008, 009
Private EdgeEdge source → private_edge path → mock data targetPROOF-010

Trust Mechanisms

MechanismDescriptionEvidence
mTLSMutual TLS on all internal pathsTRUST-PROOF-004, 006
HMACPayload integrity via SHA-256 signatureTRUST-PROOF-003
SPIFFEWorkload identity via URI SAN in certsTRUST-PROOF-004
ZenLockCiphertext-only secret managementTRUST-PROOF-005, 009
EnrollmentK8s cluster registration via age-encrypted bundleTRUST-PROOF-001, 002

Evidence Model

ConceptDescription
Evidence PackConsolidated JSON with proof status, refs, non-claims
Victory LockCommit-pinned proof artifact with validation commands
Proof LedgerIndex of all proofs with scenarios and statuses
Replay VerifierValidator checking all artifacts and claims guard
State MachineTransition model for delivery, connectivity, topology, buffer
Non-ClaimsExplicitly unclaimed capabilities (not false, just not proven)

Status Classifications

StatusMeaning
victory_lockedProof committed, verified, witnessed
local_mock_provenDemonstrated in deterministic mock harness
implementation_presentCode exists but no execution proof artifact
plannedDesign documented, implementation not started
blockedCannot proceed due to known blocker
not_claimedExplicitly not claimed
supports / maps_toCompliance relationship (not certification)