ExchangeStatusMonitor

exec.exchangestatusmonitor

Execution planned Spec started frozen

ExchangeStatusMonitor treats Polymarket itself as a degradable dependency.

What it does

ExchangeStatusMonitor treats Polymarket itself as a degradable dependency. It polls CLOB V2 endpoint health, watches for reject-rate spikes, and parses public maintenance signals. When degradation is confirmed, it emits ObservationReports that trigger pause or de-risk actions across the exec layer.

Pipeline placement

runs after: Continuous background process; does not depend on order flow → ExchangeStatusMonitor → runs before: All exec bots that submit orders

Applies to: All active trading while Polymarket CLOB V2 is the execution venue

Why it matters

If this fails	Consequence
Exchange degradation not detected	Orders continue to be submitted to a degraded CLOB, accumulating 429 errors, failed acks, and stale fills.
Maintenance window missed	Orders submitted during a scheduled maintenance window are rejected without useful error context, causing unnecessary retries.
Resume too early after incident	Resuming order submission before the CLOB has fully recovered causes a second wave of errors and potentially double-fills on retry.

Inputs

Polymarket inputs

Input	Source	Required	Use
CLOB V2 health/ping endpoint	clob_public	required	Detect CLOB REST endpoint availability and error rates.
Polymarket public status page	internal HTTP poller	optional	Parse maintenance-window announcements and incident notices.

Internal inputs

Input	Source	Required	Use
Reject-rate metrics from OrderLifecycleManager	exec.orderlifecyclemanager	required	Detect reject-rate spikes (429 or 503 responses) as an exchange degradation signal.

Authority

What this bot is permitted to do

Reshape

State

Readiness

Spec started

Status

planned

Class

Execution Utility

Default mode

shadow_only

Developer owner

Polytraders core — Execution pod

Capital impact

Direct

Reason codes emitted

Code	Severity	Meaning	Action
EXCHANGE_STATUS_HEALTHY	INFO	Exchange is healthy; quarantine completed; order submission permitted.	Clear pause state; resume normal operations.
EXCHANGE_STATUS_PAUSE	WARN	Exchange is degraded or in maintenance; order submission paused.	Emit ObservationReport; exec bots suspend new order submissions.
EXCHANGE_STATUS_FLATTEN	HARD_REJECT	Exchange outage confirmed; all open orders should be cancelled.	Emit ObservationReport; trigger mass cancel.
EXCHANGE_STATUS_RESUMING	INFO	Exchange has recovered; quarantine period started.	Start resume_quarantine_min timer; do not resume submissions yet.

Related bots in Execution

exec.antitoxicfill exec.cancelreplaceoptimizer exec.dustandroundingcleaner

Used by

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

Strategy	State	Activity
US Elect — book-builder	demo-wired	last triggered 32m ago
NBA H2H — moneyline market-make	demo-wired	last triggered 39m ago

Showing 2 of 2 · 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