AUREON

Financial Compass for onchain AI agents on Robinhood Chain.

> Objectives that persist. Capital that restores. Settlement you can trust.


Contract Address: 0xd293291060334d42e5dbea6fb854c231af527777

---

What is AUREON?

AUREON is the financial intelligence layer for onchain AI agents on Robinhood Chain — a product and protocol surface where capital is governed by persistent Financial Compass objectives, not by one-off swaps that forget their purpose the moment they settle.

The agent economy is already moving capital: bots, treasuries, and autonomous operators deposit, rebalance, and route exposure onchain. Robinhood Chain gives settlement speed and EVM composability; it does not give agents a durable financial intent. Every transparent trade can still leave the *policy* behind — the rule that said “keep twenty percent stable,” the band that said “this equity sleeve stays inside tolerance,” the restore path that should fire when markets move. AUREON exists so agents can operate as economic actors with living objectives — continuous health, staged or vault restore, and an append-only timeline — without turning custody over to a black box.

In practice, AUREON is a hosted policy and health engine, a non-custodial Smart Vault path on Robinhood Chain, an operator utility for humans who need a console, and a typed @aureon/sdk for agents and integrators. You register a Financial Compass objective. The system marks the Capital Book, scores health, detects violations, and produces restore plans. Receipts are honest: settlement: "vault" means onchain; settlement: "staged" means ledger-local and must be labeled as such. Growing capital intelligently — for onchain AI agents.

What we build

We are building the policy and restore layer for agent capital on Robinhood Chain — infrastructure where Financial Compass objectives, capital health, and verified restore plans are one product, not three disconnected tools. That means a full stack: intent as a first-class object, continuous monitoring, non-custodial execution, and integrator tooling that never asks for private keys.

Products and surfaces: aureonlabs.network is the public face — product narrative, architecture entry points, and how the stack fits together. @aureon/sdk is the typed TypeScript client — wallet session handshake, portfolio sync, objective CRUD, health and timeline, vault step preparation, restore execution, and controlled market-event rehearsal for integrators. Smart Vaults on Robinhood Chain hold the onchain capital path; keepers and the Health Watchdog coordinate restores without taking custody of keys.

What the objective layer does: each Financial Compass objective encodes a durable rule — stable allocation bands, equity sleeves, tolerances, priorities. The Health Engine marks weights against public prices. The Watchdog turns drift into violation state. The restore planner returns actionable plans — wrap and unwrap paths, vault swaps — and execution leaves a receipt plus a timeline event so agents and humans share the same memory of what happened and why.

What we build for integrators and the market: agent runtimes that can create a twenty-percent stable objective, survive a market move, restore without lying about settlement, and prove the loop in SDK and utility. We are not claiming custodial portfolio management or silent discretionary trading. We are shipping a credible objectives + health + restore stack on Robinhood Chain that agents can call through one typed surface.

AUREON architecture

AUREON is a three-boundary stack built for agent capital with persistent intent on Robinhood Chain. Each boundary has a clear job: keys and broadcast at the edge, policy and health in the hosted layer, and settlement on chain when the receipt says vault. Together they implement Objectives that persist. Capital that restores. Settlement you can trust.

Boundary 1 — Client / Agent is where trust starts. The operator or agent runtime holds the wallet, signs the session nonce, and broadcasts vault steps. @aureon/sdk is the typed HTTP client: it validates inputs, carries the API key and JWT, prepares unsigned calldata, and never receives a private key. If custody leaks here, the rest of the stack cannot fix it — so signing stays with the host by design.

Boundary 2 — Hosted AUREON layer is the product core. The API gateway exposes Capital Book, objectives, health, timeline, vault preparation, and restore coordination. The ledger remembers policies and events. Public price marks feed the Health Engine. The Watchdog heartbeats violations. The restore planner turns breach into a plan. This layer is what makes AUREON policy-native: a swap without an objective is a forgotten transaction; an objective without health is a wish.

Boundary 3 — Robinhood Chain is verifiable settlement when capital actually moves onchain. Smart Vaults hold non-custodial rebalancing capital. Keeper paths can execute vault swaps under plan. Integrators still sign locally for deposit and withdraw steps the SDK prepares. Staged restores remain ledger-local — useful for rehearsal and operator flows — and are labeled staged so product surfaces never confuse them with vault settlement.

The diagram below is the full Financial Compass path from agent to chain:

mermaid
flowchart TB
  subgraph edge["Boundary 1 — Client / Agent"]
    Agent[AI agent / operator]
    SDK["@aureon/sdk"]
    Signer[Wallet signer · keys stay local]
  end

  subgraph hosted["Boundary 2 — Hosted AUREON"]
    API[API gateway]
    Book[Capital Book]
    FCO[Financial Compass objectives]
    Health[Health Engine]
    Watch[Watchdog]
    Plan[Restore planner]
    Timeline[Append-only timeline]
  end

  subgraph chain["Boundary 3 — Robinhood Chain L2"]
    Vault[Smart Vault]
    Keeper[Keeper rebalance path]
    Receipt[Settlement receipt · vault or staged]
  end

  Agent --> SDK
  SDK --> Signer
  SDK --> API
  API --> Book
  API --> FCO
  FCO --> Health
  Health --> Watch
  Watch --> Plan
  Plan --> Timeline
  Plan --> Receipt
  Signer --> Vault
  Keeper --> Vault
  Vault --> Receipt

Cross-boundary rule: intent flows in as objectives; evidence flows out as health, timeline, and settlement-honest receipts. Keys never cross into the hosted layer. That is the architecture we ship — expandable to richer agent fleets and multi-objective coordination without changing the core split: policy in the middle, Robinhood Chain at the bottom, keys at the edge.

How Financial Compass works

A Financial Compass objective is a durable capital rule with a target, a tolerance, and a priority. AUREON does not treat the last swap as the source of truth. The objective is the source of truth; markets are the disturbance; restore is the correction.

Register the rule: through the utility or @aureon/sdk, an agent creates an objective — for example a stable allocation at twenty percent with a three-point band, or an equity sleeve with its own weight and tolerance. The Capital Book supplies positions from chain sync or explicit operator input. AUREON does not invent balances to make the book look healthy.

Mark and score: public price marks update portfolio weights. The Health Engine compares live weights to objective bands and writes healthy or violation. The timeline records the story — objective created, violation detected, restore executed — so agents and humans can audit the same sequence.

Restore with honesty: when the Watchdog reports a breach, a restore plan is available. Execution may settle through the vault path on Robinhood Chain or remain staged on the ledger. Every receipt carries settlement. Product and agent UIs must surface that field. Staged is not a secret second mode; it is a labeled mode.

End-to-end loop: create objective → mark capital → detect violation → restore → read receipt → confirm health. That loop is the wedge for launch content, SDK demos, and utility walkthroughs — built as product surface, not as a slide.

For agents and integrators

An onchain AI agent on AUREON is not a chat wrapper over a swap button. It is a software actor that (1) authenticates a wallet session, (2) syncs or sets a Capital Book, (3) registers Financial Compass objectives, (4) reads health and timeline, and (5) executes restore plans while respecting settlement labels.

What you get today:

• @aureon/sdk — TypeScript client and CLI for the full objective loop.
• Operator utility — human console for capital, policy, health, and API keys.
• Non-custodial vault steps — prepare locally, sign locally, broadcast locally.
• Settlement-honest receipts — vault vs staged, always explicit.

Why agents need this: agents need persistent financial intent — not only transaction hashes. AUREON binds objective runtime to capital health so the same stack that stores the rule also detects breach and leaves public, readable evidence of restore. One narrative: Financial Compass for onchain AI agents on Robinhood Chain, backed by a real utility, a real SDK, and receipts that tell the truth.

Full architecture, API reference, and integrator walkthroughs live in the aureon-sdk repository.

---

AUREON — growing capital intelligently for onchain AI agents.

Collapse