⚠ 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

FillQualityAnalyzer

exec.fillqualityanalyzer
Execution planned Spec started frozen

FillQualityAnalyzer scores every completed fill on price slippage, execution latency, and post-fill toxicity relative to the original intent.

What it does

FillQualityAnalyzer scores every completed fill on price slippage, execution latency, and post-fill toxicity relative to the original intent. Low-scoring fills generate WARN annotations; systematic poor scores feed back to strategy tuning.

Pipeline placement

runs after: OrderLifecycleManager (FILLED event received) FillQualityAnalyzer runs before: Post-trade governance pipeline

Applies to: Every completed fill event emitted by OrderLifecycleManager

Why it matters

If this failsConsequence
Slippage not tracked per fillExecution costs compound silently; strategy returns eroded without visibility into the cause.
Post-fill toxicity not measuredThe system continues submitting orders on markets with chronic adverse selection, accumulating losses.
Fill latency not profiledSlow fills on fast-moving markets indicate queue-position issues that smarter order type selection could fix.

Inputs

Polymarket inputs

InputSourceRequiredUse
CLOB V2 trade tape — last 100 fills on marketws_marketrequiredCompute post-fill mark drift over toxicity_horizon_s for toxicity score.
Market mid at time of fill (top-of-book snapshot)clob_publicrequiredCompute arrival mid for slippage calculation.

Internal inputs

InputSourceRequiredUse
ExecutionReport (FILLED) from OrderLifecycleManagerexec.orderlifecyclemanagerrequiredSource fill price, size, intent price, and submit_ms for all score dimensions.
Original DecisionReport (intent price)strat layer via internal busoptionalCompare fill price against decision-time price to compute decision-to-fill slippage.

Authority

What this bot is permitted to do

Reshape

State

Readiness

Spec started

Status

planned

Class

Execution Utility

Default mode

shadow_only

Developer owner

Polytraders core — Execution pod

Capital impact

Direct

Reason codes emitted

CodeSeverityMeaningAction
FILL_QUALITY_PASSINFOFill quality score >= min_score_for_repeat on all dimensions.Emit annotated ExecutionReport; no further action.
FILL_QUALITY_BELOW_THRESHOLDWARNOverall fill score below min_score_for_repeat.Annotate ExecutionReport; emit WARN to strategy layer.
FILL_QUALITY_CRITICALHARD_REJECTOverall fill score below 0.2 — severe slippage, latency, or toxicity.Emit HARD_REJECT; alert risk pipeline.
FILL_SLIPPAGE_ELEVATEDWARNSlippage exceeded warn_threshold_bps.Annotate ExecutionReport.
FILL_QUALITY_TOXICITY_UNAVAILABLEWARNPost-fill trade tape unavailable; toxicity_score not computed.Omit toxicity_score from overall; note in ExecutionReport.

Used by

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

StrategyStateActivity
Crypto Q2 — basket rebalancefrozenlast triggered 3m ago

Showing 1 of 1 · demo-wired ≠ production-live

Why this matters

Execution bots does NOT propose new positions; only routes and shapes approved intents. 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…