Five Layers, One Atlas

Sean Neville — cofounder of Circle, architect of USDC, now CEO of Catena Labs — published a thesis at a16z crypto identifying five infrastructure layers that blockchains provide for AI agents. The argument is structural: as agents take on more economic activity, the systems that govern identity, payments, trust, governance, and user control must shift from human-mediated to architecturally enforced. The question is where, specifically, these requirements land in the transaction lifecycle.

The Atlas maps that. The diagram below places each of Neville’s five pillars on the eight-stage STP sequence — Intent through Finality — and marks the compliance checkpoints where each pillar’s infrastructure requirements intersect with regulatory obligations. Hover any checkpoint to see what fires.

Identity for Non-Humans

The first pillar is agent identity. Neville frames this as KYA — Know Your Agent — the non-human equivalent of KYC. The Atlas’s KYA section maps five checkpoints across the STP sequence: DID resolution at Identity (S2), delegation verification at Identity–Discovery (S2–S3), capability-envelope evaluation at Discovery–Negotiation (S3–S4), a seven-stage compliance pipeline spanning Identity through Facilitation (S2–S7), and credential health monitoring at Finality (S8).

The compliance gravity concentrates early. Three of the four active checkpoints on the Identity pillar are gates — hard stops that must clear before the journey proceeds. The fourth, Credential Health, is a post-settlement obligation: the ongoing duty to ensure cryptographic material has not been compromised or rendered quantum-vulnerable. The dashed stroke marks it as policy-enforced — no smart contract watches your key rotation schedule.

Atlas sections: KYA · DID Resolver · Delegation Explorer Vendors: Catena Labs (ACK-ID, ACK-Pay, Rulebooks), Coinbase (AgentKit)

Filling Gaps in Payment Systems

The payments pillar is the densest band on the diagram — seven checkpoints across all eight stages. This is the x402 payment flow: agent opens wallet, discovers price, negotiates via HTTP 402, signs a gasless EIP-3009 transfer, clears CDP sanctions screening, facilitates Travel Rule transmission, and settles on Base in approximately two seconds.

The Atlas’s A1 path maps this journey step by step. The x402 compliance middleware — a Cloudflare Worker deployed at x402-middleware.stablecoinatlas.com — implements six of these seven checkpoints as a reference pipeline. Five are gates. The only monitors sit at Discovery (price observation, no compliance action) and Facilitation (Travel Rule logging).

a16z reports approximately $1.6 million per month in agent-driven x402 payments. The compliance question is not whether these payments will scale, but whether the compliance architecture will be in place when they do.

Atlas sections: x402 Path · x402 Middleware · Agentic Rail Vendors: Coinbase (Smart Wallet, CDP, AgentKit), Circle (USDC), Cloudflare (Workers, KV, D1, R2)

Governing AI-Run Systems

The governance pillar spans the full lifecycle with a distinctive pattern: gates in the first half, obligations in the second. Intent scoping (S1) is a policy-enforced gate — GENIUS §3 determines whether a transaction falls under federal or state oversight based on the $10B issuer threshold. Identity (S2) carries the heaviest compliance gravity in the entire Atlas: five gate checkpoints. Transport (S5) runs OFAC screening at the edge. Authorization (S6) verifies reserves and capability envelopes.

Then the pattern shifts. Facilitation (S7) and Finality (S8) carry obligations, not gates — Travel Rule transmission, SAR filing, attestation publication, Verifiable Credential receipt storage. The Atlas’s Compliance Surface visualizes this asymmetry across all 53 paths: gates accumulate before the state change; obligations radiate after it.

Atlas sections: GENIUS Act · Compliance Surface · STP Resolver Vendors: Coinbase (CDP screening), Cloudflare (edge-deployed Worker middleware)

Repricing Trust

Neville’s fourth pillar argues that when execution costs approach zero, verification becomes the scarce resource. The Atlas renders this as the KYT (Know Your Transaction) layer: continuous monitoring that turns raw blockchain data into compliance evidence.

The trust band starts with attestation at Identity (S2) — the KYA compliance pipeline’s signed audit trail. Screening gates fire at Negotiation (S3) and Authorization (S6). Between them, a policy-enforced monitor at Transport (S5) watches for AML patterns — transaction velocity, counterparty clustering, structuring detection. The dashed stroke on that checkpoint is the honesty marker: no smart contract detects structuring. A human analyst reviews flagged patterns.

The band ends with two obligations: KYT logging at Facilitation (S7) and zero-knowledge proofs at Finality (S8). The ZK checkpoint is the endgame Neville describes — prove compliance without revealing underlying data. The Atlas maps this at StableZKP.com, and the KYA page frames the three-layer stack: identity (StableDID.com) → compliance (StableKYA.com) → privacy (StableZKP.com).

Atlas sections: KYT · ZKP · KYA Pipeline Vendors: Circle (USDC attestations), Cloudflare (edge verification, R2 receipt storage)

Preserving User Control

The fifth pillar is about scoped delegation — ensuring that when users hand authority to agents, the boundaries are architecturally enforced rather than merely promised. The Atlas maps this through the KYA delegation tree and the VASP registration framework.

The pattern here is notable: four of five checkpoints are code-enforced. Scope (S1), Attenuate (S4), and Enforce (S6) are all gates implemented at the smart-contract level. The single monitor — Bind at Identity (S2) — is also code-enforced. Only the final checkpoint, Audit (S8), is a policy-enforced obligation. This pillar is the most architecturally trustworthy of the five: the constraints are baked into the contracts, not dependent on off-chain process.

Atlas sections: KYA Delegation · Capability Simulator Vendors: Catena Labs (ACK Rulebooks), Coinbase (AgentKit)

What the Diagram Shows

Read the five bands together and a pattern emerges. Identity (S2) is the most congested column — every pillar has at least one checkpoint there. Finality (S8) is the second most congested, but its checkpoints are predominantly obligations and proofs rather than gates. The compliance architecture front-loads its gates (stop and verify) and back-loads its obligations (record and prove).

This is the same asymmetry the Atlas documents across all 53 paths. The STP model is the constant. The pillars are a lens. The compliance checkpoints are the terrain.