Operational readiness · Jobs 3, 7, 11, 12, 15, 16, 21 and 28
What the shared history collectors can support today
A simple readiness table showing how much comparable history exists, the publication gate for each idea and the exact reason no ranking has been produced yet.
Readiness table
History, gates and blockers
“Earliest eligibility” is conditional on future runs succeeding and every non-time gate passing. Unknown dates are left unknown.
Methodology
How the counts were checked
- Read the successful run records in Cloudflare D1 for the shared daily listing collector and monthly FAA registration collector.
- Count distinct snapshot dates, the observed span, current rows, first-baseline events and later change events separately.
- Apply the conservative publication rule already recorded for each idea. Where two project notes disagree, use the longer or more demanding rule.
- Calculate only the earliest time gate. Keep the date conditional when outcome samples, identity QA, editorial methodology or another source must also pass.
- Publish one aggregate row per idea. Do not calculate the intended ranking before its gate is met.
Sources, cadence and interpretation
What zero and unknown mean
Daily listing history: Cloudflare listing_tracker_runs, listing_tracker_current and listing_tracker_events, collected at 05:15 UTC from Sprinkle dealer and marketplace listings.
Monthly registration history: Cloudflare registration_tracker_runs, collected on the first day of each month at 05:30 UTC from a privacy-safe Sprinkle/FAA tracker. The collector stores irreversible owner fingerprints rather than owner names or addresses.
Zero is shown only when a successful collector run returned zero, such as zero later state-change events after a baseline. Unknown means the required fact or source is not observable yet. Unknown is never converted to zero.
If a collection fails, the previous successful history remains the current operational record. Eligibility dates move later when scheduled snapshots are missed.