In CSD the quantum state never jumps, and that's a theorem about volume-preserving maps rather than a preference among interpretations.
no_exact_collapse
The textbook says that when a measurement happens the quantum state jumps discontinuously to match the outcome, and you can ask whether that jump is a physical event or an update to a description. The dispute is as old as the theory, and the stakes are real, as a physical jump would be abrupt, irreversible, unexplained by any equation in the theory, and apparently instantaneous across any distance.
An update, on the other hand, needs no physics at all. When you learn which box the ball is in your probabilities collapse and nobody is alarmed, so the whole question is whether quantum collapse is more like the ball.
CSD's answer is the ball, with a twist that makes the answer checkable rather than rhetorical. On a volume-preserving substrate, one whose motion carries every region of the underlying state space to a region of the same size, a physical collapse isn't merely unnecessary, as it's impossible.
The corpus proves that no measure-preserving map implements exact collapse, where a measure-preserving map is one that keeps the size of every region unchanged, which is exactly what the motion of a deterministic, volume-conserving substrate does. So such a substrate couldn't contain a collapse process even if its designer wanted one, and the stance becomes a constraint, with CSD on record as unable to cheat.
What replaces the jump is a record. System and apparatus evolve together under the one dynamics, the record fixes which region of the space of quantum states the trajectory realises, and the update rule the textbook postulates separately falls out of the record construction. The thing that changes discontinuously is the summary, and the world underneath does what it was always doing.
No measure-preserving map on the arena implements exact collapse. Approximate collapse exists but is priced, as accuracy is bounded against ready-state improbability, with the exchange rate explicit.
The post-measurement update is then derived rather than postulated, and it appears as the block projection realised on the pointer arena, an output of the record construction.
CsdLean4/RecordLayer/MeasurementConstraints.leanSource links are pinned to a commit, so they do not drift. The anchors above are checked mechanically against the Lean tree on every build. The mathematics is not, and cannot be: that is a human responsibility and it rests with the author.
Part of Constraint-Surface Dynamics · Formalised in csd-lean4.
Google Analytics counts visits to this page, which stores cookies in your browser. They record how the page was reached, not who you are, and nothing is passed on. Blocking cookies for this site breaks nothing here. Details.