⚠ 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

ConfigDriftDetector

gov.config_drift_detector
Governance & Ops planned Spec ready frozen

Compares the running BotConfig of every live bot against the latest committed config in the config repo.

What it does

Compares the running BotConfig of every live bot against the latest committed config in the config repo. Any drift (running != committed) is surfaced as a ConfigDriftReport naming the bot, the field, and the drift amount. Operators are forced to either commit the change or revert it.

Pipeline placement

runs after: — ConfigDriftDetector runs before: —

Applies to: Continuous

Why it matters

If this failsConsequence
Untracked tuningAn on-call who tweaks a threshold via the Admin UI without committing the change loses an audit trail; the next incident review cannot reconstruct the system state.
Drift between staging and prodWithout an explicit comparison, prod can silently run an ancient config while staging is updated.
Compliance evidenceAuditors require evidence that the running configuration matches a reviewed and signed-off version.

Inputs

Internal inputs

InputSourceRequiredUse
Running BotConfig per botBot runtimerequiredEffective config in process memory, including any live-edited fields.
Committed BotConfig per botConfig repo (Git)requiredSource of truth signed-off configuration.

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

Direct

Reason codes emitted

CodeSeverityMeaningAction
GOV_CONFIG_DRIFT_DETECTEDP3Gov Config Drift DetectedSee decision output and developer log for context.
GOV_CONFIG_DRIFT_RESOLVEDP3Gov Config Drift ResolvedSee decision output and developer log for context.
GOV_CONFIG_DRIFT_UNKNOWNP3Gov Config Drift UnknownSee decision output and developer log for context.

Used by

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

StrategyStateActivity
US Elect — book-builderdemo-wiredlast triggered 7m ago
NBA H2H — moneyline market-makedemo-wiredlast triggered 14m 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…