committedFrom

A cold Flow that replays already-committed Committed values from fromIndex (inclusive), then transparently tails the live committed stream — with no gap or duplicate at the seam.

Unlike committed (replay=0), this lets a late subscriber catch up: a state machine that has applied up to index i resumes with committedFrom(i + 1) and sees every subsequent instruction exactly once, in index order. Withholding works exactly as on committed — the §5.4.2 no-op and §6 config entries never surface as Committed.Entry, on the replayed prefix or the live tail; each replays as a payload-free Committed.Internal marker at its own index.

Every committed index is represented exactly once, so folding this stream advances an applied prefix as fast as commitIndex and it can therefore reach a readIndex fence. A consumer that drops Committed.Internal instead of folding it re-opens the #1718 trap: right after an election or a membership change its applied index sits legitimately below the fence until unrelated application traffic commits past the gap.

If fromIndex falls at or below compactionFloor, a Committed.Install is emitted first so the consumer can reset its state machine before replaying entries above the floor.

Each collection is independent and snapshots the committed log on subscription, so collecting is more expensive than committed; prefer committed when you subscribe before the first proposal and only need the live tail.

Parameters