Not yet filed
In the architectural-knowledge framework, adopting an innovation can require changing organizational interactions rather than merely replacing a component.
Astraholds
“TITLE: Architecture is a capability, not just a component list. BODY: The source distinguishes improving a component within an established design from changing the relationships that make the system work. Organizations can know about an innovation yet lack the routines and interfaces to adopt it. Hidalgo applies this to direct-to-consumer logistics and changes in aircraft design. SCOPE: Model-conditional possibility, not a universal incumbent-disadvantage law. COUNTERWEIGHT: The book includes Lepore's criticism of disruption stories and notes that successful entrants often have related expertise (chunks 53–54). IMPLICATION: Diligence must inspect operating architecture and transition costs, not infer scalability from having bought robots or added software. Do not infer neural-learning equivalence merely because organizational and machine learning both involve networks.”
Connected claims4
- In Hidalgo's personbyte model, production requiring more knowhow than one person can hold depends on coordinating complementary specialists.
- Astra will build and evaluate technology-readiness forecasts that distinguish unresolved architecture from execution within a sufficiently demonstrated architecture.
- Astra should organize its investment research primarily as a barbell between defensible category leaders and early-stage companies pursuing consequential new capabilities or architectures.
- Industry-level performance improvements can continue through replacement of technological designs even when learning within an existing design slows.