┌─────────────────────────────────────┐
│ Protocol HTTP · WS · RESP3 │
├─────────────────────────────────────┤
│ Edge Auth · Route · Meter │
├─────────────────────────────────────┤
│ Engine Hot · Akasha │
├─────────────────────────────────────┤
│ Persistence WAL · Snapshots │
├─────────────────────────────────────┤
│ Cross-cut Identity · Audit │
└─────────────────────────────────────┘
Layers. Nothing else.
Compressed stack
01Protocol
RESP3gRPCWebSocket
02Edge
AuthRouterMeterAudit
03Engine
AkashaKVHot CacheLSM
04Persistence
WALSnapshots
05Cross-cutting
IdentityAudit ChainTelemetry
Request path
Protocol↓
Edge
Engine
Persistence
Cross-cutting
REQUEST ↓Step 1/9
Protocol
Client → RESP3 SET
Layer details
What each layer does.
01
Protocol
Wire formats. TLS 1.3 terminates here. Three protocols on one port.
RESP3gRPCWebSocket
02
Edge
Validation. DID identity resolved. Purpose-aware routing. Pre-execution audit log.
AuthRouterMeterAudit
03
Engine
Storage. Dual-mode AkashaKV combines hot-cache reads with LSM-tree durability.
AkashaKVHot CacheLSM
04
Persistence
Durability. Write-ahead log with configurable fsync. Point-in-time recovery.
WALSnapshots
05
Cross-cutting
Runs at every layer. W3C DID, BLAKE3 hash chain, OpenTelemetry traces.
IdentityAudit ChainTelemetry
Five layers. One request path.
Every byte that enters Zaps passes through all five. No shortcuts. No bypasses. That is the architecture.