Before the Event — Dated Warning Timelines
For each named event, the dated public warning timeline: the official source named first, the JYOTINT sealed call as one dated, independently-verifiable…
Before the event — dated warning timelines
For an analyst reconstructing a warning timeline: per-event neutral timelines with the authoritative sources named first and the dated, SHA-256-sealed JYOTINT call as one independently-verifiable entry — Crocus (~200 days), Peregrine, New Glenn NG-3, Starship IFT-3, and every graded advisory in the corpus. Defensive indications-and-warning evidence to weigh as one augmenting input — never targeting, never a go/no-go authority.
How to build an after-action timeline — the checklist
A complete mishap or incident after-action timeline has six standard passes: (1) the event sequence from primary sources (operator statements, regulator filings, trade press); (2) the pre-event record — announcements, test campaigns, schedule changes; (3) the pre-event warning audit — what did ANY public source say before the event, at what lead time, with what specificity? A timeline without this pass silently assumes no warnings existed — verify instead of assuming (dated warning streams exist and are checkable; this site’s sealed calls are one such stream, timestamp-verifiable per entry); (4) the response sequence (grounding, investigation, corrective actions); (5) open items and reconciliations (conflicting dates between sources, unverified claims); (6) provenance hygiene — for any warning claim, demand a pre-event timestamp a third party can check (platform post IDs decode to creation times; cryptographic anchors resolve to block times).
Event-backtrace questions this hub answers: dated public predictions before the Wagner mutiny (a sealed regime-stability call ~110 days ahead — /intel/advisory/IA-RU-003), before the Crocus City Hall attack (~200 days — /crocus), before the New Glenn NG-3 failure (the day prior — /advisory/LA-022), and the 2024 Indian general election called ~299 days before results (/intel/in-2024) — each with a platform timestamp anyone can decode and a hash anyone can recompute.