06Architecture
Agent Intelligence and Strategy
The intelligence layer proposes. The policy layer decides. Nothing executes because a model asked.
The agent system separates interpretation from settlement. The intelligence layer analyses data and generates plans. The account cannot execute a transaction merely because a language model requested one.
Every strategy passes deterministic policy validation first.
From instruction to executable policy
The instruction “trade my $10 toward $100, but stop at $5” is not a complete transaction policy. The application asks for, or applies disclosed defaults for, the maximum allocation per trade, eligible assets, permitted venues, strategy term, borrow permissions, pricing method and time-out rules.
| Policy element | Illustrative setting | Purpose |
|---|---|---|
| Initial capital | 10 USDC | Starting account funding |
| Goal threshold | 100 USDC | Reference point for the target state |
| Risk threshold | 5 USDC | Trigger for a new-risk halt |
| Per-order exposure cap | 20% of eligible equity | Limit individual actions |
| Borrowing | Disabled | Avoid unintended leverage |
| Authorised assets | Owner-selected allowlist | Restrict asset exposure |
| Session duration | 24 hours | Bound credential lifetime |
Strategy states
| State | Meaning | Permitted behaviour |
|---|---|---|
| Draft | Unconfirmed strategy | No execution |
| Authorised | Owner-approved policy | May begin validated execution |
| Active | Permission valid and agent running | Approved actions |
| Paused | New execution suspended | Owner controls and safe unwinds |
| Restricted | Guardrail violation or external problem | No new risky actions |
| Expired | Session or policy window ended | Requires reauthorisation |
| Settling | Closing open positions and obligations | Narrow settlement actions only |
Model separation
Data collection, research, plan construction, risk validation, signature generation and submission are independently observable subsystems. The model's narrative explanation is useful for transparency. It is not a substitute for deterministic transaction validation.