The first Kinewright engine now answers a command at the next step instead of at the end of a clip. This article shows what the stage adds, the numbers it stands on, and the limits it keeps on purpose: inside a transition a command still waits for the clip, and the stage says so with its figures.
What this stage adds
A runtime substrate under the page: a fixed tick of 120 Hz, commands as tick-stamped events, a journal of them, seeded random streams and a byte-for-byte replay. The same journal gives the same bytes in two processes, and the same platform-stable digests on two machines of different architectures.
A step planner as the way a command is answered. A request is laid out at the next touchdown of either foot, in the frame of the clip it continues, and the five transitions — the start, the stop from a walk, the stop from a run, walk to run and run to walk — are laid out inside the accepted clips and held to them.…