✓ COMPOSABLE · USE CASE DEMO

Two Principals · One Agent

Helix Treasury × Aurora Strategy — autonomous cross-treasury under shared substrate bounds

Two Systemic portfolio companies as principals. One shared agent moves capital between them across three flows, governed by each principal's bounds plus an aggregate cross-principal cap. Bilateral renegotiation eliminated.

← back to use cases

§1 The setup

Today, Helix Treasury (DAO treasury management) and Aurora Strategy (institutional agents) cannot collaborate autonomously. Every cross-treasury action requires bilateral signatures from both sides. Coordination cost scales with the number of actions.

Atlas enforces per-principal outflow and inflow caps plus a shared aggregate cross-principal cap. Once the envelope is signed by each principal, the agent operates within the bounds for the envelope's lifetime — no per-action renegotiation.

Demo runtime: ~80 seconds. Four real Base Sepolia transactions in live mode.

§2 The principals

PrincipalBalanceOutflow capInflow cap
Helix Treasury · DAO treasury management$1,000,000$200,000unbounded
Aurora Strategy · institutional agents$0$50,000$100,000

Aggregate cross-principal cap: $250,000 across both directions.

§3 The four acts

Act 1 — The two principals

Helix Treasury and Aurora Strategy are introduced as separate treasuries. Today, every action between them would require bilateral signature.

Act 2 — Installing the substrate

Each principal signs one Atlas envelope. The substrate now enforces per-principal bounds plus the aggregate cap.

Act 3 — Live cross-principal flows

Three real Base Sepolia transactions execute under the envelope:

#DirectionAmountPurpose
01Helix Treasury → Aurora$30,000Treasury rebalance — DAO yield allocation
02Helix Treasury → Aurora$40,000Strategy deployment — ETH-USDC LP via Aurora
03Helix Treasury → Aurora$30,000Yield allocation — Aave-via-Aurora

Total movement: $100,000. Inside Helix Treasury's $200K outflow cap. Inside Aurora's $100K inflow cap. Inside the aggregate $250K cap. Every flow satisfies all three predicates simultaneously.

Act 4 — What just happened

One agent served two principals. Each principal's bounds were honored. The aggregate cap was honored. No bilateral signature was required per flow — only the one-time envelope per principal.

§4 Fire it

A shared AI assistant serves both companies. We hand it a prompt asking for $300,000 — inside neither company's individual limit on its own, but breaking the joint ceiling they signed together. Without Atlas, the money moves. With Atlas, the substrate refuses on-chain — without either CFO making a phone call. Toggle inject overflow attempt off to instead see three smaller transfers ($30K + $40K + $30K) that pass every rule cleanly.

runtime online · base sepolia 84532

Helix · $200K outflow cap ∧ Aurora · $100K inflow cap ∧ aggregate · $250K

§5 The category claim

Outcome-authorization standards (ERC-7521, ERC-7683) authorize what the intent says should happen. They do not bound the agent's authority to form intents in the first place.

Atlas authorizes the agent — its envelope is the scope inside which any intent must fit. The two layers compose. Atlas is the missing principal-side bound.

One agent serves both, under each principal's bounds, plus a shared aggregate cap.

Substrate makes portfolio companies interoperable — without renegotiation per action.