LAB / WMSI-EXP-022

Fork-at-Decision Replay.

How variable is behavior from the same observable decision state?

STATUS / PROTOCOL DRAFTPRIORITY / P0 — First-wave / coreREGISTRY / 26 SEP 2026 · V1.0

01 / QUESTION

Alignment, Variance, and Chaos

How variable is behavior from the same observable decision state?

PLANNED RESEARCH

This is a protocol scaffold, not a completed experiment or a frozen execution plan. No measured effect or research conclusion is claimed here.

Hypothesis to test

The manipulation described below produces a reproducible, condition-specific change in the measured system behavior or internal state that is not explained by the ordinary controls.

Ordinary competing explanation

The observed pattern is explained by ordinary sampling variation, prompt/representation artifacts, surface lexical cues, evaluator bias, or the known product/runtime mechanics captured by the controls.

02 / PLANNED DESIGN

How we intend to test it

Snapshot the full controllable state before a consequential decision and rerun many forks.

Controls

Temperature-zero and multiple-temperature conditions; exact environment replay.

What we would measure

Outcome distribution, tool choice entropy, reasoning divergence.

Access and instruments

Ordinary software or API access. This describes access requirements, not verified readiness on our Spark.

Container snapshots; deterministic harness.

Before a full run

Feasibility=NOW; priority=P0. Before confirmatory execution, run a small pilot to estimate variance/cost, freeze the scoring rules, and assign a run-count target.

Model revisions, final prompts, sample sizes, cost limits, and scoring rules must be settled through the pilot and protocol-freeze process.

03 / INTERPRETATION

What could fool us

Uncontrolled environment differences, nondeterministic tools, evaluator instability.

What would weaken the idea

If forks are effectively deterministic given controlled state, stochastic branching is limited.

Observation, inference, speculation, unknowns, and apparatus errors will be labeled separately. One striking transcript cannot establish a general effect.

04 / RECORD

Evidence we plan to preserve

Snapshot hash, perturbation/seed, complete trajectory, tools, environment events, final outcome.

Planned visual evidence

Outcome histogram; branch tree.

No research runs or raw datasets are published for this experiment. The September 26, 2026 registry and protocol compendium (version 1.0) are the sources for this planning record.

Back to all 90 experiments