Management Infrastructure for Autonomous Enterprises https://npcmemo.substack.com
- 0 replies
- 1 recast
- 2 reactions
Both Fat Protocol and Fat App Thesis are wrong. “Technological revolutions cement their legacy in the slow consolidation that follows the fever pitch of their inception. From the print revolution to contemporary artificial intelligence, transformative innovations undergo an installation period of exuberant experimentation and capital inflows, followed by a deployment period wherein common standards, infrastructures, and institutions harden into place. This essay charts five historical and contemporary case studies – early modern printing, industrial manufacturing, the internet, blockchain-based finance, and modern AI – to illustrate how durable “fat” forms emerge only when coordination becomes structurally unavoidable in deployment, rather than at speculative peaks during installation. Drawing on Elizabeth Eisenstein’s insights on print’s epistemic scaffolding, Carlota Perez’s model of installation/deployment cycles, David Lang’s view of standards as coordination rails, Klepper and Hounshell’s studies of industrial consolidation, Adrian Johns’s work on trust regimes, histories by Janet Abbate and others on internet chokepoints, and analyses by the BIS and technologists like Joel Monegro and David Phelps on blockchain dynamics, the essay develops a “stabilization stack” framework.” https://npcmemo.substack.com/p/eisensteins-spine-and-technology
- 0 replies
- 1 recast
- 8 reactions
“This essay traces how “procurement” is moving into the runtime path of software. In today’s agent workflows, service selection is often manual, improvised, and weakly governed: developers paste API docs into LLMs, hardcode keys, upload PDFs as ad hoc context stores, and rely on interfaces that auto-route models or browse the web. The resulting system is efficient only locally and often fails institutionally across cost control, licensing, security, and auditability. Historical precedents—AppExchange-style connector selection, AWS Marketplace entitlement/metering APIs, service meshes, and API-native payments—suggest a missing layer: runtime procurement for agent capability exchange. The essay names its incentives, failure modes, and likely choke points.” https://npcmemo.substack.com/p/liquid-services-and-runtime-procurement
- 0 replies
- 0 recasts
- 2 reactions