Phase 32 · transient preservation

Protection or cleanup?

AT-0247 → AT-0254. Benchmark seed 247 with a mandatory coupling floor of 0.35. Every schedule reaches the same destination error, so the only question left is when the damage happened — and whether the mechanism ever avoided it or merely tidied the final frame.

Core objective, sharpened

Can the relational state of an object be changed while its identity state is preserved — not merely restored at the final instant, but held inside tolerance at every moment of the transition?

Plain language

Imagine dragging something across a room and asking whether it got scratched. Reading only the final photograph is not enough: the object can be badly deformed halfway and spring back at the end. Here we film the whole journey and score the worst frame. Schedules that only tidy up at the end are labelled endpoint cleanup, not protection.

Controls

SeedSeed 247 reproduces the recorded transient benchmark.Candidate systems — 60Cases that cannot be matched on destination error are discarded, not scored.Coupling floor — 0.35Mandatory minimum coupling. The benchmark floor is 0.35 of baseline.Peak tolerance — 0.45Maximum identity deviation permitted at any moment of the transition.

Running the transient package — matching every schedule on destination error, sweeping the coupling floor and running the peak-objective search. This takes several seconds.