ReplaySimulator
Re-runs any historical pipeline trace against the current bot revisions to verify that the outcome would be the same (or to surface changes).
What it does
Re-runs any historical pipeline trace against the current bot revisions to verify that the outcome would be the same (or to surface changes). Used for regression testing, incident post-mortems, and 'what would have happened' reviews. Runs only on recorded ReportEnvelope streams — never against live state.
Pipeline placement
Applies to: Continuous
Why it matters
| If this fails | Consequence |
|---|---|
| Regression detection | When a single bot is bumped, the simplest correctness check is to replay yesterday's traffic and diff the outcomes. |
| Postmortem reproducibility | An incident review that cannot reproduce the exact decision is just speculation. |
| Promotion gate | Templates require a passing replay against the canonical fixture set before promoting from shadow to advisory. |
Inputs
Internal inputs
| Input | Source | Required | Use |
|---|---|---|---|
| Recorded ReportEnvelope stream | ReportEnvelope archive | required | Source of inputs to replay. |
| Current bot revisions | Bot registry | required | Target system to replay against. |
Authority
What this bot is permitted to do
State
Readiness
Spec ready
Status
planned
Class
Governance Service
Default mode
shadow
Developer owner
Governance pod
Capital impact
Indirect
Reason codes emitted
| Code | Severity | Meaning | Action |
|---|---|---|---|
| GOV_REPLAY_MATCH | P3 | Gov Replay Match | See decision output and developer log for context. |
| GOV_REPLAY_REGRESSION | P3 | Gov Replay Regression | See decision output and developer log for context. |
| GOV_REPLAY_ABORTED | P3 | Gov Replay Aborted | See decision output and developer log for context. |
| GOV_REPLAY_NO_NETWORK_VIOLATION | P3 | Gov Replay No Network Violation | See decision output and developer log for context. |
Related bots in Governance & Ops
Used by
Reverse index — strategies that currently reference gov.replay_simulator. 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 2m ago |
Showing 1 of 1 · 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 →