Skip to main content

Non-Claims

The following capabilities are explicitly not claimed.

Q&A

Does Zen Mesh claim exactly-once delivery? No. Delivery guarantees are scenario-specific — no global exactly-once claim is made.

Does Zen Mesh guarantee loss-free delivery? No. Delivery guarantees are scenario-specific and local/mock only.

Does Zen Mesh claim generic zero-trust? No. Trust is scoped to specific mechanisms (enrollment, mTLS, HMAC, ZenLock). See the zero-trust proof matrix.

Does Merkle serve purposes beyond evidence integrity? No. Merkle provides evidence integrity and state comparison only. See Merkle integrity.

Are local/mock proofs the same as production validation? No. All proofs are local/mock unless stated. Production validation gates are planned.

Runtime

ClaimStatusWhy
Exactly-once deliveryNot claimedDelivery guarantees are scenario-specific
Zero-loss deliveryNot claimedAll proofs are local/mock
General at-least-onceNot claimedALO proven only for listed scenarios
CP outage autonomyNot claimedOutage proof is local/mock only
Global relay HA or failoverNot claimedFailover is one-to-one only
Private-edge autonomyNot claimedUses mock_data
Global topology convergenceNot claimedAll convergence proofs are local/mock

Trust

ClaimStatusWhy
Generic zero-trustNot claimedScoped to specific mechanisms
Production zero-trustNot claimedAll proofs are local/mock
Production mTLS/cert rotationNot claimedNo live execution evidence
SVID/SPIFFE rotationNot claimedSPIRE not deployed
Emergency revocationNot claimedNo automated playbook
Trust bundle rotationNot claimedNo implementation
Merkle auth/replay/identity/deliveryNot claimedEvidence integrity only

Compliance

ClaimStatus
PCI DSS compliantNot claimed
HIPAA compliantNot claimed
FedRAMP authorizedNot claimed
SOC 2 certifiedNot claimed
ISO certifiedNot claimed

Machine-Readable

See /ai/evidence/v1/non-claims.json for the full machine-readable list.