TPlus
What we alert on
TPlus watches a launch webcast and posts the milestones that matter — not every second of the countdown. Prefer silence between beats. Schedules and streams can lag; this is unofficial.
On a typical flight
You get
- Liftoff
- Max-Q, MECO / stage sep, fairing (when on the plan)
- Boostback / entry / landing burns
- Booster landing, splash, or catch
- Payload deploy start / done
- Hold / scrub / go when marked
You don’t
- Every T− tick
- Every graphic or camera cut
- Guaranteed Max-Q if the timeline is empty
- Official range or provider status
Why didn’t I get …?
- Only liftoff on a rideshare?
- Timelines come from Launch Library 2. Some flights publish NET and a webcast with almost no T+ events — we won’t invent Max-Q.
- An audio footnote on an alert?
- Optional speech spotting can corroborate a milestone. The mission clock and plan stay primary.
- Something I saw on the stream that never pinged?
- If it isn’t on that mission’s plan (or the desk didn’t mark it), it usually stays quiet on purpose.
Where this is going
Today the desk leans on the on-screen clock plus the published plan. Next is a chain of weak indicators from the same stream — audio and video cues that vote, rather than spam.
How sensing works (and how to help)
More detail (for the curious)
Operator notes live in the repo: EVENT-RULES.md · SENSORS.md.