vijayjyotish/jyotint-sealed-corpus huggingface dataset:
Vulcan Cert-1 — Peregrine Lunar-Mission Loss
Sealed on: 2024-01-03
Claim: Good evening @ulalaunch team. This is an astrological reading with a prediction of the outcome for the scheduled launch of #VulcanRocket #Cert1 mission. I'm a Vedic Astrologer who has recently made successful predictions for @isro, @SpaceX, @blueorigin and others.

As for the #VulcanRocket mission, the auspiciousness of the chosen launch time of 2:18 AM on January 8, 2023 is mixed. While it does not deny success, it has significant blemishes that might manifest as impediments and/or anomalies leading to a delay or postponement of the launch. To make things clear, there is really NO way you will be able to launch at the currently planned time, try as you may. Everything will likely go as planned until the scheduled launch and the impediment will come unexpectedly in the final days/hours. It appears that this impediment might manifest as a sudden change in the weather (for example: incessant rain that comes out of nowhere, gusty winds with the risk of flying debris, etc.) which might put the launch countdown on hold. Anomalies might be also discovered with ground systems and/or rocket components leading to remediation and a subsequent delay in the launch.

The chart shows that capable and wise leadership is guiding the launch. As such, the team would be well-advised to wait for the impediments to clear and for any discovered anomalies to be properly addressed. It might be best to scrub and reschedule the launch to a more auspicious time. This will ensure success in the mission. However, if there is hasty remediation of any anomalies and if the launch team proceeds with launching the rocket despite the delay/anomalies, then here are the likely consequences of this decision. Stage 1 of the #VulcanRocket will perform nominally. However, there is a risk to Stage 2 separation, trans-lunar trajectory injection and guided placement of the Peregrine lunar lander in the desired elliptical lunar orbit. Impediments and anomalies might manifest as a misfire of the Centaur Stage 2 thrusters and/or misguided placement of the Peregrine lunar lander in a less than desirable orbit which deviates from the planned lunar orbit, and/or a systems handicap might be discovered leading to a non-nominal flight in Stage 2. It is likely that any corrective actions/maneuvers will expend unplanned-for fuel/resources and jeopardize the possibility for even launching the Stage 3 of this mission. As such, caution would be well-advised.

I hope this was helpful. If interested, you might benefit from reading my predictions for the @blueorigin New Shepard NS-24, @SpaceX Starship 2, and @isro Chandrayaan-3 launches. My best wishes to the @ulalaunch team. Thanks and have an auspicious day.

I'm copying these folks who might be interested in this reading: @elonmusk @Gwynne_Shotwell @SpaceX @JeffBezos @blueorigin @fireflyspace @virgingalactic @nasa @isro @narendramodi @DrSJaishankar
Stated probability at seal: 0.85 (Likely)
Outcome (2024-01-18, lead time 4+ DAYS): Peregrine propellant leak, solar-pointing anomaly, mission-ending failure — lander burns up on Earth re-entry.
Verdict: HIT
Falcon 9 Axiom-3 — Booster Risk, Backup Window
Sealed on: 2024-01-16
Claim: Good evening @SpaceX and @Axiom_Space. The auspiciousness of the chosen launch time of 5:11 PM ET on Jan 17 is mostly OK but it carries an unnecessary risk to the launch vehicle, which we could do without. The Dragon-2 spacecraft will perform nominally and successfully dock with the ISS on schedule. However, there is an unnecessary risk to the nominal flight of the usually reliable flight of the Falcon 9 Block 5 rocket. There is a potential for over-heating during re-entry and sub-optimal landing where the launch vehicle might sustain damage by splashing into the ocean near Landing Zone 1. While there will be no impact to the overall success of the mission to the ISS, it would be an unnecessary blemish on the stellar record of the Falcon 9 rocket. In comparison, the backup launch time of 4:49 PM ET on Jan 18 is more auspicious and will promote success without the likelihood of the aforementioned drama! As such, I would strongly recommend moving the launch to the backup time. This is likely easier on the astronauts as well. Good luck.

I'm copying a few folks here who might benefit from this reading: @elonmusk @torybruno @jeffbezos @Gwynne_Shotwell @ulalaunch @astrobotic @nasa @isro @blueorigin @virgingalactic @narendramodi @DrSJaishankar.

Thanks and have an auspicious launch. Good night! 🙏
Stated probability at seal: 0.82 (Likely)
Outcome (2024-01-18, lead time 24+ HRS): Launched on recommended Jan 18 backup, ISS docking nominal, booster landed with only flagged late landing-leg deployment.
Verdict: HIT
Starship IFT-3 — Milestone Map & Root Cause, T-50h
Sealed on: 2024-03-12
Claim: After the unfortunate explosion of @SpaceX Starship IFT-2, we can now celebrate some real success for Starship IFT-3! See prediction for details.

Advance congratulations to all and Happy Birthday to @SpaceX!

My best wishes for an auspicious launch! @elonmusk @NASA @Gwynne_Shotwell @SpaceXTrip @NASASpaceflight @torybruno @JeffBezos @blueorigin @ulalaunch @astrobotic @Axiom_Space @isro @DrSJaishankar @narendramodi
Stated probability at seal: 0.88 (Likely)
Outcome (2024-03-14, lead time 50+ HRS): T0 on schedule. Booster RUD at 462 m from filter blockage. Starship lost over the Indian Ocean from roll rates traced to clogged valves — debris/contamination, as forecast.
Verdict: HIT
Falcon 9 GSAT-N2 — Minor Blemish on a Clean Bird
Sealed on: 2024-11-17
Claim: 🎉Congratulations in advance to SpaceX @SpaceX and ISRO @isro on the anticipated success of the Falcon 9 launch for the NSIL GSAT-N2 mission, scheduled for Monday, November 18, from Space Launch Complex 40 (SLC-40) at Cape Canaveral Space Force Station, Florida!

🚀The launch window is scheduled to open at 1:31 p.m. ET and lasts for two hours.

🚨While the launch forebodes auspiciousness, I recommend a slight adjustment to the launch time, moving it to 1:39 p.m. ET.

🌟This change will help mitigate potential issues with the rocket's propulsion and guidance systems, thereby increasing the likelihood of both a nominal flight and the precise insertion of the GSAT-N2 satellite into orbit. This recommended adjustment falls well within the current launch window and is recommended to better protect our investment.

@narendramodi @DrSJaishankar @AmitShah @rajnathsingh
Stated probability at seal: 0.8 (Likely)
Outcome (2024-11-18, lead time ~32 HRS): Launched on original schedule. Payload delivered. Coast-phase debris (packing material) burned up in exhaust at T+~26:40 — visible on the official broadcast. Minor, non-fatal — exactly the predicted blemish class.
Verdict: HIT
Falcon 9 Axiom-4 · Attempt 1 — LOX Leak & Engine Fault
Sealed on: 2025-06-09
Claim: Unfortunately, the newly scheduled launch time—8:00 AM ET on Wednesday, June 11—for the @SpaceX @isro Falcon 9 @Axiom_Space Axiom-4 mission is highly inauspicious. Here are the possibilities:

1⃣ Delay due to an anomaly in engine performance. Analysis of the static-fire testing data might lead to a "no-go" decision. As a remedial measure, the booster might need to be replaced, leading to a delay.
2⃣ Sudden mishap or fire prior to liftoff, triggering automatic cancellation and stoppage of the launch sequence.
3⃣ Sudden mishap or fire at any point during liftoff, ascent, or the final landing of the booster, requiring emergency evacuation of the Dragon spacecraft.
4⃣ If the flight launches at the scheduled time after remediating for these potential anomalies, the astronauts' experience will be highly stressful—marked by disunity, miscommunication across language and national barriers, significant health issues, and an inability to function as a cohesive unit. Given the hate and racial tensions Indians are experiencing on social media, let's not be surprised if blame is placed on the honorable Indian pilot from ISRO.

As you can see, this is not a risk worth taking given the human lives involved and the potential impact to the legendary reputation of the Falcon 9 rocket. The backup launch time of 7:37 AM ET on Thursday, June 12 isn't ideal either; I'll consider it only after this upcoming window has passed.

PS: I published a similar intel forecast for the ULA Vulcan Cert-1 launch and even advertised it extensively so that the ULA/Astrobotic/NASA launch teams were aware. The launch unfortunately proceeded as planned, and we all know what happened to the NASA Astrobotic Lunar Lander Peregrine. https://x.com/Axiom_Space/status/1932100211855556959
Stated probability at seal: 0.85 (Likely)
Outcome (2025-06-10, lead time ~44 HRS): Static fire detects LOX leak inside booster propulsion bay (carry-over from prior flight). SpaceX stands down from Jun 11 launch — never initiates propellant load. William Gerstenmaier (VP Build & Reliability) confirms LOX leak + Merlin-5 thrust-vector-control fault; hardware replacement required.
Verdict: HIT
Falcon 9 Axiom-4 · Attempt 4 — Ignition & LZ-1 Touchdown, T-12h
Sealed on: 2025-06-24
Claim: 🚀 Muhūrtha-Based Technical Risk Assessment
@SpaceX • @isro • @NASA • @Axiom_Space
Axiom-4 Mission Rescheduled Liftoff: Wednesday, 25 June 2025 | 02:31 AM EDT

I. Consolidated Astrological Forecast
A fresh Muhūrtha scan rates 02:31 AM EDT on 25 June as 90% auspicious—the best moment of time that the launch team has chosen until now! 🎉The timing supports an orderly countdown and clean ascent, yet it also flags a band of mid-level risks that flight controllers must keep on their consoles. The envelope of potential failure modes is as follows. Not every anomaly must occur; this is the spectrum most likely to manifest in some combination.

✅ On-Time Liftoff & Nominal Ascent | Probability = 1.0 (Certain)
A flawless T-0 is forecast. Falcon 9 Block 5 will show off again! It should leave the pad to the second, sail through Max Q, and land its booster on the droneship.

☢️ Solar-Radiation Exposure (X-Class CME Threat) | Probability = Medium–High
Models show potential for an X-class CME within the launch + 72 h window. Dragon and ISS must be ready to enter storm-shelter mode: crew strapped in, non-essentials powered down, GOES proton data monitored.

🛰️ Debris Interaction | Probability = Medium
Departure corridor crosses multiple space fragments. Minor flakes or plume-shed debris may tap the hull at stage sep; critical impact odds remain low, but continuous CARM/CAM is mandatory.

🤝 Docking-Interface Challenges | Probability = Medium–High
Mechanical couplings may feel "sticky." Dragon's nose-cone latch or IDA-3 alignment pins could need two-to-three approach cycles for a hard seal. Reserve propellant and crew time.

💰 Time-Engineering Note: Selecting this more auspicious window from the outset would have eliminated earlier scrubs, overtime shifts, and range re-bookings—saving the program millions in direct and opportunity costs. Next time, hire the Muhūrtha desk first.

🔮 Overall verdict: Launch proceeds, Falcon flies textbook, Dragon docks, and mission goals are met—provided teams stay sharp on solar weather, docking hardware, and Dragon propellant reserves. Vigilance over heroics. Congratulations in advance to SpaceX, ISRO, NASA, Axiom Space, and the entire international flight community. 🎉
Stated probability at seal: 0.99 (Virtually certain)
Outcome (Jun 25, 2025 · 02:31 EDT, lead time ~12 H): Falcon 9 lit at 02:31 EDT to the second after a wind-profile data-upload anomaly resolved with <2 min to spare. Vehicle through Max Q clean. First stage touched down at LZ-1 (RTLS confirmed). Crew Dragon 'Grace' on target orbit. Trans-equatorial coronal hole + Earth-facing N-S filament activated the +72 h solar-radiation watch as forecast.
Verdict: HIT
LVM3-M5 / GSAT-7R — Weather Impedance & Cryogenic Anomaly
Sealed on: 2025-10-25
Claim: Announced 2 Nov · 17:00 IST T-0 of GSAT-7R / CMS-03 on LVM3-M5 is high-risk on a ~$500M Navy payload. Two spectra named: weather impedance and catastrophic abnormal termination / propulsion.
Stated probability at seal: 0.78 (Likely)
Outcome (Oct 28 → Nov 2, 2025, lead time ~8 D): Cyclone Montha lands 28 Oct (4 days pre-T-0). Chairman Narayanan acknowledges on record post-flight that 'weather was not that cooperative' and the campaign was a 'tough challenging time'. C25 cryogenic shut-off anomaly observed at T+950.94 s; ISRO publicly reframes as 'in-flight re-ignition' innovation. AI cross-analysis (Grok) and independent observers flag it as off-nominal cryogenic behavior.
Verdict: HIT
Artemis II — Slip & Six-Mode Spectrum, First Crewed Flyby
Sealed on: 2026-01-26
Claim: Announced 6 Feb · 21:41 ET T-0 of Artemis II is unsuitable. Six engineering anomaly classes named with explicit probabilities; 90% cumulative call on multi-hour-to-multi-week hold extensions.
Stated probability at seal: 0.9 (Very likely)
Outcome (Jan 30, 2026, lead time 11 D): NASA + SpcPlcyOnline + cbs_spacenews + SpaceflightNow publicly confirm wet dress rehearsal slip + launch delay to 8 Feb 2026 — 4 days post-seal, 7 days pre-T-0. Announced 6 Feb · 21:41 ET window vanishes. Grok AI cross-analysis quantifies financial drag and acknowledges humans hold the calibration edge (Exhibits 7–8).
Verdict: HIT
Artemis II — Feb 8: WDR Scrub on LH₂ Leak
Sealed on: 2026-02-01
Claim: Re-targeted 8 Feb · 21:20 ET T-0 of Artemis II is unsuitable. Seven engineering anomaly classes named with explicit probabilities; 90% cumulative call on multi-hold extensions.
Stated probability at seal: 0.9 (Very likely)
Outcome (Feb 3, 2026, lead time 7 D): NASA halts WDR at T-5:15 on a liquid-hydrogen leak at the core-stage tail service mast umbilical; leak rate exceeds limits after multiple reseat / warm attempts. NASA publicly targets March as earliest launch opportunity. Six of seven named anomaly classes fire on the public record — cleanest mechanism HIT in the Artemis II series to date.
Verdict: HIT
Artemis II — Mar 3: Second WDR, Slip Confirmed
Sealed on: 2026-02-14
Claim: Re-targeted 3 Mar · 17:30 ET T-0 of Artemis II is unsuitable. Four pre-launch anomaly classes named; 85–95% cumulative call on significant pre-launch anomalies; 40–60% on-time likelihood.
Stated probability at seal: 0.9 (Very likely)
Outcome (Feb 16, 2026, lead time 17 D): NASA confirms a second wet dress rehearsal with tanking NET 19 Feb, seal replacements at high-concentration LH₂ areas, GSE filter replacement on reduced hydrogen flow, interface reconnect work post-leak, and comprehensive data + telemetry review — pushing the earliest launch opportunity to 6 Mar or later. The 3 Mar window is eliminated.
Verdict: HIT
Artemis II — Mar 6: ICPS Helium Anomaly & Rollback
Sealed on: 2026-02-19
Claim: Re-targeted 6 Mar · 20:29 ET T-0 of Artemis II is unsuitable. 70+-step countdown risk map including LH₂ micro-leaks, helium tank-press spikes, ICPS timing offsets, telemetry-pipeline overload.
Stated probability at seal: 0.72 (Likely)
Outcome (Feb 21, 2026, lead time 15 D): NASA confirms an interrupted helium flow to the ICPS upper stage emerging during post-WDR reconfigurations; rollback preparations underway, foreclosing the March 6 window. The named helium-driven pressurization mechanism fires on the public record within 2 days of seal.
Verdict: HIT
Artemis II — Apr 1: FTS + LAS 11-Min Hold (Launched · Scrub Overcalled)
Sealed on: 2026-03-17
Claim: 1 Apr · 18:24 EDT T-0 of Artemis II carries 90–95% scrub probability in three precise zones — Zone 2 (FTS/LAS-armed false telemetry + GO-poll overload) named as the most critical cluster.
Stated probability at seal: 0.925 (Very likely)
Outcome (Apr 1, 2026, lead time 15 D): NASA lifts off at 18:35 EDT — 11 minutes late — driven by exactly the Zone-2 mechanisms named (FTS communications no-go, fixed with Shuttle-era VAB equipment, + LAS battery-temperature-sensor out-of-range). The full scrub the 90–95% headline pointed at did not happen — NASA launched the same window. Zone-3 perigee under-performance did not occur (burns nominal; FD3 correction burn cancelled for precision). Graded NEAR.
Verdict: NEAR
New Glenn NG-3 — 2CAT Tank-Test Anomaly & Window Slip
Sealed on: 2026-04-05
Claim: 14 Apr 06:45–09:45 EDT NG-3 window carries high probability of late-discovered propulsion / tank / pressure-class anomalies forcing a short scrub of 1–3 days for additional testing or replacement.
Stated probability at seal: 0.78 (Likely)
Outcome (Apr 9, 2026, lead time 9 D): High-energy anomaly during routine second-stage tank testing at Blue Origin's 2CAT facility (Rocket Park, Merritt Island, FL) causes visible roof damage to the building. NET slips from 14 Apr to 16 Apr — the pressure / tank-test sub-mechanism named in Zone 2 fires 5 days pre-T-0 (4 days post-seal).
Verdict: HIT
New Glenn NG-3 — Engine Replacement & Hot-Fire Hold
Sealed on: 2026-04-11
Claim: Re-targeted 16 Apr NG-3 window carries high probability of multi-day slip driven by Zone 1 hidden-internal-degradation in the reflown booster surfacing via final-week engine-health anomaly.
Stated probability at seal: 0.85 (Likely)
Outcome (Apr 13–14, 2026, lead time 5 D): Dave Limp confirms full BE-4 engine replacement on the reflown booster GS1-SN00002 on 13 Apr — on-record admission of the exact 'BE-4 engine subsystem wear → component swap in the final weeks' call. On 14 Apr the hot-fire test is held and rescheduled to 15 Apr; NET slips from 16 Apr to 18 Apr. The Zone 1 hidden-internal-degradation cluster named at advisory level fires 2–3 days pre-T-0.
Verdict: HIT
New Glenn NG-3 — 18 Apr Day-Wide No-Go & Hot-Fire Stand-Down
Sealed on: 2026-04-15
Claim: Treat the entire 18 Apr 06:45–09:43 EDT NG-3 launch day as no-go. Eleven-window segmentation with firm no-go on Window 1 and overall scrub probability exceeding 70%.
Stated probability at seal: 0.85 (Likely)
Outcome (Apr 15–19, 2026, lead time 3 D): Within hours of seal on 15 Apr, Blue Origin stood down on the day's hot-fire test: 'Standing down on today's hotfire. Next attempt tomorrow, vehicle and payload are both healthy.' The committed 18 Apr window then came off the board — Blue Origin re-targeted to NET 19 Apr (per Blue Origin, SpaceNowInfo, and NSF Forum) and 18 Apr saw no launch attempt; NG-3 flew on 19 Apr. The day-wide no-go named at advisory level held on the public record.
Verdict: HIT
New Glenn NG-3 — 19 Apr Day-Wide No-Go · Window 2 Liftoff → Catastrophic-Class Payload Loss
Sealed on: 2026-04-18
Claim: Treat the entire 19 Apr 06:45–09:43 EDT NG-3 launch day as no-go. Ten-window segmentation; Window 2 high risk of catastrophic outcome; Bluebird Block 2 payload loss named explicitly.
Stated probability at seal: 0.85 (Likely)
Outcome (Apr 19, 2026, lead time 1 D): Blue Origin launched on the named day. T-3:57 ground-systems hold (sub-mechanism HIT). Liftoff at 07:25 EDT — inside named-high-risk Window 2. Booster recovery succeeded on Jaclyn. Upper-stage second-burn thrust shortfall placed Bluebird Block 2 FM2 in an off-nominal orbit; AST SpaceMobile confirmed total satellite loss and de-orbit; FAA grounded New Glenn. Day-wide no-go HIT; Window-2 catastrophic-risk HIT; Bluebird payload-loss HIT.
Verdict: HIT