Refresh #
Explicit initialization by labeled refresh #
During the first m requests, label k is matched and replaced at step
k < m. Labels below k have already been refreshed, while labels at or
above k still denote the original supply. This makes it impossible for
the initialization schedule to delete a previously refreshed label.
Spatial.lean is deliberately not imported here: its current dependency on
the transport development is transient. Exact coordinates are instead
parameterized by a unit-interval location rule. The count projection and
its law are independent of that rule.
Replace exactly the labels whose indices are strictly below k.
Equations
Instances For
Immediately before step k, label k still denotes original supply.
Immediately after step k, label k denotes its replenishment.
Advancing the schedule cannot alter a previously refreshed label. Both sides equal that label's prescribed replenishment.
Advancing step k also leaves every label strictly above k alone.
The leaf-count state after the first k labeled replacements.
Equations
- FD1D.refreshState initial replenishment k = FD1D.assignmentState (FD1D.refreshAssignment initial replenishment k)
Instances For
After all m replacements, the count state forgets the initial supply.
An arbitrary labeled supply configuration at the resolution used by the count chain. No distributional assumption is imposed on the initial supply.
Spatial coordinate of each labeled supply item.
- leaf : DyadicAssignment L m
Dyadic leaf assigned to each labeled supply item.
Instances For
Coordinates for every possible replenishment-leaf assignment. This is the
coordinate-level parameter used while Spatial.lean is unavailable.
- location : DyadicAssignment L m → Fin m → ℝ
Replenishment coordinates associated with each dyadic assignment.
Instances For
The realized labeled replenishment configuration for outcome ω.
Instances For
Count projection of a labeled supply configuration.
Equations
Instances For
The labeled configuration after the first k replacements.
Equations
- One or more equations did not get rendered due to their size.
Instances For
For every replenishment outcome, the terminal count state is exactly the fiber-count state of that outcome.
At step k, the scheduled match removes original label k, not any label
that was replenished at an earlier step.
The count-state law after k scheduled replacements, with all replenishment
leaf labels sampled jointly from the uniform law on assignments.
Equations
- FD1D.refreshCountLaw initial R k = FD1D.FiniteLaw.map (fun (ω : FD1D.DyadicAssignment L m) => (initial.refresh (R.supply ω) k).countState) FD1D.FiniteLaw.uniform
Instances For
The explicit m-step schedule has exactly the iid refreshed count law,
independently of the arbitrary initial supply and coordinate rule.
Cost at initialization step j: match the request to label j in the
configuration just before that label is refreshed.
Equations
Instances For
The scheduled step always matches the still-unrefreshed original label.
The total cost of matching each initialization request to its old label.
Equations
Instances For
The pathwise schedule cost is independent of replenishment outcomes.
Every initialization match has cost at most one.
The complete m-step initialization period costs at most m.
The final finite-horizon wrapper. Its first conclusion identifies the
explicit schedule's terminal count law with refreshedLaw; its second
conclusion invokes the main arithmetic theorem with the initialization bound
proved above, so neither fact remains a hypothesis.