KB009 · architecture reference
Designed so no server holds your data
Evrylife's architecture is designed for full decentralization: no centralized server holding user data or controlling access. The ECP specifies 39 modules across 4 tiers. The app is currently in bootstrap; this page describes the constitutional target being built toward.
The data layer
The architecture specifies that all member data lives in OrbitDB stores on IPFS +
libp2p. Each ECP domain maps to an OrbitDB store (document or event-log). Identity
is a wallet did:pkh → did:key; the wallet signs writes, so the member —
not a company — controls their data.
- A member acts in the frontend.
dataServicewrites to the domain's OrbitDB store, signed by the wallet's did:key.- The write replicates peer-to-peer over IPFS/libp2p; a community indexer aggregates stores for global feeds and the explorer.
- Media is pinned to IPFS for durability — Storacha, Filecoin, or Arweave; member key first, DAO free tier as fallback.
- Lit Protocol encrypts private content client-side before storage.
dataService.
The integration stack
| Protocol | Purpose | ECP reference |
|---|---|---|
| OrbitDB on IPFS + libp2p | Mutable data layer | All modules |
| IPFS | Content-addressed storage | E004 |
| Filecoin | Long-term persistence | E004 |
| Arweave | Permanent storage | E004 |
| Storacha | Fast pinning | E004 |
| Lit Protocol | Encryption + access control | E011 |
| Semaphore | Zero-knowledge proofs | E011 |
| OrbitDB / libp2p (ECIES) | Encrypted messaging | E017 |
| Hyperlane | Cross-chain bridging | E001, SC005–006 |
| ENS | Name resolution | E005 |
Module tiers
Core protocol
The foundation layer.
Content type modules
What members create, publish, and sell.
Infrastructure
Governance plumbing and member signals.
Optional / gated
Community-gated modules.
The Web3 Meta Tree
The classification system organizing all content, locations, topics, and breakdowns — a taxonomy of 31,152 nodes across 4 pillars, counted from the protocol's taxonomy registry (governed by zkr-POGO consensus after bootstrap):
| Pillar | Top-level categories | Classification nodes | Max depth |
|---|---|---|---|
| Topics | — | 19,829 | 14 |
| Locations | — | 6,745 | 5 |
| Content Types | 17 | 3,781 | 10 |
| Breakdowns | — | 797 | 7 |
There are 17 top-level content types (videos, images, channels, events, places, etc.). Each fans out into subcategories — for example, "Videos" branches into music videos, tutorials, vlogs and so on — totalling 3,781 classification nodes. All meta tree changes are zkr-POGO-gated and require an EAIP after bootstrap.
The AI layer
The ai_agents_registry lists 11 agents:
task agents handle automated advisory work, and a guardian agent enforces the immutable floor.
The Constitution requires all AI models to run on decentralized infrastructure — Akash, Bittensor, Gensyn, or local nodes. During bootstrap, centralized AI APIs may be used while the decentralized stack matures. Agents advise; consensus decides.