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. The internal §5.4.2 no-op (LogEntry.isNoOp) is withheld here too.

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