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

OrderAmendCancelManager

exec.order_amend_cancel_manager
Execution planned Spec ready frozen

Owns every amend and cancel operation against the CLOB for orders Polytraders has placed.

What it does

Owns every amend and cancel operation against the CLOB for orders Polytraders has placed. Strategies do not cancel directly — they emit an OrderAdjustment intent which this bot validates, sequences, and submits via the EIP-712 v2 envelope. Maintains a strict monotonic intent sequence per order so cancels can never race amends.

Pipeline placement

runs after: exec.order_lifecycle_manager OrderAmendCancelManager runs before: —

Applies to: Continuous

Why it matters

If this failsConsequence
Race conditions on cancel/amendWithout a single sequencer, two strategies can race each other to amend the same order, producing inconsistent CLOB state.
Phantom cancelsA cancel that fails silently leaves an order resting that strategy code believes has been killed; mismatched state causes self-trades and over-positioning.
Amend bypasses riskAn 'amend size from 100 to 500' looks like a cancel-and-place but bypasses Risk if not routed through this bot.

Inputs

Polymarket inputs

InputSourceRequiredUse
CLOB v2 amend/cancel endpointsCLOBrequiredThe actual targets for the action.
Order ack/reject eventsWebSocketrequiredConfirm or fail each operation.

Internal inputs

InputSourceRequiredUse
OrderAdjustment intentStrategy or runbookrequiredThe request to modify or cancel an order.
OrderLifecycleManager stateexec.order_lifecycle_managerrequiredSource of truth for order status before and after.
RiskVote pipelineRisk podrequiredAmends with non-zero new_size must pass Risk like any other OrderIntent.

Authority

What this bot is permitted to do

Amend Cancel

State

Readiness

Spec ready

Status

planned

Class

Execution Utility

Default mode

shadow

Developer owner

Execution pod

Capital impact

Direct

Reason codes emitted

CodeSeverityMeaningAction
EXEC_AMEND_OKP2Exec Amend OkSee decision output and developer log for context.
EXEC_CANCEL_OKP2Exec Cancel OkSee decision output and developer log for context.
EXEC_AMEND_INFLIGHTP2Exec Amend InflightSee decision output and developer log for context.
EXEC_AMEND_UNKNOWNP2Exec Amend UnknownSee decision output and developer log for context.
EXEC_AMEND_TIMEOUTP2Exec Amend TimeoutSee decision output and developer log for context.
EXEC_CANCEL_TIMEOUTP2Exec Cancel TimeoutSee decision output and developer log for context.

Used by

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

StrategyStateActivity
US Elect — book-builderdemo-wiredlast triggered 9m ago
NBA H2H — moneyline market-makedemo-wiredlast triggered 16m ago
US Elections — sentiment fadedemo-wiredlast triggered 23m ago

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

Why this matters

Execution bots does NOT propose new positions; only routes and shapes approved intents. 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…