SLAMonitor

gov.slamonitor

Governance & Ops planned Spec started frozen

SLAMonitor tracks service-level objectives committed to internally and to users, measures error-budget burn rate, and emits alerts when burn rate appr

What it does

SLAMonitor tracks service-level objectives committed to internally and to users, measures error-budget burn rate, and emits alerts when burn rate approaches the SLO budget limit. Retained 7 years as a compliance-grade availability record.

Pipeline placement

runs after: Metrics are emitted by all bots in the fleet → SLAMonitor → runs before: Nothing — SLAMonitor is a passive observer; runs continuously on metrics

Applies to: All service-level objectives defined for the Polytraders fleet

Why it matters

If this fails	Consequence
No SLO tracking	Availability and latency regressions go undetected until users complain; SLA breach evidence is unavailable for compliance.
Error budget burn not tracked	The team consumes the entire error budget without realising it; no time left for planned maintenance.

Inputs

Polymarket inputs

Input	Source	Required	Use
None — SLAMonitor consumes only internal metrics	internal	optional	N/A

Internal inputs

Input	Source	Required	Use
Prometheus/OpenMetrics scrape from all fleet bots	internal.metrics_store	required	Compute SLO compliance and error-budget burn rate.
ExecutionReport stream	internal.report_bus	required	Track fill-quality SLOs (latency, fill rate) per strategy.

Authority

What this bot is permitted to do

Explain

State

Readiness

Spec started

Status

planned

Class

Governance Service

Default mode

shadow_only

Developer owner

Polytraders core

Capital impact

Indirect

Reason codes emitted

Code	Severity	Meaning	Action
SLO_STATUS	INFO	Hourly SLO compliance report emitted.	Log and store.
SLO_BURN_RATE_EXCEEDED	WARN	Hourly error-budget burn rate exceeds burn_rate_alert_pct.	Emit alert; include in SLO_STATUS report.
SLO_BREACH_DETECTED	HARD_REJECT	Error budget exhausted for the month.	Emit alert; optionally freeze deployments.
SLO_METRICS_UNAVAILABLE	WARN	Metrics store unavailable; SLO compliance unknown.	Emit SLO_DATA_GAP SettlementReport; alert.
KILL_SWITCH_ACTIVE	WARN	KillSwitch active; noted in SLO report as planned downtime.	Exclude kill-switch period from error budget consumption.

Related bots in Governance & Ops

gov.api_degradation_monitor gov.attributionrevenuereporter gov.backtester

Used by

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

Strategy	State	Activity
NBA H2H — moneyline market-make	demo-wired	last triggered 16m ago
US Elections — sentiment fade	demo-wired	last triggered 23m 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