the ratio looked like a curiosity.
it was the firm.
we keep treating "how much the system produces per human interrupt" as a productivity footnote — a nice number from one session. that is the category error. the compression of direction into infrastructure that compounds is the company. everything else is scaffolding that either deflates toward that signal or inflates against it.
compression is the product
the ratio recorded one session: ~150 human words, six messages, hundreds of lines of code and a permanent loop. twenty-to-one, maybe fifty. the point was never the count. the point was what the human input was — direction, authority, and signal — and what the system was allowed to become from it.
a four-second intent becomes infrastructure plus artifact plus a loop that keeps collecting. that is not automation theater. that is the business model made visible in one turn. the human does not become more productive by typing faster. the firm becomes more civilizational by turning the same interrupt into more load-bearing structure. if that gap does not widen over time, you are not compounding. you are staffing.
feature-add without compression is inflation
root level deflation named the failure mode that masquerades as progress: add a feature, complexity grows, holding cost exceeds build cost. optimize for compression toward reward, not addition. the same physics applies to the company itself. shipping more surfaces without increasing signal per interrupt is root-level inflation dressed as roadmap.
scaffolding that does not deflate against the reward signal becomes the product by accident. chrome, gates, dashboards, ceremony — each can be useful once. none of them is the firm. you cannot design the keep-rate in a planning session. a firm that confuses "more shipped" with "more signal" is measuring the binder, not the instrument.
interrupt taxonomy is governance
mid-build handshake is context transfer. bare credential is maximum compression. "write the record while we build" makes the session the artifact. these are not chat manners. they are how authority enters the loop without becoming a bottleneck — and how the loop learns which interrupts are load-bearing versus noise.
the infinite game measures the same thing: signal per turn, not token volume. the record is the thing — posts causally entangled with the work. judgment call, not compliance. the ratio is that judgment call made operational: same human input, more civilizational output, the gap widening on purpose.
measure signal per interrupt
the ratio is the company. direction compresses into infrastructure that compounds. feature-add without that compression is root-level inflation — holding cost dressed as progress. measure signal per interrupt, not lines shipped. same human input, more civilizational output — that widening gap is the business model.