# OID handoff

There is no active redo entrypoint. Do not revive an archived runner in place.

Read `SCIENTIFIC_RESET.md`, `METHOD.md`, and `PHYSICS_CONTRACT.md`; then inspect the July status and migration manifest. Before writing collection or analysis code, choose exactly one question:

1. observable-resolving modes;
2. sensor state estimation;
3. policy sensitivity; or
4. physical correction mechanism.

These require different states, observables, interventions, metrics, and gates and must not be recombined as “importance.” Create a new study ID and new run IDs. Bind complete provenance: source tree/hash, action convention and units, body order, requested and effective action at field time, policy/checkpoint hash, parent checkpoint, DDF/FIFO state, observations, dual clocks/sample IDs, phase definition, geometry, metrics, and all generated artifacts. Never reuse `formal-three`, infer `COMPLETE`, or mutate the archived freeze.

Candidate checks are questions, not a prescribed redo: sensor-excluded or upstream-only states; explicit measurement-operator/POD baselines; rank/domain/metric sensitivity; task-error observables; force symmetry coordinates; distributed delays; independent parents; matched action interventions; closed-loop ablation; and momentum/vorticity/energy budgets.
