⚠ INTERNAL — Operator UX mock · Design preview of V2 development path · demo-wired ≠ production-live · back to dev guide
Polygon · pUSD 10
📓 Developer Guide 📋 Reason Codes 📈 Shadow Mode
JD John Doe · Admin

Dispute-Risk Pricing

strat.dispute-risk-pricing
Strategy planned Spec started frozen

Dispute-Risk Pricing identifies Polymarket markets affected by UMA dispute uncertainty where the current price does not reflect the true resolution pr

What it does

Dispute-Risk Pricing identifies Polymarket markets affected by UMA dispute uncertainty where the current price does not reflect the true resolution probability given the dispute risk. The bot buys positions that appear mispriced due to dispute-inflated uncertainty, but only when the resolution-rule reading is unambiguous and the parser confidence is at maximum.

Pipeline placement

runs after: Observation bus / internal analytics Dispute-Risk Pricing runs before: Risk guardrail pipeline

Applies to: Polymarket binary markets currently under UMA dispute where the rule parser confidence is at maximum and the current CLO

Why it matters

If this failsConsequence
Rule reading changes during dispute windowIf the resolution rule interpretation changes after entry, the position is now directionally wrong and cannot be safely exited at the original thesis.
Stale input dataActing on stale signals for Dispute-Risk Pricing produces trades based on outdated market conditions, generating adverse fills.
KillSwitch not respectedEmitting OrderIntents while KillSwitch is active bypasses risk controls.

Inputs

Polymarket inputs

InputSourceRequiredUse
CLOB book (mid, depth, spread)ws_marketrequiredRead current market price and available depth for order sizing.
Market status (open/closed/resolved)clob_publicrequiredSkip closed or resolved markets.

Internal inputs

InputSourceRequiredUse
KillSwitch active flagKillSwitchrequiredAbort all intent emission if KillSwitch active.
Dispute-Risk Pricing analytics signalinternal (analytics engine)requiredProvides the core Dispute-Risk Pricing signal that drives trade decisions.
Builder code bytes32internal configrequiredInjected into builder field on every signed V2 OrderIntent.

Authority

What this bot is permitted to do

Trade

State

Readiness

Spec started

Status

planned

Class

Alpha Strategy

Default mode

shadow_only

Developer owner

Polytraders core — Strategy pod

Capital impact

Direct

Reason codes emitted

CodeSeverityMeaningAction
DRP_TRADEINFOAll gates passed. IOC OrderIntent emitted for Dispute-Risk Pricing.Emit IOC OrderIntent.
DRP_MARGINALWARNEdge is within the warning threshold; size reduced 50%.Emit at 50% size; log warning.
DRP_NO_EDGEINFOEdge below hard floor. Skipping.Skip; emit sampled DecisionReport.
DRP_CONFIDENCE_BELOW_FLOORHARD_REJECTParser confidence below 0.70 hard floor.Skip; no OrderIntent.
DRP_CONTRADICTION_HALTHARD_REJECTOracle signal contradicts current rule reading. All trading on market halted.Skip; no OrderIntent; log alert.
DRP_HARD_REJECTHARD_REJECTA critical gate condition blocked the trade (stale data, kill switch, or hard parameter breach).Skip; no OrderIntent.
KILL_SWITCH_ACTIVEHARD_REJECTGlobal kill switch is active.Skip all markets; no OrderIntents emitted.

Used by

Reverse index — strategies that currently reference strat.dispute-risk-pricing. If you change this bot's authority or reason codes, these strategies must re-pass shadow.

StrategyStateActivity
NBA props — line-shopdemo-wiredlast triggered 25m ago
Crypto Q2 — basket rebalancefrozenlast triggered 32m ago
US Elect — book-builderdemo-wiredlast triggered 39m ago

Showing 3 of 3 · demo-wired ≠ production-live

Why this matters

Strategy bots does NOT sign, route, or directly submit orders to the chain. Understanding the authority boundary prevents misuse and makes promotion-gate reviews faster and more reliable. View raw spec JSON →
Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline
⚙ Page Configuration
Current page settings
Loading configuration…