Position-Staleness & Inventory-Hallucination Slippage Playbook

2026-03-13 · finance

Position-Staleness & Inventory-Hallucination Slippage Playbook

Why this matters

Many execution stacks optimize slippage assuming position state is close to real-time truth.

In production, that assumption fails when:

Then the router trades against a hallucinated inventory.

Result: you pay hidden slippage through avoidable hedge churn, over-correction, and deadline panic decisions.


Core failure mechanism

Let:

When event latency widens, e_I becomes persistent, not noise.

Two expensive branches appear:

  1. Phantom-neutral branch (I_est ≈ 0, I_true != 0)

    • strategy believes risk is neutral and delays corrective flow,
    • later catches up in worse liquidity.
  2. Phantom-exposed branch (I_est != 0, I_true ≈ 0)

    • unnecessary hedges/offsets are fired,
    • you pay spread/fees/impact for non-risk.

Near cutoff times, both branches become convex in cost.


Branch-cost decomposition

E[Cost] = C_base + C_phantom_hedge + C_late_catchup + C_flip_churn + C_reconcile_shock

Where:

The key is not just average lag, but lag interacting with urgency windows.


Metric stack

1) Position Freshness Gap (PFG)

PFG = now - last_confirmed_inventory_event_ts

2) Inventory Uncertainty Band (IUB)

IUB = q90(I_true | event stream) - q10(...)

3) Shadow Exposure at Risk (SEaR)

Expected notional error from inventory uncertainty:

SEaR = E[ |I_true - I_est| * mid_price ]

4) Hedge Mismatch Pressure (HMP)

HMP = E[ |H*(I_est) - H*(I_true)| ]

Where H* is target hedge function.

5) Reconciliation Shock Rate (RSR)

Frequency of inventory corrections above threshold k shares/contracts after delay.


Control policy state machine

STATE 1 — LOCKED

Conditions:

Policy:

STATE 2 — DRIFT_WATCH

Conditions:

Policy:

STATE 3 — SHADOW_RISK

Conditions:

Policy:

STATE 4 — SAFE

Conditions:

Policy:

Use asymmetric hysteresis to prevent flapping.


Modeling pattern (production)

  1. Dual-ledger inventory model

    • keep I_confirmed and I_provisional in parallel,
    • decision logic consumes posterior over I_true, not single point state.
  2. Event-latency regime model

    • estimate latency by venue × channel × session segment,
    • detect sudden lag-regime shifts and widen uncertainty immediately.
  3. Uncertainty-aware action objective

    • optimize mean + q95 cost with explicit penalties on phantom hedge and late catch-up branches.
  4. Reconciliation-safe ingestion contract

    • idempotent event apply,
    • monotonic sequencing where available,
    • bounded correction protocol for late corrections.
  5. Delay-injection replay

    • replay historical sessions with synthetic drop-copy and confirm delays,
    • validate state transitions and p95 protection before policy promotion.

Practical rollout checklist


Bottom line

A large share of avoidable slippage is not market impact—it is state impact from trading on stale inventory truth.

Treat inventory as a latency-conditioned belief state, not an exact register. Once uncertainty is priced directly into control decisions, phantom hedges and late catch-up convexity drop materially, especially in deadline-heavy execution windows.