ARIANE 501 / AN ASSUMPTION-CHALLENGING LAB

The 37-Second
Blind Spot.

A Million Green Tests,
One Missing Assumption.

A testable disaster. A misleading green dashboard. A lesson for the systems we build with AI.

Retrospective documentary analysis + synthetic mechanism experiment.
No flight telemetry. No claim of independent AI discovery.

THE ASSURANCE GAPILLUSTRATIVE
64bit16bit

One unchecked conversion.
Two identical failure paths.

SRI / 01HALTED
SRI / 02HALTED
Packet received?PASS

The weak oracle sees a frame.
It does not see the loss of navigation.

1,600,000seeded synthetic opportunities
1,000,000legacy-like tests; zero detections
256finite Boolean configurations
1 missing assumptionno finite test count can repair it

01 / HYPOTHESIS & VERDICT

More tests cannot discover
a failure your test world excludes.

The disaster was testable and preventable.
Monte Carlo would not automatically have found it.

The hypothesis is that representative simulation and AI-assisted test design could expose an Ariane 501-like failure before deployment. The inquiry establishes feasible detectability; our toy experiment tests the conditions needed, not an unconditional AI-discovery guarantee.

Read the hypothesis assessment

02 / FIRST, GET THE CLOCK RIGHT

37 seconds after ignition.
About 30 after lift-off.

  1. H0

    Ignition command

    The inquiry's reference clock. Not lift-off.

  2. H0 + 36.7 s

    Backup SRI fails

    The alignment conversion exceeds its range.

  3. About 0.05 s later

    Active SRI follows

    Identical software, the same systematic error.

  4. About H0 + 39 s

    Launcher disintegrates

    Erroneous steering causes destructive loads.

Timing from the 1996 Inquiry Board report. Its 72 ms data cycle and approximately 0.05 s failure separation are different statements. Read the chronology and source.

03 / SAME INPUTS. DIFFERENT TEST WORLDS.

Three ways to get a green result.
Only one changes the design.

SYNTHETIC EVIDENCE

The expanded-input experiments share identical random inputs. Replacing the implementation, weakening the oracle, and removing alignment can all produce zero detections. They do not mean the same thing.

Published opportunities and outcomes, read directly from the result artifact at build time
Test worldOpportunitiesNavigation lossesDetected
Legacy-like supportThe input distribution excludes the failure region.1,000,00000
Expanded supportThe mechanism executes; the safety oracle sees the loss.100,00025,00525,005
Rare-tail supportThe trigger exists, but the test budget matters.200,0009696
Idealized SRI stubA nominal-output harness removes the failing path.100,00000
Packet-presence oracleDiagnostics count as packets. A green result hides navigation loss.100,00025,0050
Post-launch alignment removedAn explicit intervention blocks this modeled chain.100,00000
25,005

Modeled navigation losses hidden by the packet-presence oracle.
A million green tests are not a safety argument without a meaningful contract.

Try the misleading green preset →

A trial is one independent conversion opportunity, not a launch. Rates are not Ariane failure probabilities. Distributions, seeds, confidence intervals, and limitations / Raw results (JSON)

04 / FROM POSSIBLE FAILURE TO ACTIONABLE FINDING

What would have to be true
for this failure to be uncovered?

An input must reach real failing behavior, the evaluation must recognize it, and the evidence must survive into a decision. These are separate, testable obligations.

  1. Expose the dangerous input

    Show that the triggering region exists in the test support. Start with a deterministic boundary witness.

  2. Reach the vulnerable lifecycle

    Run the input while the function is active. Include state, ordering, retries, and transitions.

  3. Preserve executable semantics

    Exercise the conversion and exception behavior. A nominal-output mock can erase the defect.

  4. Observe the right contract

    Distinguish navigation from diagnostics, or real task completion from a success-shaped response.

  5. Defend the rare-event budget

    Choose a probability target and justify the sampling model. More tests cannot fix zero detection probability.

  6. Retain evidence and enforce a response

    Save a replayable falsifier, name a decision owner, and test that the release gate actually fails.

Remove one prerequisite. Keep the others.

CONTROLLED SYNTHETIC EXPERIMENT

The complete experiment crosses 128 configurations of seven process switches; retention and response are separate. These nine controls isolate missing prerequisites and include a guarded negative control. No additional Monte Carlo draws.

Injected detection is separate from the hypothetical iid random campaign and its modeled response policy.
ControlActual navigation lossInjected detectionRandom budgetCampaign detection chance95% target metReplay retainedModeled block
All prerequisites presentYesYes5,99095.000084%YesYesYes
No overflow exposureNoNo5,9900.000000%NoNoNo
Wrong lifecycle onlyNoNo5,9900.000000%NoNoNo
Idealized SRI stubYesNo5,9900.000000%NoNoNo
Packet-only oracleYesNo5,9900.000000%NoNoNo
Too little random budgetYesYes100.498876%NoYesYes
No replay evidenceYesYes5,99095.000084%YesNoNo
No enforced responseYesYes5,99095.000084%YesYesNo
Guarded negative controlNoNo5,9900.000000%NoNoNo

At the invented rare-tail p = 0.0005, 5,990 tests are the minimal 95% budget. A short budget can still detect the injected fault; it just does not meet that random-discovery target. Retention and response do not alter detection. The Boolean response is not a measurement of human behavior.

05 / GO BEYOND THE DASHBOARD

The research is the product.
The demo is an invitation to question it.

OPEN ABOUT THE WORK. OPEN ABOUT THE LIMITS.

AI helped build this lab.
That is not evidence AI
would have caught the fault.

We knew the answer before designing the experiment. No blinded AI evaluation, trained model, flight telemetry, or independent human scientific validation was performed in-session.

Alternative web search located sources; direct source-text verification established the claims. The source catalog preserves access limitations, academic mirrors, and metadata-only checks.

Read the AI usage disclosure →

Usage totals, verified model identifiers, time, and cost are unknown, not zero. Model artifact version 1.1.