Visual System

The Two-Model
System

How to read the Cartography of Compliance. Every compliance mechanism in the stablecoin ecosystem carries five simultaneous readings — domain, depth, stage, checkpoint, and enforcement. Two spatial models make this complexity legible.

Five Readings

Every compliance mechanism encodes five properties simultaneously

Color tells you the compliance domain. Position tells you the depth or stage. Shape tells you the checkpoint type. Fill treatment tells you the enforcement mechanism. A badge tells you who owns it. Learn to read any one of these and you can decode every diagram across the Atlas.

DOMAIN COLORS — 7 compliance domains + neutral
Neutral
\u00b7 S1 Intent
Identity
T6 \u00b7 S2 Identity
Discovery
T4 \u00b7 S3 Discovery
Reserves
T2 \u00b7 S4 Negotiation
Transfer
T5 \u00b7 S5 Transport
Execution
T3 \u00b7 S6 Authorization
Token
T1 \u00b7 S7 Facilitation
Reporting
T7 \u00b7 S8 Finality
CHECKPOINT SHAPES — 3 relationships to the state transition
Gate
Pre-condition check \u2014 blocks if it fails
solid = code-enforced \u00b7 hollow = policy-enforced
Monitor
Concurrent observer \u2014 watches without halting
solid = code-enforced \u00b7 hollow = policy-enforced
Obligation
Post-settlement consequence \u2014 reports after the fact
solid = code-enforced \u00b7 dashed = policy-enforced
ENFORCEMENT MARKERS — code vs. policy
Code-enforced
Compiled into chain logic \u2014 cannot be bypassed.
Solid border + filled shape
Policy-enforced
Depends on external actor \u2014 can be bypassed.
Dashed border + hollow shape

Model 1 — Vertical

How deep does compliance run?

Stack Diagrams use Build LLC section-cut conventions to reveal the architectural depth of compliance mechanisms. Five horizontal layer bands represent the chain stack from L1 Network to L5 Application. Compliance blocks sit at the layer where they execute — their vertical position is the answer to "how embedded is this?"

Base L2 \u2014 Architecture StackACK Agentic Payment \u00b7 Section Cut \u00b7 Compliance Depth AnalysisA-001 \u00b7 EXEMPLAR STACK DIAGRAMStablecoinAtlas.comCOMPLIANCE DEPTH \u2192L5 APPLICATIONWallets, dApps, payment interfaces, agent runtimesL4 MIDDLEWARE / APIOracles, indexers, compliance APIs, protocol SDKsL3 EXECUTIONSmart contracts, state transitions, token standardsL2 CONSENSUSOP Stack Sequencer \u2192 Ethereum PoS finalityINHERITED FROM ETHEREUML1 NETWORKP2P gossip, node discovery, data propagationINHERITED FROM ETHEREUM\u25b2 STATE TRANSITION \u25b2AI Agent(buyer \u00b7 3rd-party)Merchant Agent(seller \u00b7 1st-party)ACK-IDW3C DIDs + VCsKYA complianceT6 Identity · S2ACK-PayPayment Requestnegotiation protocolT2 Reserves · S4x402Cloudflare WorkerHTTP 402 transportT5 Transfer · S5ChainalysisKYT APIsanctions screeningscreening · S4–S7ACK ReceiptW3C VC proofcryptographic receiptT1 Token · S7CDP Smart WalletEIP-712 typed signatureCDP Facilitator co-signUSDC ERC-20transfer() · balanceOf()freeze / burn (Circle admin)SAR FilingACK PROTOCOL LAYERCOINBASE / BASEEnforcement BoundaryL3: code-enforced \u2014 compiled intosmart contract logic. Cannot bebypassed without redeploying the contract.policy-enforced(dashed borders)can be bypassedLEGENDIdentity (T6)Reserves (T2)Transfer (T5)Execution (T3)Token (T1)Reporting (T7)ScreeningCHECKPOINTSGate (solid = code)Gate (hollow = policy)MonitorObligationSolid = code-enforcedDashed = policy-enforcedInherited layer

Base L2 architecture. ACK protocol at L4, Coinbase infrastructure at L3. Layer bands progress from light (L5, surface) to darker (L1, deep). Dashed borders = policy-enforced; solid borders = code-enforced.

See chain-by-chain Stack Diagrams on StableL1.com →

Model 2 — Horizontal

What does a payment encounter?

Journey Maps trace a specific payment scenario through the 8 STP stages — from Intent to Finality. Each station on the track represents a compliance checkpoint. The route line shows the payment's path; checkpoint shapes show the type of compliance action; domain colors identify what aspect of compliance fires at each stage.

Agentic Payment Journey \u2014 Catena Labs ACK ProtocolAI agent purchases API access \u00b7 ACK-ID + ACK-Pay + x402 transport \u00b7 USDC settlement on Base L2J-001 \u00b7 EXEMPLAR JOURNEY MAPStablecoinAtlas.comAGENTIC ROUTECHECKPOINT SHAPESGate (pre-condition) \u00b7 solid = codeMonitor (concurrent) \u00b7 solid = codeObligation (post-settlement) \u00b7 dashed = policySCREENING & MONITORING ZONE (KYT / OFAC)STATE CHANGE(L3 Execution)GATES & PRE-CONDITIONSOBLIGATIONSACKACKACKDELEGATEDDELEGATEDACKBASES1IntentS2IdentityS3DiscoveryS4NegotiationS5TransportS6AuthorizationS7FacilitationS8FinalityAI AgentACK-IDACK RegistryACK-Payx402 (delegated)CDP Wallet (delegated)ACK-Pay ReceiptBase L2 + Reporting

ACK agentic payment journey. 8 stages from Intent to Finality. Hover any stage to see the protocol details, checkpoint type, and enforcement mechanism.

See agent-specific Journey Maps on StableKYA.com →

The Thesis

Compliance is migrating downward

EraDepthExample
2020 L5 Application Manual KYC vendors, wallet-level screening
2022 L4 Middleware Chainalysis APIs, CCTP, Circle compliance APIs
2024 L3 Execution ERC-4337 programmable validation, Transfer Hooks
2025–26 L2 Consensus Permissioned validators, ZK-KYC, regulatory view keys

Explore the compliance-depth matrix →