Building Design

@@ -27,12 +27,11 @@ Building Design covers the design system behind every Woodfine building: a fixed

## Design Philosophy and System

[[bim-design-philosophy|BIM Design Philosophy]] states the core commitment: buildings are designed to comply with jurisdictional code at the design stage, not checked for compliance afterward. [[design-system-bim|The Building Design System]] and [[flat-file-bim-leapfrog|Flat-File BIM Leapfrog]] set out the planned coordination layer and the five architectural constraints — flat-file storage, open standards, offline-first operation, and Apache 2.0 licensing — that keep a building's digital record usable independent of any vendor. [[bim-market-context|BIM Market Context]] and [[open-bim-regulatory-acceptance|Open BIM and Regulatory Acceptance]] cover the government mandates already pushing the AEC industry toward the same open standards. [[aec-interface-conventions|AEC Interface Conventions]], [[bim-aec-muscle-memory|AEC Muscle Memory]], and [[property-manager-bim-gap|the Property Manager BIM Gap]] cover the interface conventions the planned tools borrow and the handover problem — models most facility managers never actually use — that this practice is designed to close.
[[bim-design-philosophy|BIM Design Philosophy]] states the core commitment: buildings are designed to comply with jurisdictional code at the design stage, not checked for compliance afterward. [[design-system-bim|The Building Design System]] sets out the planned coordination layer that keeps independent BIM authoring surfaces working from a shared specification vocabulary. [[bim-market-context|BIM Market Context]] and [[open-bim-regulatory-acceptance|Open BIM and Regulatory Acceptance]] cover the government mandates already pushing the AEC industry toward the same open standards. [[aec-interface-conventions|AEC Interface Conventions]], [[bim-aec-muscle-memory|AEC Muscle Memory]], and [[property-manager-bim-gap|the Property Manager BIM Gap]] cover the interface conventions the planned tools borrow and the handover problem — models most facility managers never actually use — that this practice is designed to close.

<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: design-philosophy-and-system -->
- [[bim-design-philosophy]] — Woodfine's buildings are designed to comply with jurisdictional codes at the design stage, rather than being checked for compliance after the fact — a consequence of building on open, portable standards from the outset.
- [[design-system-bim]] — A planned design-system platform for the built environment — the missing coordination layer that would let independent BIM authoring surfaces work from a shared specification vocabulary, the way a software design system keeps independent product teams consistent.
- [[flat-file-bim-leapfrog]] — The Building Design System is constructed on five architectural constraints — flat-file storage, open standards, Rust and Tauri, offline-first operation, and Apache 2.0 licensing — enabling vendor-obsolescence-survivable building information models. Asset-anchored ownership, offline capability, IoT integration, and convergence of BIM with lease and financial ledgers follow from the architecture itself.
- [[bim-market-context]] — Government BIM mandates across the UK, EU, and other jurisdictions require open, vendor-neutral data formats; Woodfine's buildings are designed and specified against those open standards from the outset.
- [[open-bim-regulatory-acceptance]] — Building Information Modelling is mandated across most G7 economies for public procurement, with open, vendor-neutral standards as the delivery requirement rather than proprietary formats.
- [[aec-interface-conventions]] — BIM authoring tools across the industry share a common interface vocabulary — a spatial hierarchy, an element properties panel, a 3D viewport, and saved views — because they build on the same underlying IFC data model, giving PointSav's planned interface layer a shared foundation to build on rather than inventing a new one.
@@ -42,14 +41,12 @@ Building Design covers the design system behind every Woodfine building: a fixed

## BIM Objects and the Digital Record

[[bim-objects-what-they-are|BIM Objects]] are Woodfine's term for a reusable building-element specification that carries its own code and performance requirements with it. [[bim-objects-substrate|BIM Objects — Substrate]] and [[bim-objects-three-layers|BIM Objects — Three Layers]] cover the fixed primitive categories objects are organized into and the three information layers — what it is, what jurisdiction requires, what climate requires — every object carries at once. [[city-code-as-composable-geometry|City Code as Composable Geometry]] and [[gis-as-bim-substrate|GIS as a BIM Substrate]] cover how regulatory requirements and location data feed directly into that specification. [[asset-anchored-bim-vault|The Asset-Anchored BIM Vault]] and [[3d-asset-tokens|the Three-Dimensional Asset Token]] cover how a building's own digital record is stored and versioned.
[[bim-objects-what-they-are|BIM Objects]] are Woodfine's term for a reusable building-element specification that carries its own code and performance requirements with it. [[bim-objects-substrate|BIM Objects — Substrate]] and [[bim-objects-three-layers|BIM Objects — Three Layers]] cover the fixed primitive categories objects are organized into and the three information layers — what it is, what jurisdiction requires, what climate requires — every object carries at once. [[asset-anchored-bim-vault|The Asset-Anchored BIM Vault]] and [[3d-asset-tokens|the Three-Dimensional Asset Token]] cover how a building's own digital record is stored and versioned.

<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: bim-objects-and-the-digital-record -->
- [[bim-objects-what-they-are]] — A BIM Object is Woodfine's term for a reusable building-element specification that carries its applicable code and performance requirements with it, so non-compliant configurations are caught at design time rather than at inspection.
- [[bim-objects-substrate]] — BIM Objects are organized into a small, fixed set of primitive categories — spatial elements, physical elements, materials, systems, performance thresholds, and more — each anchored to open industry standards (IFC, Uniclass, bSDD) rather than a proprietary schema, so a specification stays portable and verifiable across tools and vendors.
- [[bim-objects-three-layers]] — A BIM Object carries three layers of information at once — what it is, what its jurisdiction requires of it, and what its climate requires of it — with the stricter of the two requirement layers governing whenever both apply to the same property.
- [[city-code-as-composable-geometry]] — An architectural model that encodes regulatory requirements directly into element specifications as geometric and numeric constraints rather than applying them post-design, making non-compliant configurations structurally impossible by construction.
- [[gis-as-bim-substrate]] — What the PointSav GIS co-location dataset offers a BIM composition pipeline: cluster manifold fields, civic context layers, and stability guarantees.
- [[asset-anchored-bim-vault]] — A building's authoritative digital record structured as plain-text and standardized-binary files in a git-versioned directory, qualifying as an ISO 19650-conforming Common Data Environment that travels with the property deed.
- [[3d-asset-tokens]] — The archive's unit of stored data, combining an immutable binary payload, machine-readable metadata skeleton, and live taxonomic graph connection encoding provenance and context.
<!-- END AUTO-GENERATED -->