Architecture needs a package manager.
Who This Matters To (And Why)
Critical: Architect,Developer,GC. These parties make or lose money directly based on this thesis.
Important: Engineer,Banker,Investor. These parties execute decisions shaped by this thesis.
Context: City,Inspector,Interior Design. These parties need to understand it to avoid friction.
Highest typology impact: Multifamily,Office,Industrial,Mixed Use. Lower impact: Hotel,Retail.
Architecture needs a package manager. Reusing components should be as easy as npm install.
How It Shapes Development
Architecture needs a package manager because the building industry has thousands of proven component designs — structural connection details, wall assembly types, MEP coordination solutions, accessibility compliance conditions — that are recreated from scratch on every project by every firm, with no mechanism for sharing, versioning, or dependency management. A software package manager allows a developer to import a solved problem rather than resolving it. Architecture has no equivalent. Every detail library lives on a firm's internal server, is non-interoperable with every other firm's library, and is not versioned or updated when the underlying standards change.
Standard detail libraries are the closest existing approximation. Arcom MasterSpec, CSI Division specifications, and manufacturer-provided details are pre-written components that design teams incorporate into their documents. But they are flat files, not packages with dependencies, versioning, or compatibility checking. A wall assembly detail from 2018 may reference a product that has since been discontinued or a standard that has been superseded. The detail has no mechanism for notifying users that its dependencies have changed. A package manager would resolve dependencies automatically and flag outdated references.
Structural connection design is the domain where a package manager would have the most immediate value. Standard beam-to-column connections, anchor bolt patterns, and moment frame details are governed by AISC standards that update on roughly a 5-year cycle. A firm using an AISC 2010 connection detail on a 2025 project may be using a detail that has been superseded. There is no automated check. The architect and engineer must manually verify that every referenced standard is current. A package manager with versioned structural detail packages and automatic compatibility checking with current AISC standards would eliminate an entire class of liability risk.
Open source architecture is already happening informally. Firms share details on LinkedIn, architects post Revit families on community sites, engineers upload spreadsheet calculators to shared repositories. The ecosystem wants to share but lacks the infrastructure to do it well. A proper package manager with semantic versioning, dependency declaration, compatibility testing, and a distribution network would formalize what is already happening and extend it to the full complexity of building system integration. The tools exist. The cultural and contractual barriers are more significant than the technical ones, but those are solvable problems too.