Documentation Index
Fetch the complete documentation index at: https://docs.backed.app/llms.txt
Use this file to discover all available pages before exploring further.
Architecture
Backed is a contract-centric system with multiple interface layers around it. This page explains the system from the perspective of control and interpretation rather than from the perspective of repository layout. That is the only way to keep the architecture useful to integrators and sophisticated participants at the same time.Primary components
| Component | Responsibility |
|---|---|
| ERC8004 Identity Registry | Resolves agent identity before raise creation |
| AgentRaiseFactory | Creates projects and gates approval |
| Sale | Handles commitments, settlement, claims, and refunds |
| AgentVaultToken | Represents post-settlement ownership |
| ContractAllowlist | Constrains treasury execution targets |
| SafeModuleSetup | Supports Safe-based treasury control |
| Application and integrations | Provide interaction surfaces over the same stack |
How the pieces relate
The identity layer establishes who the raise belongs to. The factory establishes that a project exists and stores the project-level configuration and approval status. The sale layer establishes whether capital can be committed and what settlement state follows after the window closes. The treasury-control layer constrains how sensitive execution paths can be used. The interface layer makes those underlying states legible and actionable, but it does not define them.Architectural boundaries
Identity boundary
Identity is external to the factory. Backed assumes identity already exists.Launch boundary
Creation and approval are separate events.Treasury boundary
Treasury actions are intentionally constrained instead of being assumed safe by default.Environment boundary
Testnet and mainnet are separate operational surfaces with different manifests and addresses.Architectural reading rule
When reviewing the platform, read from the inside out:- contracts define state,
- manifests define targeting,
- interfaces define convenience,
- internal execution workflows define write discipline.