Eight token primitives. Eighteen components. Cities as design-system publishers.
The AEC equivalent of a foundation design system, anchored on IFC 4.3 and Uniclass 2015. Designers who already know Revit, ArchiCAD, BricsCAD, or Bonsai already know the substrate.
- Token categories
- 8
- Component recipes
- 3
- Research backplane entries
- 3
What this is
A flat-file BIM substrate that travels with the building. The archive is a directory of plain-text and standardised-binary files (IFC-SPF, BCF 3.0, IDS 1.0, COBie, glTF, CityJSONSeq, per-element YAML sidecars, hash-addressed object store) readable for decades after any specific software vendor is gone. The building outlives the software; the file format outlives the vendor; the archive travels with the land.
Five hyperscaler-incompatible capabilities
- Asset-anchored BIM. The digital twin is signed with the land title and transfers with the deed.
- Offline-capable BIM for field use. Basements, rooftops, air-gapped defence facilities, regulated healthcare campuses.
- Vendor-obsolescence-survivable BIM. Buildings live 50+ years; file formats outlive the vendors that wrote them.
- IoT integration directly into the BIM archive. Sensor readings as per-element YAML sidecars; data never leaves the owner's premises.
- BIM + lease register + financial ledger as one portable archive. For a property owner these are the same asset.