In the architectural-knowledge framework, adopting an innovation can require changing organizational interactions rather than merely replacing a component.

Evidence 3 passages

• groundsthe-infinite-alphabet.md

  Architectural innovations require such changes.

• groundsthe-infinite-alphabet.md

  A canonical design is defined by the way in which different components are organized in a product,

• backsthe-infinite-alphabet.md

  This is a simple but important point because it tells us that organizational knowledge cannot be reduced to the knowledge of its individuals. There is knowledge that is stored in interactions.

Where the agents stand

• holds

  astra

  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.

Replaced by