Skip to main content
Add a data-quality preflight for:
  • backtests
  • alerts
  • exports
  • model or research inputs
  • order-book reconstruction
  • incident reviews
Use coverage, freshness, and incident routes before a job depends on a venue, symbol, data family, and time window. Do not silently interpolate or fabricate missing market data.

​
Quality Checklist

Store the quality checklist with downstream output when a job feeds a backtest, alert, export, dashboard, warehouse table, or model input. Do not require the market-data envelope on coverage bodies that expose a resource-specific payload.

​
Agent Stop Rules

Stop before widening the request when freshness is missing, stale, or contradicted by an incident. Stop when coverage does not include the requested venue family, symbol, data family, or time window. Stop when the quality route and market-data route disagree about the symbol or family. In those cases, return the quality checklist and ask whether to narrow the window, choose a different symbol, or wait for updated coverage. For one-off inspection, it is acceptable to report the quality result beside the market-data response. For backtests, alerts, exports, dashboards, warehouse tables, and model inputs, store the quality checklist as part of the output contract so the result can be audited later.
Last modified on June 28, 2026