Governance & Ops — 19 bots
Audit, replay, reporting, incident, cron, attribution
Total bots
19
Frozen
19
Demo-wired
0
Production-live
0
Spotlight bots
gov.builderattribution
BuilderAttribution tags every outgoing order with the Polytraders builder code before submission, logs each fill against the builder code, and reconci
gov.posttradeexplainer
PostTradeExplainer turns every fill into a plain-English SettlementReport: which strategy, which signal, which guard checks passed, why this size, why
gov.strategyregistry
StrategyRegistry is the single source of truth for which strategy is at which lifecycle stage and under what authority.
All Governance & Ops bots
| Bot | Class | Authority | Status | Readiness | Wired? | Purpose |
|---|---|---|---|---|---|---|
| APIDegradationMonitor gov.api_degradation_monitor | Governance Service | Observe | planned | Spec ready | Watches every external API surface Polytraders depends on (CLOB v2 REST, CLOB WebSocket, Polymarket metadata REST, Ethereum RPC, builder fee oracle) a | |
| AttributionRevenueReporter gov.attributionrevenuereporter | Governance Service | Explain | planned | Spec started | AttributionRevenueReporter reconciles builder-code rebates with internal fill records and publishes a daily auditable SettlementReport. | |
| Backtester gov.backtester | Governance Service | Explain | beta | Limited live | Backtester replays historical CLOB snapshots and the full report archive through the live execution path at tick resolution. | |
| BuilderAttribution gov.builderattribution | Governance Service | Explain | live | General live | BuilderAttribution tags every outgoing order with the Polytraders builder code before submission, logs each fill against the builder code, and reconci | |
| ConfigDriftDetector gov.config_drift_detector | Governance Service | Observe | planned | Spec ready | Compares the running BotConfig of every live bot against the latest committed config in the config repo. | |
| Cron Runner gov.cron-runner | Governance Service | Explain | live | General live | CronRunner maintains the authoritative cron schedule for the entire Polytraders system. | |
| ExperimentTracker gov.experimenttracker | Governance Service | Explain | planned | Spec started | ExperimentTracker manages shadow and limited-live A/B experiments, records matched-pair samples, computes confidence intervals, and emits a drift sign | |
| ExposureExplainer gov.exposure_explainer | Governance Service | Explain | planned | Spec ready | Produces a plain-English narrative of current portfolio exposure: which markets, which outcomes, how much pUSD is at risk, why each position was opene | |
| Health & Heartbeat gov.health-heartbeat | Governance Service | Explain | live | General live | HealthHeartbeat monitors the liveness of all 97 production bots by polling each bot's internal health endpoint at a configurable interval. | |
| IncidentCommander gov.incidentcommander | Governance Service | Explain | planned | Spec started | IncidentCommander coordinates halts, flattens, and post-mortems when a guard, monitor, or operator declares an incident. | |
| Paper-Trade Runner gov.paper-trade-runner | Governance Service | Explain | beta | Limited live | Paper-Trade Runner mirrors every live signal against a simulated paper account in real time (mode=paper). | |
| ParameterChangeAuditor gov.parameterchangeauditor | Governance Service | Explain | planned | Spec started | ParameterChangeAuditor intercepts every config edit across the Polytraders fleet, records what changed, who changed it, when, and the before/after val | |
| PnL Reporter gov.pnl-reporter | Governance Service | Explain | live | General live | PnLReporter reconciles all fill events into realised and unrealised P&L, denominated in pUSD. | |
| Portfolio Sync gov.portfolio-sync | Governance Service | Explain | live | General live | PortfolioSync keeps the in-memory portfolio state — open positions and open orders — continuously synchronised with on-chain pUSD balances and CLOB op | |
| PostTradeExplainer gov.posttradeexplainer | Governance Service | Explain | planned | Spec started | PostTradeExplainer turns every fill into a plain-English SettlementReport: which strategy, which signal, which guard checks passed, why this size, why | |
| ReplaySimulator gov.replay_simulator | Governance Service | Simulate | planned | Spec ready | Re-runs any historical pipeline trace against the current bot revisions to verify that the outcome would be the same (or to surface changes). | |
| SLAMonitor gov.slamonitor | Governance Service | Explain | planned | Spec started | SLAMonitor tracks service-level objectives committed to internally and to users, measures error-budget burn rate, and emits alerts when burn rate appr | |
| StrategyRegistry gov.strategyregistry | Governance Service | Explain | planned | Spec started | StrategyRegistry is the single source of truth for which strategy is at which lifecycle stage and under what authority. | |
| UserActivityLedger gov.useractivityledger | Governance Service | Explain | planned | Spec started | UserActivityLedger records every user-initiated action — strategy starts, parameter changes, halts, and overrides — as a SettlementReport, providing a |
Why this matters
Understanding which family a bot belongs to is the first step to understanding what it can and cannot do. Governance & Ops bots does NOT propose, approve, or block trades; only observes and reports — this boundary is enforced in code and visible in every bot's authority chips.