battlegrid-strategy-examples

Strategy Studio — full-power composition patterns

strategy-authoring owns the flow (evidence → locked spec → discover → compile → review → apply). This skill owns what to compose: a default build — a few platform sections, no conditions, untouched weights — wastes the studio. The playbooks below are compiled in CI, so their shapes are binding in the sense that matters — they are checked, not merely asserted. Loose tokens elsewhere in this file are not covered by that gate, and vocabulary moves with deploys, so discovery in the conversation stays the authority — prefer what list_strategy_vocabulary, get_strategy_column_contract, and get_strategy_signal_definition return over anything printed here, and read exact headers from a preview's conditionColumns before conditioning on them.

The full-power checklist

Before compiling a CREATE, every "no" here is a decision to state, not an omission:

1. At least one custom section whose columns encode the thesis — not only platform modules.
2. Conditions encode the entry logic: building blocks (verdict: null) + verdict carriers, and at least one required: true condition vetoing obvious disqualifiers before any billing or LLM call.
3. Every signal meant to score is named in rules with a deliberate tier — unnamed signals keep server defaults (typically Off). Verify in the compiled scorecard, never assume.
4. Gates (minAggregateScore, minRequiredCount, minAtrPct) are computed against the chosen weight budget, not guessed.
5. Trade levels + position management match the setup's geometry and holding period.
6. marketReadText states standing orders with {...} markers so live values render inline.

Header grammar (system-generated — never named by the author)