Frozen raw-host evidence · Study v4

A failure happened. Only one policy changed its next plan.

Explore how three runtime-selected policies behaved before, during and after the same imposed generation-2 failure. Every view below is derived from the published descriptive pilot, not a new simulation.

12 / 12 valid lifecycles analysis · loading source · loading

Evidence boundary

Promising for efficiency, not delivery.

The pilot was deliberately small and descriptive. Generation 2 is the common perturbation, never a policy result.

✓Observed: causal policy response and repair behavior.
×Not established: superiority, delivery advantage or field performance.

01 · Causal response

Protection factor by generation

Select a traffic class, then step through the generation sequence. Generation 3 is the first plan made after the terminal failure.

Protection factor across eight generations Line chart comparing fixed-minimum, fixed-class-aware and biological-adaptive. Generation 2 is the imposed failure.
fixed-minimum fixed-class-aware biological-adaptive
Selected generation
Generation 3

fixed-minimum
—

selected-class factor

fixed-class-aware
—

selected-class factor

biological state at plan
—

selected-class factor

02 · Post-shock cost

Initial protection + emitted repair

Five prescheduled generations, 200 source symbols per lifecycle. Requested repair is shown as context but is not added to the wire total.

initial symbols repair symbols emitted

03 · Whole-run transport

Same binary, two conditions

Means across the two randomized blocks. Change the outcome without changing the treatment source.

04 · Delivery guardrail

Delivery saturated after the shock

Both conditions are shown in frozen block order. In regime-change-v1 the shared generation-2 failure explains 7/8; generations 3–7 were 5/5 for every policy.

ConditionPolicyBlock 1Block 2Interpretation
Do not rank generation 2. It was the deterministic policy-neutral perturbation. The informative response begins at generation 3.

05 · Provenance

Trace every view to frozen evidence

The explorer is a generated reporting surface. It performs no network request and contains the evidence input inline.

Read the final descriptive result Inspect the explorer input Open the immutable GitHub Release