temporal reverse
Cold ticker and infinite history
A cold selection becomes useful immediately while one durable, coalesced workflow fills missing history behind an opaque cursor.
- Question
- What happens when the requested series does not exist locally yet?
- Binding decision
- Interactive demand is progressive, restart-safe, coalesced, authorized, and limited by provider budget.
- Owner input
- The exact interactive versus repair priority weights require workload and cost evidence.
- 01Viewport demandrequest
- 02Coverage querybounded transition
- 03Coalesce rangebounded transition
- 04Fetch DBNbounded transition
- 05Commit batchbounded transition
- 06Prepend barsclient state
First useful data wins
On ticker selection, the gateway authorizes demand, queries committed coverage, attaches live ownership, and joins or starts bounded history work. Existing committed chunks stream first. New pages become visible only after their QuestDB batch watermark advances, then merge with the live tail without duplicates.
- Visible-range demand is exclusive and cancelable.
- Opaque cursors prevent clients from manufacturing storage offsets.
- Progress and exhaustion guards prevent fetch loops while scrolling left.
EvidencePrompt: cold ticker and frontend rules.
Workflow granularity is a range
Restate, if selected over a small owned job table, coordinates one bounded provider/dataset/schema/instrument/range/generation workflow. It authorizes, fences, pages through the Nautilus Databento historical client, receives canonical Nautilus values, commits them, advances coverage, publishes, and reports terminal state. It never runs once per market tick.
- Overlapping requests coalesce by workflow key.
- Kill-point tests cover every external side effect.
- Watchlist warming and bulk repair cannot starve active-ticker demand.
EvidenceExecPlan Phase 4.
mise x -- task backfill:crash-matrixAcceptance target: Retries produce one logical history and deterministic cancellation.