Floor plans are APIs.
Who This Matters To (And Why)
Critical: Architect,GC,Developer. These parties make or lose money directly based on this thesis.
Important: Engineer,Interior Design,Banker. These parties execute decisions shaped by this thesis.
Context: City,Investor,Inspector. These parties need to understand it to avoid friction.
Highest typology impact: Multifamily,Office,Hotel,Mixed Use. Lower impact: Retail,Industrial.
A floor plan is an API. Every wall, door, and room is a contract between systems.
How It Shapes Development
Floor plans are APIs because they define the interface between the building's physical structure and the activities that occur within it. An API specifies what inputs a system accepts, what outputs it provides, and what constraints govern the exchange. A floor plan specifies what activities a space accepts (its program), what utilities it provides (plumbing, electrical, data, HVAC), and what constraints govern use (occupancy load, egress, ADA). A tenant who leases space is integrating their operations with the building's API. If the API doesn't match their requirements, integration fails.
Tenant improvement construction is API customization. The base building provides a standard interface: slab, ceiling height, HVAC stub-outs, electrical panels, plumbing chase locations. The tenant's requirements may differ from the standard interface: they need more electrical density, or a different HVAC zone configuration, or a wet lab with specific plumbing requirements. The TI build-out is the work of extending the base building API to match the tenant's interface requirements. Buildings with flexible, well-documented base building systems have lower TI costs because the API is easier to extend.
Building systems integration failures are API mismatches. A tenant who installs a commercial kitchen in a space without a grease interceptor has connected to a plumbing API that doesn't support their application. A data center tenant who requires 200 watts per SF of power density in a building designed for 5 watts per SF has connected to an electrical API that is 40x undersized. These mismatches are discovered during tenant design and resolved by expensive building system upgrades — or they prevent the lease from executing at all. API compatibility between tenant requirements and building systems is a material term in every commercial lease.
Open building theory formalizes the floor plan as a layered API. The support layer (structure, envelope) is the base API that changes rarely. The infill layer (partitions, ceilings, mechanical distribution) is the extension layer that changes at tenant turnover. The stuff layer (furniture, equipment) changes with individual users. Each layer has a different interface and a different lifecycle. Buildings designed with clean interfaces between layers have lower total lifecycle costs because each layer can be updated independently without disturbing the others. A building where the HVAC ductwork is embedded in the structure has conflated two layers with different lifecycles, making updates to either more expensive.