Refresh lifecycle
The resumable collection and atomic publication model for market data.
Partial upstream progress never becomes public market state.
Collection
Ordinary contracts and multivariate contracts are collected under one cycle. Every completed page is immutable and checkpointed. If a function stops after upload but before checkpoint, the unreferenced object is ignored; once the checkpoint commits, a retry resumes from the next cursor.
Consolidation and hydration
Multivariate pages are re-read, verified and deduplicated, with later observations for the same ticker winning deterministically. The system then resolves the event and collection context needed to describe each selected leg. Missing joins block publication. No partly described contract is produced.
Verification and publication
The publisher builds the ordinary, multivariate, event, combined-state and Sports artifacts, verifies their hashes and counts, and writes an immutable manifest. Publication remains atomic: the active pointer changes only when the complete descriptor is authorized and matches the current refresh cycle, while a completed collection call alone is not publication evidence.
Durable public state changes only after the generation reaches its terminal published state and readers independently verify the manifest.
Retries resume from checkpoints.
Failure behavior
- A timeout preserves the checkpoint and returns control for a later resume.
- A failed component upload leaves the prior generation active.
- A failed manifest readback leaves the prior generation active.
- A stale publisher cannot activate a superseded generation.
- Duplicate delivery is idempotent only when the complete generation descriptor matches.