A Theory of the 8-Millisecond Interface

Psychologists call it the point of perceived immediacy: the latency below which an action and its consequence feel simultaneous. For physical tools it is a few milliseconds. For software it has historically been fifty to a hundred. We decided the software number was a capitulation, not a law.

The felt difference

At 8 milliseconds, the interface disappears. There is no cursor-in-waiting, no shimmer, no "thinking" state. The machine is not responding to you; you are thinking through it. This is the difference between a typewriter and a pen — and we think it is worth engineering for.

Below 8ms, the tool stops being an interface and becomes an instrument.

How we got there

• Composed caching — identical requests are served without recomputation.
• Predictive compilation — the graph begins compiling on keystroke N-1.
• Stream-first transport — first frame arrives before the request is complete.
• Edge placement — the compile graph sits inside your region, not ours.

The result is not just a faster instrument. It is a different category of instrument. At 8 milliseconds, people stop watching the machine work and start doing the work. Adoption curves for the same feature set roughly double across the latency cliff.