Radar rules and the default agent
Radar rules control which agents are on duty for a coin. Each rule puts an agent on duty when its conditions match. The default agent handles everything else.
Quick start: your first rule
Here's a simple rule that puts your Trend agent on duty during a Bull trend:
| Field | Value |
|---|---|
| Agent | Trend Rider |
| Regime | Bull trend |
| Hours | (all hours) |
| Order | 1 |
When BTC enters a Bull trend, your Trend Rider agent goes on duty and can open trades.
How rules work
Each rule has:
| Field | What it does |
|---|---|
| Agent | Which agent goes on duty when this rule matches |
| Conditions | When the rule matches: regime (with its volatility and warning settings), trading hours, or both |
| Order | Which rule is checked first (1 = checked first) |
| Minimum confidence | Optional floor — agent only trades when confidence clears this bar |
Matching rules put agents on duty
When you add a coin to Radar:
- Radar checks each rule in order (1, 2, 3...)
- All matching rules put their agents on duty — not just the first match
- On-duty agents watch for trade opportunities
- When an agent's strategy qualifies, it can open a trade
The default agent
The default agent goes on duty only when no rule matches. It's the catch-all.
| Situation | What happens |
|---|---|
| One or more rules match | Those agents go on duty. Default is off. |
| No rules match | Default agent goes on duty. |
| No rules and no default | Coin is Idle — no agent on duty. |
Tip: Start with just a default agent, no rules. Add rules later when you want different agents for different conditions.
Always-on agents
An always-on rule's one condition is Always. It matches at every check, so its agent is on duty all the time, behind your other rules. Always-on rules sit after every other rule, and a coin with one has no default agent — the fallback is one or the other, never both.
| You want… | Use |
|---|---|
| A backup agent only when no rule matches | The default agent |
| A backup agent on duty all the time, trading whenever the agents above it don't qualify | An always-on rule |
An always-on agent trades the coin in every regime. Your team holds one position and one cooldown per coin, so its open trade or cooldown can keep a rule's agent from entering. Several always-on rules back each other up in order.
Settings
Order (1 = checked first)
| Setting | What it means |
|---|---|
| Order number | Rules are checked in this sequence. Lower numbers are checked first. |
Why it matters: When two agents qualify on the same candle close, the lower-numbered rule's agent trades. See Which rule wins.
Minimum agent confidence (%)
| Setting | What it means | Default |
|---|---|---|
| Min confidence | Agent only trades when its confidence reading is at least this percentage. | None (agent's own settings apply) |
This is separate from Minimum regime strength. Regime strength filters which regimes match. Agent confidence filters which trades the agent takes.
Limits
| Limit | Value |
|---|---|
| Maximum rules per Radar setup | 10 |
| Default agents | 1 (optional) |
Worked example: BTC with regime-based agents
You want different agents for different market conditions:
| Rule | Agent | Conditions | Order |
|---|---|---|---|
| 1 | Momentum Trader | Regime: Bull trend | 1 |
| 2 | Scalper | Hours: 13:00–21:00 UTC (London-NY overlap) | 2 |
| Default | Range Trader | (none — catch-all) | — |
What happens throughout the day
| Time (UTC) | Regime | Who's on duty | Why |
|---|---|---|---|
| 08:00 | Bull range | Range Trader | No rules match → default |
| 09:00 | Bull trend | Momentum Trader | Rule 1 matches |
| 14:00 | Bull trend | Momentum Trader + Scalper | Rules 1 and 2 both match |
| 15:00 | Bull trend | Momentum Trader + Scalper | Both still match |
| 22:00 | Unclear | Range Trader | No rules match → default |
When both agents qualify
At 14:00, both Momentum Trader and Scalper are on duty. If both qualify for a trade on the same candle close:
- Momentum Trader trades (Order 1 wins over Order 2)
- Scalper's signal is kept — it can still trade on a later candle
Which rule wins?
When two on-duty agents both qualify on the same candle close, the lower-numbered rule wins.
| Situation | Result |
|---|---|
| Agent A (Order 1) and Agent B (Order 2) both qualify | Agent A trades |
| Agent B (Order 2) qualifies, Agent A doesn't | Agent B trades |
| Only one agent qualifies | That agent trades |
Important: Order only decides ties on the same candle close. Normally, whoever qualifies first trades — regardless of order number.
The losing agent's signal is marked Taken by higher rule (see Glossary). Its edge is kept for a later candle.
Good to know
-
All matching rules put agents on duty. If rules 1 and 3 match, both agents are on duty — not just rule 1.
-
Default never runs alongside rules. When any rule matches, the default is off.
-
Order only matters for ties. Day-to-day, agents trade whenever they qualify. Order only decides when two agents qualify on the exact same candle close.
-
Same agent in two rules? If your agent appears in rules 1 and 3, and both match, the agent is on duty once (under its lower-numbered rule).
-
Inactive agents are skipped. If an agent is inactive or ineligible, its rule is skipped during matching.
Advanced: How matching works step by step
- Check each rule's conditions — regime match? hours match? both required?
- Collect all matching rules — not just the first one
- Put those agents on duty — each agent can scan for trades
- If no rules match, check for a default — if set, it goes on duty
- If no match and no default — coin is Idle
Each agent's strategy runs independently. Radar just decides who's on duty — your strategy decides when to trade.
Advanced: Rule conditions
Each rule can have:
| Condition | What it checks |
|---|---|
| Regime | Market regime matches your selection (e.g. Bull trend), its volatility is one the rule accepts, and the rule's warning setting allows the current warnings |
| Hours | Current UTC time is within your hours/days |
| Both | Both regime AND hours must match |
| Always | Nothing — it matches at every check. It is the rule's only condition |
A rule without conditions would always match — the builder doesn't allow this. Use the default agent for catch-all coverage when no rule matches, or an always-on rule to keep an agent on duty all the time behind your other rules.
See Market regimes and Trading hours for details on each condition type.