⚠ 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

PostTradeExplainer

gov.posttradeexplainer
Governance & Ops planned Spec started frozen flagship

PostTradeExplainer turns every fill into a plain-English SettlementReport: which strategy, which signal, which guard checks passed, why this size, why

What it does

PostTradeExplainer turns every fill into a plain-English SettlementReport: which strategy, which signal, which guard checks passed, why this size, why this price. Retained 7 years for regulatory compliance.

Pipeline placement

runs after: Order fill confirmation from CTFExchangeV2 PostTradeExplainer runs before: Nothing — runs post-fill on every ExecutionReport event

Applies to: Every filled or partially filled order

Why it matters

If this failsConsequence
No post-trade explanationUsers and regulators cannot understand why a trade was made; compliance audit fails.
Explanation not linked to fillFill records and strategy intent cannot be reconciled; audit trail is broken.

Inputs

Polymarket inputs

InputSourceRequiredUse
Fill confirmation from CTFExchangeV2clob_authrequiredConsume fill metadata (size, price, side, builder_fee_pusd) for the explanation.
ExecutionReport envelopeinternal.report_busrequiredSource of the full order lifecycle context for the explanation.

Internal inputs

InputSourceRequiredUse
DecisionReport for the originating intentinternal.report_archiverequiredFetch strategy name, signal inputs, and parameter values at decision time.
RiskVote record for the originating intentinternal.report_archiverequiredInclude guardrail votes in the explanation.

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

CodeSeverityMeaningAction
TRADE_EXPLAINEDINFOA fill was successfully explained and a SettlementReport emitted.Log and store.
EXPLANATION_ARCHIVE_UNAVAILABLEWARNDecisionReport or RiskVote could not be fetched; partial explanation emitted.Emit partial SettlementReport with explanation_complete=false.
RETENTION_BELOW_REGULATORY_MINIMUMWARNretain_explanation_days is below 2555 (7 years).Emit WARN; do not reduce retention.
EXPLANATION_MISSING_GUARD_VOTESWARNRiskVote records not found for the fill; explanation is incomplete.Emit partial explanation; flag explanation_complete=false.
KILL_SWITCH_ACTIVEWARNKillSwitch was active at fill time; noted in explanation.Include kill-switch note in explanation.

Used by

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

StrategyStateActivity
Crypto Q2 — basket rebalancefrozenlast triggered 24m 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 →
Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline
⚙ Page Configuration
Current page settings
Loading configuration…