⚠ 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

APIDegradationMonitor

gov.api_degradation_monitor
Governance & Ops planned Spec ready frozen

Watches every external API surface Polytraders depends on (CLOB v2 REST, CLOB WebSocket, Polymarket metadata REST, Ethereum RPC, builder fee oracle) a

What it does

Watches every external API surface Polytraders depends on (CLOB v2 REST, CLOB WebSocket, Polymarket metadata REST, Ethereum RPC, builder fee oracle) and publishes a per-surface health envelope (latency p50/p99, error rate, last_success_ts_ms). Risk and Strategy bots consume this envelope to decide whether to operate normally, degrade, or pause.

Pipeline placement

runs after: — APIDegradationMonitor runs before: risk.killswitch, exec.smart_router

Applies to: Continuous

Why it matters

If this failsConsequence
Cascading failures from a single dead dependencyWithout an explicit health signal, every bot infers liveness from its own latest call — producing inconsistent retreat behaviour across the system.
Silent degradationsAn API can stay up but slow to 30-second responses; bots without an explicit threshold keep blocking on it instead of failing fast.
Postmortem confusionWithout a health timeline, postmortems cannot answer 'what was the actual external latency at 14:23?'.

Inputs

Polymarket inputs

InputSourceRequiredUse
CLOB REST + WebSocketPolymarketrequiredProbe latency and error rates.
Polymarket metadata RESTPolymarketrequiredHealth probe.
Ethereum RPCRPC providerrequiredLatency + block-tip lag probe.

Internal inputs

InputSourceRequiredUse
Real outbound traffic latency samplesEvery botrequiredPassive observation in addition to active probes.

Authority

What this bot is permitted to do

Observe

State

Readiness

Spec ready

Status

planned

Class

Governance Service

Default mode

shadow

Developer owner

Governance pod

Capital impact

Indirect

Reason codes emitted

CodeSeverityMeaningAction
GOV_API_OKP3Gov Api OkSee decision output and developer log for context.
GOV_API_DEGRADEDP3Gov Api DegradedSee decision output and developer log for context.
GOV_API_DOWNP3Gov Api DownSee decision output and developer log for context.
GOV_API_UNKNOWNP3Gov Api UnknownSee decision output and developer log for context.

Used by

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

StrategyStateActivity
BTC weekly — close-aware quotesdemo-wiredlast triggered 38m ago
Fed Rates — surprise driftfrozenlast triggered 45m ago

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

Why this matters

Governance & Ops bots does NOT propose, approve, or block trades; only observes and reports. 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…