Lockstep to pipeline in almost one line

Lockstep systems update and render sequentially, which simplifies reasoning about concurrency but limits parallel writing to a single core. Pipelining allows phases to run in parallel, moving from a lockstep to a pipelined tick system. The phases still run on separate cores/threads in batches, waiting at barriers before the next tick.

This maintains back pressure and overrun tracking while enabling writing and reading simultaneously. Read consistency is ensured through read transactions wrapping each render batch, with all batches starting before the write batch completes, eliminating read skew. The pipelined system is almost unaffected compared to the lockstep system, with write and read operations occurring concurrently.