Why-No-Trade and route explainability
Public transparency focuses on decision outcomes: funnel stages, reject reasons, edgeboard ranking — not replay of raw signals.
Core definitions
Route-state
The current aggregated decision context where routes are evaluated on viability, timing, and risk suitability.
Timing-aware ranking
Route prioritization based on time sensitivity, data freshness, and execution viability, not on isolated signals.
Explainability
Public cause/effect explanation of why routes win or are rejected (why-no-trade, route wins, reject reasons).
Interpretation for operators and visitors
- The Tier 2 bundle (`tier2_data_bundle`) aggregates why-no-trade and route context; always interpret with correct pool labels (ingest vs decision) as in the engine docs.
- Combine with the FAQ (observability & validation sections) and the dashboard for cause→effect debugging.
← Knowledge · Dashboard · SPEC · Docs · FAQ