A Squad and a strategy are separate things, and they are joined by an indicator. The Squad deliberates on its own markets on its own schedule and publishes a decision; a strategy that wants that opinion adds the Committee Decision indicator and treats it like any other line.
This is worth being precise about, because it decides what a Squad is: a Squad does not trade, and it does not approve trades. It produces a view. Your strategy decides what that view is worth.
Adding the indicator#
Open a strategy, go to Indicators, and add Committee Decision. Pick your Squad from the dropdown — that is the only setting it needs, because the market comes from the strategy's own ticker.
The indicator gives you five lines:
| line | what it tells you |
|---|---|
decision | the standing call: 1 long, -1 short, 0 hold, 2 close longs, -2 close shorts |
confidence | how sure it was, 0 to 1 |
committee_points | its cumulative score — positive means its calls have been paying off |
last_decision_points | how the most recent graded call scored |
decision_age_minutes | minutes since the standing call was made |
Reference them in a bias generator or a signal rule exactly as you would
reference RSI.rsi. A minimal directional bias is
CommitteeDecision.decision equal to 1.
Two rules worth following#
Gate on the score. A Squad's opinion is only worth acting on if its
opinions have been working. Adding CommitteeDecision.committee_points
greater than 0 to your conditions means the strategy follows the Squad
while it is paying off and ignores it when it is not — which is the entire
reason the score exists.
Gate on the age. The decision line holds its last value until the
Squad speaks again. That is what lets a 5-minute strategy read a 4-hour
Squad — but it also means a Squad you switched off keeps publishing
its final opinion forever. Add CommitteeDecision.decision_age_minutes with
a limit of roughly two or three of the Squad's intervals.
One committee, many strategies#
Nothing binds a Squad to a single strategy. Once it covers BTCUSDT, every strategy you run on BTCUSDT can read the same decision line — a momentum strategy, a mean-reversion strategy and a slow trend strategy can all consult the same Squad, and each will do something different with the same call.
The reverse also works: a strategy can add the Committee Decision indicator more than once, pointed at different Squads, and combine them. Two Squads agreeing is a stronger condition than one, and you can write that as an ordinary rule.
Timeframes do not have to match#
A Squad's interval and a strategy's timeframe are unrelated. The decision line is held between wakes, so a 5-minute strategy reading a 4-hour Squad simply sees the Squad's current call on every bar. Nothing is skipped and nothing is interpolated — the value is exactly what the Squad last said.
Backtesting#
A Squad-driven strategy backtests like any other, over the period the
Squad has actually been running. Before its first decision the line reads
0, so a backtest starting earlier is flat until the Squad comes alive.
That is honest rather than a limitation to work around: there is no way to
know what a Squad would have said on a day it did not exist.
See cadence, decisions and the track record for how a Squad produces those decisions and how the score is calculated.