Rules and Runtime
Hub agents are controlled by natural-language rules first. Forms and profiles can help advanced operators, but they do not replace the agent's standing rule file.
Rules
Rules describe what the agent may do, when it should hold, and what facts must exist before any action can move toward execution.
Good rules include:
- chain-specific Solana/Base behavior,
- default sizing or deterministic sizing formulas,
- entry filters,
- exit rules,
- DCA, risk, or strategy profile references,
- approval policy,
- source preferences and exclusions,
- stop-balance and max-open-position limits.
Every applied rules change should be versioned, auditable, and reflected in the runtime view. If the rule text cannot compile into deterministic constraints, Hub should show the unresolved or review-needed state rather than pretending the rule is active.
Natural-language priority
Users should be able to edit behavior in plain language:
- "List my DCA profiles."
- "Show my risk profiles."
- "Change the 2x strategy to sell all."
- "Use this DCA for tokens under 10k market cap."
Advanced UI can expose profile helpers later. It should stay optional and must not turn Hub into a mandatory strategy-builder form.
Runtime modes
Runtime state uses explicit vocabulary:
| Mode | Meaning |
|---|---|
shadow | Recommendations only. No autonomous execution. |
live_unarmed | Configured, but not allowed to execute autonomously. |
live_armed | Execution can proceed only after policy, risk, scope, replay, approval, and reconciliation readiness pass. |
paused | No new autonomous actions should start. |
shadowMode may appear as compatibility state, but new runtime controls should
use the explicit modes above.
Safety boundary
The LLM does not approve its own action. Runtime changes and trade execution must still pass deterministic policy, risk, scope, replay, approval, and reconciliation gates.
Do not silently rewrite exit policy for an open position after a rules/profile change. Existing positions keep the resolved entry-time policy unless the user performs an explicit lifecycle transition.
Empty and degraded states
If Hub does not yet have agent-native rule versions, profile records, scheduler state, or runtime controls for a specific agent, the UI should say that directly. Do not fabricate live runtime state.