CONCEPT
Augmentation vs. Automation
Engelbart's foundational distinction: automation <em>removes</em> the human from the loop, augmentation <em>redesigns</em> the loop so the human's participation becomes more powerful. The most consequential design decision of the AI decade.
The distinction between augmentation and automation is not a matter of emphasis but of architecture. Automation identifies a task, designs a machine to perform it, and removes the human — whose role approaches zero. Augmentation, by contrast, does not remove the human but redesigns the interaction so that the human's contribution (judgment, direction, purpose, evaluation) is amplified by the machine's speed, breadth, and consistency. The capability is a property of the system, not of either component alone. Engelbart drew this line in 1962. The computing industry has spent six decades stepping over it without noticing — consistently preferring automation because it produces cleaner metrics, easier sales pitches, and organizational changes that require only headcount arithmetic rather than rethinking what work is for.
In The You On AI Field Guide
Engelbart was precise about the distinction because precision was the only defense against a culture that would collapse it the moment it became inconvenient. The computing industry, from the 1960s onward, demonstrated a persistent tendency to describe