BIM design philosophy
AI-readable research file. Served by
app-orchestration-bimat/research/bim-design-philosophyand consumed by AI agents as Markdown context.
The Foundry Building Design System is built on a single architectural stance: PointSav’s existing constraints — flat-file storage, open standards, Rust + Tauri, offline-first, EUPL-licensed, seL4-hardened — are not stylistic choices. They are the precise set of constraints that make five hyperscaler weaknesses into customer-visible differentiators.
Hyperscalers (Autodesk, Bentley, Trimble, and the broader IWMS incumbents like Planon, IBM Tririga, Eptura Archibus) sell different- looking products that share an identical architectural spine. Five foundational assumptions underpin all of them, each one simultaneously a revenue mechanism and a structural vulnerability:
- The authoritative database lives in the vendor’s multi-tenant cloud.
- Access to the customer’s own data requires a live subscription check.
- Interoperability is achieved through lossy export/import, not native format.
- AI must run in vendor tenancy on vendor-controlled data.
- The economic unit is the seat, or the token, per month.
A sixth — version lock (Revit 2025 cannot open in 2024) — is arguably the most effective lock-in mechanism ever shipped in AEC software. The flat-file BIM substrate refuses each of these by construction.
What the substrate is
A directory of plain-text and standardised-binary files that an ordinary text editor or SVG viewer can open without a proprietary SDK, decades after the software vendor that produced it is gone.
| Format | ISO / publisher | Role |
|---|---|---|
IFC-SPF (.ifc) | ISO 16739-1:2024 | Authoritative geometry + semantics |
| IDS 1.0 | buildingSMART (June 2024) | Validation contract |
| BCF 3.0 | buildingSMART | Per-topic collaboration history |
| COBie via ifccsv | NIST | Asset handover spreadsheet |
| Per-element YAML sidecars | local convention | Pset_* + sensor + work-order |
| Speckle-inspired object store | local convention | Hash-addressed Merkle DAG |
| glTF 2.0 | ISO/IEC 12113:2022 | Visualization cache (regenerable) |
| SVG | ISO/IEC 14496-22:2019 | 2D drawings (regenerable) |
| CityJSONSeq | OGC | Portfolio / urban context |
The building’s authoritative state is the .ifc file plus the
sidecars. Visualisation derivatives are caches; they regenerate at
will from the authoritative source. Any specific BIM viewer or BIM
authoring tool is replaceable; the archive is permanent.
What the substrate is NOT
- Not an authoring tool.
app-workplace-bimis the authoring tool layered on top. - Not a SaaS platform. Every byte lives on the customer’s hardware. No cloud dependency.
- Not vendor-prescriptive. Open standards and open toolchains throughout. PointSav adds the convergence layer (BIM + lease + ledger) and the leapfrog invention (City Code as Composable Geometry); the substrate itself is open.
Five hyperscaler-incompatible capabilities
(From ~/Foundry/BIM_Buildable Architecture.md, April 2026.)
- Asset-anchored BIM — the digital twin signed with the land title and travelling with the property deed. Multi-tenant SaaS cannot offer this without breaking the tenancy model.
- Offline-capable BIM for field use — basements, rooftops, air-gapped defence facilities, healthcare campuses. ACC, Tandem, iTwin Experience cannot work offline by construction.
- Vendor-obsolescence-survivable BIM — buildings live 50+ years; Revit’s file format lasts three. The flat-file archive outlives the vendor by decades.
- IoT integration directly into the BIM archive — per-element YAML sidecars ingest sensor readings via local MQTT broker. No cloud intermediary; data never leaves the owner’s premises.
- Convergence of BIM + lease register + financial ledger — for a property owner, these are the same asset. Multi-tenant cloud cannot commingle them by construction.
Government regulatory acceptance
The format stack — IFC-SPF + IDS 1.0 + BCF 3.0 + COBie — fulfills the mandatory open-standard delivery requirements across US federal (GSA, USACE, VA, NAVFAC), EU member states (Germany, Italy, Spain, Denmark, Norway, Netherlands, Poland), the UK BIM Framework, Singapore CORENET X (mandatory October 2026), Dubai (mandatory since January 2024), and emerging Latin-American mandates.
The offline-first, flat-file architecture is the only approach that natively satisfies ITAR air-gapped requirements for defence projects, EU Data Act data sovereignty for European projects, HIPAA technical safeguards for VA healthcare facilities, and GDPR data residency for EU government clients. EUPL-1.2 is OSI-approved, FAR 12.212-compatible, and EU-procurement-preferred. The certifications path: buildingSMART IFC certification (highest leverage), buildingSMART openBIM software certification (EU procurement scoring weight), CMMC Level 2 readiness documentation (DoD subcontractor positioning).
References
~/Foundry/BIM_Buildable Architecture.md~/Foundry/.claude/sub-agent-results/A-bim-design-system-prior-art-2026-04-28.md~/Foundry/.claude/sub-agent-results/B-bim-city-code-as-geometry-2026-04-28.md~/Foundry/.claude/sub-agent-results/C-bim-regulatory-acceptance-2026-04-28.md- Doctrine claim #40 (proposed) — Flat-File BIM Substrate
- Doctrine claim #41 (proposed) — City Code as Composable Geometry