Skip to content
PointSav Digital Systems

Revision as of · 9e782ef0

Historical revision — this record as it stood on 30 June 2026, not the current version. View the current record →

BIM and real property surfaces

BIM and real-property surfaces describes how the PointSav platform treats Building Information Modelling as a first-class operational domain within a real-estate customer deployment. The platform provides dedicated design-system tooling, ISO 19650 record-keeping conventions1, and Totebox archive patterns for real-property data. BIM components, tokens, and geospatial primitives live in a separate customer-tier design system (woodfine-design-bim) distinct from the vendor pointsav-design-system — this article summarises the integration points; the detailed BIM content is in woodfine-design-bim. By the end of this article, a reader will understand the two-design-system boundary, the ISO 19650 suffix discipline, and the Chart of Accounts placement for BIM contributors.

Two design systems, deliberately separate

The single most important structural clarification: PointSav operates two distinct design systems, not one design system with a BIM sub-section.

Design system Repository Audience Domain
pointsav-design-system github.com/pointsav (vendor) PointSav contributors and fleet operators UI and UX substrate for os-console, os-workplace, and the full vendor OS family as described in the design philosophy
woodfine-design-bim github.com/woodfine (customer) Architects, engineers, real-property operators BIM tokens, IFC components2, geospatial visual primitives, real-property design system

The two systems share authoring methodology — a common structured-metadata schema, the six-tier sovereignty structure, strict lowercase-hyphenated naming — but they do not share content. The separation is structural: BIM concerns real property; the vendor design system concerns operating-system surfaces. Content or tokens that are specific to BIM workflows belong in woodfine-design-bim, never in pointsav-design-system.

The intended public deployment for woodfine-design-bim is bim.woodfinegroup.com. Full BIM component specifications, token definitions, and geospatial primitives are maintained there.

ISO 19650 record-keeping suffix discipline

BIM document management operates under ISO 196501, which defines explicit document-state codes for every artefact. The PointSav deployment adopts these codes as filename-suffix conventions so that audit tooling can read document state directly from the filename.

Suffix ISO 19650 status Meaning
_JW S0 Work in progress — draft, not yet shared
_FIN S4 Final, shared for approval or coordination
_PUB A0 Published and approved for use
_EXE CR Executed or signed — record or as-constructed state
_MCH / _DAT (matches parent) Machine-readable version of the parent document

Audit tooling reads the suffix and routes accordingly. A _PUB file is signed and treated as immutable; a _JW file is in flight and does not carry verified status. A _EXE file has passed F12 operator confirmation and enters the Totebox archive as a sealed record under the WORM ledger discipline.

The suffix discipline applies to every BIM artefact that enters the Gravity Engine — whether a drawing, a coordination model, a permit, or a lease record. This makes the record-keeping posture consistent with the broader WORM ledger discipline across the platform.

BIM contributors in the Chart of Accounts

In the institutional Chart of Accounts, BIM-domain contributors occupy a specific structural socket:

Profile Domain Sub-Domain Anchor archetype
IT Support Contributors BIM The Engineer

This placement is not aesthetic. It determines how service-people sockets BIM contributors when their work product enters service-content. A BIM modeller, a BIM coordinator, and a structural engineer all occupy the Engineer archetype slot under IT Support → Contributors → BIM, which means the platform applies the same evaluator key (logic_efficiency) and the same task-routing logic to their output.

BIM contributors sit structurally adjacent to DevOps, Networking, Database, Backend, GIS, and IoT workers — all Engineer-archetype positions under IT Support. This adjacency means BIM work inherits the same computational treatment as other data-and-logic disciplines, rather than being classified under Compliance or Real Estate where a different archetype governs.

BIM-adjacent operating-system surfaces

Three os-console surfaces are planned for BIM-domain work. All three are aspirational and carry appropriate forward-looking language.

Planned surface Function
app-console-bim High-fidelity BIM viewer and review; intended to read IFC files via an IFC-native Rust library; renders B-rep geometry via a Rust geometry kernel
app-console-bim GIS variant Geospatial overlay and analytics via a Rust-native whitebox toolset; intended to replace legacy C++ geospatial tooling
app-console-bim Maps Console Spatial visualisation with a map-driven Console layout

Each planned surface is single-purpose and Rust-native. The substrate design explicitly avoids legacy C++ BIM tooling, which carries decades of accumulated complexity and exceeds the hardware profiles of the lower Totebox tiers.

The F12 input gate handles BIM document ingestion — an operator drags an IFC or drawing file into F12, selects the Chart-of-Accounts destination, confirms the extracted entities, and the file enters the Totebox archive with an ISO 19650 suffix and a timestamped audit record.

See also

  • woodfine-design-bim — the customer-tier BIM design system (maintained separately at github.com/woodfine)
  • archetypes-and-chart-of-accounts — the Chart of Accounts and eleven archetypes taxonomy
  • totebox-os — the Totebox operating system that hosts real-property archives
  • app-console-input — the F12 input gate through which BIM documents enter the platform
  • service-content — the Gravity Engine that classifies and routes BIM documents
  • worm-ledger-design — the WORM ledger substrate that seals real-property records

  1. International Organization for Standardization, ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). Part 1: Concepts and principles. https://www.iso.org/standard/68078.html ↩ ↩2

  2. buildingSMART International, Industry Foundation Classes (IFC) — the open BIM standard for building data exchange. https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/ ↩

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →