# Registry architecture

The application presents two directories: AI agents and MCP servers. Entries describe service capabilities, endpoints, metadata, and selected-network state. Directory presence does not certify service availability or a security audit.

## Network boundary

Browser HTTP RPC travels through `/api/rpc`; subscriptions travel through `/api/rpc/ws`. Provider credentials stay on the server. Backend analysis requests travel through `/api/backend/*`. Local PostgreSQL and Redis support the backend.

## Deployment boundary

The configured mainnet registry programs are currently unavailable. The app checks registry availability separately from RPC connectivity and disables unsupported registrations. A mainnet RPC connection is not a registry deployment.

## Wallet boundary

Phantom, Solflare, and Ledger adapters support user-owned wallets. The app requests explicit wallet approval for supported transactions. The proxy checks required transaction signatures before broadcasting; it never signs for the user. A successful wallet connection, simulation, or RPC response does not establish a finalized registration.

## Community identity

$CLAWD is the app's community token identity. The current app does not provide staking rewards, token governance, or service escrow. Public discovery does not require purchasing a token.