CONCEPT
Capability Hierarchy (Engelbart)
Engelbart’s three-level model of how augmentation systems actually improve—distinguishing the daily productive work from the improvement of that work from the improvement of the improvement process—and the insight that protecting the higher levels against the velocity of the lowest is the only institutional corrective to the bootstrapping paradox.
Douglas Engelbart’s capability hierarchy distinguishes three levels at which any
augmentation system can operate. At the A-level, the team uses the tools to do productive work: write code, build products, solve problems. At the B-level, the team improves the tools and processes used for A-level work: refines the interface, develops better methodologies, identifies failure modes. At the C-level, the team improves the process of improving: steps back from immediate work to examine whether the B-level approach is itself sound, whether the capabilities being developed are the capabilities that matter, whether the direction of the bootstrapping is wise. The hierarchy is not a ranking of prestige but a
dependency chain: the quality of A-level work depends on the quality of B-level improvement, which depends on the quality of C-level reflection. Each level operates on a different cycle time—A-level work happens daily, C-level improvement happens over longer periods that