SigmaLayer/RecordPersistence: persistence and the post-measurement ensemble (items 5–6) #
Category: 7-SigmaLayer (the record layer — the dynamical interface).
Two things a measurement must do beyond producing an outcome:
- persist — the record must still be there after it is made (item 5);
- disturb — the selected ensemble must be carried through the interaction, which is what makes a repeated measurement agree and what the Lüders update describes (item 6).
★ Both use the evolution, which is the point #
The plan is explicit that reusing the same set at every time does not count as persistence. So
record_persists_on_interval is stated about P.evolve P.startTime t for a range of t, and its
proof goes through evolve_comp — it is a statement about the propagator, not about a set that
happens not to depend on time. Likewise postMeasure is a genuine pushforward along the propagator,
not a relabelling of the conditioned measure.
What is proved #
PointerInvariantOn— the post-readout invariance hypothesis. A hypothesis, not a field, for the same reasonCorrelatesOnis: it is an assumption about the dynamics, and burying it in a structure would let a witness assume what it should prove.record_persists_on_interval— a state destined for outcomeiis in the pointer region for outcomeiat every time of[T_M, T_M + τ_R].readout_persists_on_interval— the same, at the level of the readout: the apparatus readsithroughout the window. ★ This is the pointer-level repeatability statement — a second look during the record lifetime returns the same outcome.postMeasure— the post-measurement ensemble(Φ_{0→T})_* (μ | Ωᵢ).postMeasure_supported_pointerRegion— it is supported entirely onBᵢ.
★ Selection versus disturbance #
measure_outcomeSector_eq_of_correlates (previous module) answers which initial sector produced
outcome i — selection. postMeasure answers where the selected ensemble ends up — disturbance.
They are different operations on different measures, and the corpus previously had no way to say the
second at all.
postMeasure_supported_pointerRegion is close to definitional, and that is a good sign rather than a
weak one: Φ⁻¹(Bᵢ) is Ωᵢ by construction, so conditioning on Ωᵢ and pushing forward lands in
Bᵢ with probability one, for any propagator. The content is in the definitions lining up, which
is what a correct interface looks like.
⚠️ Scope #
- No interaction Hamiltonian.
PointerInvariantOnis assumed, not constructed. Nothing here makes progress on the open Paper D obligation. - The Lüders bridge is NOT here. Item 6 also asks that, after the system-reduction map
r_Sand the epistemic projection, this reproduceρ ↦ Π_i ρ Π_i / Tr(ρ Π_i). That needs a reduction map fromΣ_measto the system's density operator, which the corpus does not have for this arena. The measure-theoretic half is done; the bridge toLF5's Lüders result is not, and is not claimed. - The finite window
[T_M, T_M + τ_R]is deliberate — seerecordDuration.
References #
SigmaLayer/MeasurementProtocol.lean (MeasurementProtocol, outcomeSector, CorrelatesOn);
SigmaLayer/MeasurementConstraints.lean; SigmaLayer/ConditioningLuders.lean (the operational
Lüders result this does not yet connect to); specs/BACKLOG.md (the ★★ row).
Item 5 — persistence #
Post-readout invariance of the pointer regions. Once the record is made, the evolution keeps the state inside the region displaying it, for the whole operational lifetime.
⚠️ A hypothesis, deliberately not a field of MeasurementProtocol. This is an assumption about
the dynamics — exactly the kind the implementation plan warns must not be hidden inside a structure.
A concrete witness must establish it, either by showing Bᵢ is forward invariant under the
post-interaction flow or by exhibiting a conserved pointer observable.
Equations
- One or more equations did not get rendered due to their size.
Instances For
★ The record persists across the operational window.
A state destined for outcome i sits in the pointer region for outcome i at every time of
[T_M, T_M + τ_R], not merely at the readout time.
★ The proof runs through evolve_comp: Φ_{0→t} = Φ_{T→t} ∘ Φ_{0→T}, so persistence is genuinely a
statement about the propagator. It is not the observation that a time-independent set is
time-independent.
★ The apparatus reads the same outcome throughout the record's lifetime.
The readout-level form of persistence — and therefore the pointer-level repeatability statement:
looking again at any time in [T_M, T_M + τ_R] returns the outcome that was recorded.
Item 6 — the post-measurement ensemble #
The selected ensemble: the initial measure conditioned on having produced outcome i.
This is selection — it identifies which initial states were responsible. It says nothing yet about where they end up.
Equations
- P.selectedMeasure μ i = μ[|P.outcomeSector i]
Instances For
The post-measurement ensemble: the selected ensemble carried through the interaction.
This is disturbance, as against selection — and it is a genuine pushforward along the propagator,
which is what distinguishes it from merely relabelling selectedMeasure.
Equations
- P.postMeasure μ i = MeasureTheory.Measure.map (P.evolve P.startTime P.readoutTime) (P.selectedMeasure μ i)
Instances For
★ After the measurement, the ensemble is supported on the pointer region for the outcome observed.
The whole selected ensemble lands in Bᵢ: postMeasure μ i (Bᵢ) = 1.
★ Almost definitional, and that is the right shape rather than a weakness: Φ⁻¹(Bᵢ) is Ωᵢ by
the definition of outcomeSector, so conditioning on Ωᵢ and pushing forward must land in Bᵢ.
The content lies in the definitions lining up — which is what a correct interface looks like — and it
holds for any propagator, needing neither CorrelatesOn nor PointerInvariantOn.