The Timing Gap

Modern compute infrastructure is built to react. The Timing Gap series argues that reaction is the wrong abstraction layer — and that the physical position required to act before commitment has always existed, unnamed, in every compute system ever built. Paper 1 establishes the problem: execution is committed before governance can intervene, and the gap between them widens as system density increases. Paper 2 names and defines the prime plane — the physical stratum between bare hardware and the OS scheduler, occupied by embedded controllers, BMCs, and power regulation firmware — and describes the admission narrowing authority that position carries. Paper 3 closes the argument at scale: infrastructure that requires additional coordination to handle additional load was never coherent to begin with. The line either works at any length or it was never a line. The three papers are intended to be read as a single argument.