IncidentCommander
IncidentCommander coordinates halts, flattens, and post-mortems when a guard, monitor, or operator declares an incident.
What it does
IncidentCommander coordinates halts, flattens, and post-mortems when a guard, monitor, or operator declares an incident. It records the incident timeline, dispatches auto-actions by severity, pages on-call, and tracks RCA completion.
Pipeline placement
Applies to: Any declared incident affecting the Polytraders bot fleet
Why it matters
| If this fails | Consequence |
|---|---|
| No centralised incident coordinator | Multiple bots may take conflicting halt/flatten actions; incident timeline is incoherent. |
| RCA not completed within SLA | Repeat incidents occur because root cause is never addressed; compliance audit finds gaps. |
Inputs
Polymarket inputs
| Input | Source | Required | Use |
|---|---|---|---|
| None — IncidentCommander is a pure internal governance orchestrator | internal | optional | N/A |
Internal inputs
| Input | Source | Required | Use |
|---|---|---|---|
| Incident declaration event from any guard or operator | internal | required | Trigger incident workflow; dispatch auto-actions by severity. |
| KillSwitch active flag | gov.killswitch | optional | Check if KillSwitch is already active before dispatching halt auto-action. |
Authority
What this bot is permitted to do
State
Readiness
Spec started
Status
planned
Class
Governance Service
Default mode
shadow_only
Developer owner
Polytraders core
Capital impact
Critical
Reason codes emitted
| Code | Severity | Meaning | Action |
|---|---|---|---|
| INCIDENT_DECLARED | INFO | An incident was declared and auto-actions dispatched. | Log; emit OperationsReport. |
| INCIDENT_RESOLVED | INFO | An incident was resolved. | Log; start RCA countdown. |
| RCA_OVERDUE | WARN | RCA not filed within require_rca_within_h. | Emit WARN alert. |
| PAGING_SYSTEM_UNAVAILABLE | WARN | On-call paging system is unreachable. | Fallback to Slack; emit WARN. |
| KILL_SWITCH_ACTIVE | WARN | KillSwitch already active when halt_all dispatched. | Log; no duplicate halt needed. |
Related bots in Governance & Ops
Used by
Reverse index — strategies that currently reference gov.incidentcommander. If you change this bot's authority or reason codes, these strategies must re-pass shadow.
| Strategy | State | Activity |
|---|---|---|
| AI Frontier — release-day taker | frozen | last triggered 11m ago |
| NBA props — line-shop | demo-wired | last triggered 18m ago |
| Crypto Q2 — basket rebalance | frozen | last triggered 25m ago |
Showing 3 of 3 · 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 →