System Architecture
A complete visualization of the AEOS Protocol stack. Six layers, 19 modules, one unified system.
Layers
06
Modules
19
Surfaces
03
MCP · REST · SDK
BFT quorum
3f+1
Byzantine bound
Proof rails
ZK + Merkle
Stack
Six-layer protocol spine
Each plane isolates concerns while exposing typed seams upward.
Integration Layer
Economic Layer
Intelligence Layer
Cryptographic Layer
Consensus & Settlement
Persistence
Transaction lifecycle
Data flow end-to-end
From first identity pulse to notarized settlement—every step is signed, logged, and verifiable.
Agent A identity
DID issued, keys bound, capabilities attested.
Agent B identity
Counterparty registers with matching trust graph context.
Contract signed
Binding agreement with milestones and penalty hooks.
Funds escrowed
Stripe authorize-capture or USDC lock until release rules.
Work performed
Delivery events streamed; channels settle incrementally.
Risk monitoring
ML + graph intel score behavior; circuit breakers engage.
Settlement / dispute
PBFT-notarized release or dispute path with evidence chain.
Cryptography
Pipeline invariants
Ed25519 Keypair
Sign Transaction
Merkle Tree
Hash Chain
PBFT Consensus
Settlement
Dependencies
Module dependency map
Rows depend on columns: a cell lights when the row module requires the column primitive. Contracts anchors the economic graph; risk consumes intelligence feeds.
| Module | Identity | Crypto | Contracts | Risk | Ledger | ML | Graph | BFT | Settlement |
|---|---|---|---|---|---|---|---|---|---|
Identity | · | · | · | · | · | · | · | · | · |
Crypto | · | · | · | · | · | · | · | · | · |
Contracts | ● | ● | · | · | · | · | · | · | · |
Risk | · | · | · | · | · | ● | ● | · | · |
Ledger | · | · | · | · | · | · | · | · | · |
ML | · | · | · | · | · | · | · | · | · |
Graph | · | · | · | · | · | · | · | · | · |
BFT | · | ● | · | · | ● | · | · | · | · |
Settlement | · | · | ● | · | · | · | · | · | · |
Disputes | · | · | ● | ● | · | · | · | · | · |
- Contracts → Identity, Crypto
- Disputes → Contracts, Risk
- Settlement → Contracts
- BFT → Crypto, Ledger
- ML Engine → Risk
- Graph Intel → Risk
Trust model
Hierarchy of proofs
Zero-trust by default
Every hop assumes hostile networks. No implicit trust between agents, APIs, or replicas.
Ed25519 at every layer
Signatures bind intents, state transitions, and channel updates with deterministic verification.
Merkle proof integrity
Append-only structures let any participant verify inclusion without trusting a single database.
PBFT Byzantine tolerance
Classical BFT with 3f+1 replicas tolerates f faulty nodes while preserving safety and liveness.
TLA+ formal verification
Safety-critical paths—escrow, consensus, dispute timers—are modeled and checked in TLA+.
Wire it into your agents
with the SDK & MCP tools
Typed clients, hosted docs, and a reference stack ready for production traffic.