Layer Breakdown

Every request flows through identity, policy, and execution stages before reaching external systems, ensuring that authorization and payment logic are applied consistently across all channels.

Logical Stack

1

Client Layer

Web, mobile, SDKs, and partner APIs. The entry point for all user and agent interactions.

2

Identity Layer (SIWX)

Sign-In-with-X for users and agents, based on cryptographic signatures over structured messages. Generalizes SIWE across auth providers and agent types.

3

Control Plane

Auth, Agent, Policy, Payment, Execution, and Trust services that normalize actions, evaluate rules, orchestrate payments, and maintain system state.

4

Account Layer (ERC-4337 / EIP-7702)

Brain smart accounts and EIP-7702 delegation contracts that enforce constraints and validate execution at the account level.

5

Trust Layer (ERC-8004)

Agent registry and reputation contracts providing portable identity, validation records, and composable trust signals.

6

Execution Layer

Integrations with trading, lending, payment, and job/escrow protocols, including ERC-8183-compliant job contracts for conditional commerce.

7

Infrastructure

Base and Ethereum networks, RPC providers (Alchemy), AI services, and compliance tooling.

Request Lifecycle

Client Request
    ↓
Identity Verification (SIWX + ERC-8004)
    ↓
Policy Evaluation (static rules + dynamic conditions)
    ↓
Payment Handling (x402, if required)
    ↓
Execution Routing (on-chain or off-chain)
    ↓
UserOperation → Bundler → EntryPoint → BrainAccount
    ↓
Result + Receipt Recorded
    ↓
Reputation Updated (ERC-8004)

Layer Interactions

From	To	Mechanism
Client	Identity Layer	SIWX signature verification
Identity Layer	Control Plane	Scoped session token
Control Plane	Account Layer	UserOperation construction
Account Layer	Trust Layer	Validation record writes
Control Plane	Execution Layer	Routed action calls
Execution Layer	Infrastructure	On-chain tx via bundler

Each layer exposes well-defined interfaces so that external systems, wallets, and agents can integrate without custom coupling.