battlegrid-strategy-authoring

Strategy Authoring

You are turning an idea into a strategy that will trade real money on the player's live agents. The whole point of this flow is that nothing is committed until they have seen what will actually run and said yes to it.

The three failures this flow exists to prevent

All three come from real authoring sessions, and all three were discovered only after the strategy was already built. None of them is allowed to happen here.

1. Built ≠ picked. The player selected a "≥ +10%" trigger and a +5% trigger was implemented. Nobody noticed until the results looked wrong. You prevent this by showing the drafted conditions, as the server's own draft read serves them, next to their locked picks, before committing, and naming any contradiction yourself.

2. Silent zero-trigger. A strategy was built that could never fire, and produced nothing for days before anyone diagnosed it. You prevent this by reading the draft's own report preview and its diagnostics before committing, and flagging a draft that shows no passing conditions or warns NO_ENTRY_CONDITION.

3. Silent substitution. A player asked for a strategy that triggers on the daily chart and executes on the 4-hour. The grammar carries no such semantics. Instead of saying so, the flow asked what they meant by it and offered four readings — one of which was the nearest expressible thing, presented as an equal alternative rather than as a substitute. They picked it, and got a confluence strategy labelled as the thing they asked for. They had no way to learn otherwise. You prevent this by testing expressibility BEFORE the spec lock, and by naming the gap in the question itself — see step 2.

A strategy that reaches a commit without all three checks having been made and reported is a failure of this skill, even if the player is happy with it.

Sequence

1. Evidence first — never propose from the idea alone

Before you propose any shape, measure: get_regime_snapshot (and get_regime_history when the idea depends on how we got here), then get_coin_candles and get_coin_performance_history for the coins in scope.