OperatorMonitor and control all live strategies — their state ladder position, wired bots, and current signal mode.When: When you need to pause, resume, or promote a strategy.

Details

What this page is forMonitor and control all live strategies — their state ladder position, wired bots, and current signal mode.

When to use itWhen you need to pause, resume, or promote a strategy.

Powered bystrat.maker_tight risk.killswitch

← Back

Create New Strategy

Configure your trading bot strategy. Five steps: Portfolio › Market scope › Basics › Parameters › Confirm. The first two are M2 hard requirements — you cannot launch without them.

1 · Portfolio
2 · Market scope
3 · Basics
4 · Parameters
5 · Confirm

1 · Target portfolio M2 required

Portfolio is the unit of account. Strategies, positions, signals and risk all hang off the portfolio you pick here. One strategy = one portfolio at launch. Changing portfolio requires stop-and-relaunch.

Bind to portfolio *

Portfolio-layer guardrails (drawdown cap, daily-loss limit, cluster exposure caps) apply on top of the strategy-layer filters you set in step 4.

2 · Market scope M2 required

Which markets the strategy evaluates. Two modes ship in M2; filter-expression DSL is M3. See M2 scope › Market scope for the canonical rule.

Cluster binding primary Manual list cap 50 Filter expression M3

Bound clusters

cluster.us_election_2026 × cluster.fed_decisions ×

Markets currently in scope: 14. Membership updates fire STRAT_MARKET_IN_SCOPE / STRAT_MARKET_OUT_OF_SCOPE.

3 · Basic information

Select categories first, then choose a compatible bot engine.

Category or Tag *

Navigate through markets, categories, subcategories, and tags.

Bot engine *

Only bots compatible with your selected categories are shown. Bot must be at least demo-wired to be selectable.

Strategy name *

Description

Signal handling mode

Expiration time

Signal expiration time in seconds

Timeframe

Window the bot uses to analyze the market

Instruments (registry-picked)

Today the form accepts free-text Polymarket slugs. The mock replaces that with a registry picker: only instruments already onboarded by the rails team are selectable. V1-only and halted markets are shown disabled with the reason code that would block them.

Save fails with GOV_INSTRUMENT_UNKNOWN if a slug isn't in the registry, or GOV_INSTRUMENT_V1_BLOCKED if it's V1-only.

Instrument	Category	Status	Spread
2026 US Senate control election-2026-us-senate	Politics	V2 · trading	18 bps	Inspect
UK snap election 2026 uk-snap-election-2026	Politics	V2 · trading	47 bps	Inspect
Fed rate decision — 2026 Q2 fed-rate-2026-q2	Macro	V2 · trading	22 bps	Inspect
ETH spot ETF approval eth-spot-etf-approval	Crypto	GOV_INSTRUMENT_V1_BLOCKED	—	View
SCOTUS affirm 2026 scotus-affirm-2026	Legal	halted	68 bps	View

Browse the full registry →

Reason-code allowlist preview

These are the only codes envelopes from this strategy are allowed to emit. Picked automatically from the selected bot engine's spec. Anything else fails the lint at save.

STRAT_MAKER_QUOTE_INSIDE STRAT_MAKER_NO_EDGE DISC_HEADLINE_MATCH DISC_HEADLINE_NOISE RISK_KILLSWITCH_TRIPPED RISK_BOOK_STALE_15S RISK_EXPOSURE_CAP_HIT EXEC_ROUTE_CTFV2_ACCEPTED EXEC_SLIPPAGE_EXCEEDED

V2 enforcement

These are read-only assertions the system makes at save time.

Exchange	`CTFExchangeV2`	enforced
Signing scheme	`EIP-712 v2`	enforced
Settlement asset	`pUSD`	enforced
Builder code	`0x… required`	missing — fill on portfolio

Promotion state preview

A new strategy always starts demo-wired. To promote, run a 24-hour shadow soak from the Pipeline.

demo-wired → shadow-ready → runtime-live → production-live

Cancel Create strategy

Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline