AURA

Instructions Overview

The aura-core instruction catalog, organized by domain

Most in-treasury instructions follow the same shape: load the AgentTreasury domain from its account, mutate it (recording an audit event), then serialize it back and emit events. Live CPI and settlement paths sometimes mutate only the hot pending fields to stay within SBF limits. Standalone PDAs (fee vault, swarm pool, operator role, …) follow an init / edit / close pattern.

Gating

Unless noted, instructions are owner-gated. Some accept an operator role with the matching permission, the AI authority (proposals/session keys), or a guardian quorum (governance/recovery).

Instruction Domains

Browse the complete instruction catalog by domain:

  • Treasury — Lifecycle, metadata, state transitions
  • dWallets — Registration, controls, balances, transfers
  • Execution — Proposals, batches, chain profiles, settlement
  • Confidential — FHE guardrails, decryption, epoch management
  • Policy — Configuration, templates, versioning, canary deployments
  • Scheduled & Conditional — Standing orders, triggers, conditions
  • Trust & Identity — Trust scoring, agent authorities, ownership handover
  • Authorization — Multisig, custody recovery, break-glass
  • Governance — Guardian rotation, AI authority rotation, overrides
  • Roles & Permissions — Operators, session keys, capability manifests
  • Exposure & Pooling — Exposure groups, swarm pools, address lists
  • Fees & Billing — Fee vaults, schedules, billing templates, protocol config
  • Observability — Health scoring, snapshots, analytics, audit trails

The TypeScript and Rust SDKs expose builders for the full instruction surface; the SDK pages mirror these domains.

On this page