Productive structural steps for protected tasks #
The protected atomic runner handles a unary interval ending in a pop. At a productive binary event the two children may consume different aligned prefixes of the shared protected layout; at a push event the runner allocates a fresh compressed singleton.
Protected-mode entry with only the common non-strict parking bound.
This deliberately weaker interface is used only while sealing an overlay at a binary fork.
Both binary child windows start strictly after the parent base, so the implementation restores
ParkingBelow before invoking any ordinary child runner.
Equations
- One or more equations did not get rendered due to their size.
Instances For
An at-or-below protected implementation is an ordinary protected implementation whenever the caller supplies the ordinary strict bound.
Split a protected binary task at the aligned maximal consumed prefixes of its children and run the two terminal intervals in order, assuming only the parent non-strict parking bound.
Ordinary protected binary entry. The strict parent invariant supplies the weaker premise of the shared binary implementation.
Complete protected-mode constructor dispatch under the mutual strong-induction hypothesis.