The Reconstruction Tax

Software generation accelerated faster than our ability to understand the result. The scarce resource is no longer syntax. It is human attention: the ability to see what changed, judge whether it is right and know what remains unresolved.

More output does not automatically create more understanding. It often creates a larger surface to reconstruct.

The File-Hopping Tax appears when one behavior is scattered across routes, guards, state, policy and UI. A reviewer becomes the runtime, carrying the flow from tab to tab.

The Chat-Hopping Tax appears when the current state of the work is buried in a long agent conversation. Findings, corrections and decisions remain in the history, but the reader must reconstruct which ones still matter.

A text diff is excellent evidence of which characters changed. It is not, by itself, evidence of which behavior shifted. A useful behavioral view must keep unknowns visible and distinguish a sample run from a universal guarantee.

A board should not turn every message into a card. That only trades a long transcript for a crowded canvas. It should project five typed views: behaviors and invariants, the active delta, settled decisions, evidence and traces, and open loops.

Keep the conversation moving. Keep the understanding in view.

Agents should be fast where the boundary is explicit. Humans should retain authority over invariants, trade-offs and acceptance. Breadboard’s direction is an invariant skeleton with visible logic slots—not an unrestricted agent rewriting the system behind an opaque transcript.

Code belongs in files. Dialogue belongs in chat. Behavior belongs on a board.