A safe publish accepts an update only if it extends the current published prefix; otherwise it keeps the current output (the implementation would emit a violation).
Instances For
Output-prefix safety (Invariant L.9 / Theorem L.19): a safe publish never regresses, so the stream of published outputs forms a chain under the prefix order and no position is ever rewritten.
Bounded-service core (Theorem L.14): with a positive fairness quantum, a continuously runnable wave accrues enough deficit credit to pay for a task of any cost after finitely many scheduler ticks, so it is not starved.