Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

PointSav Digital Systems

Revision as of · 535d34ec

Historical revision — this record as it stood on 22 August 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 distinct operational domain within a real-estate customer deployment. BIM components, tokens, and geospatial primitives live in a separate customer-tier design system (woodfine-bim-library) distinct from the vendor pointsav-design-system — this article summarises the integration points; the detailed BIM content is in woodfine-bim-library. By the end of this article, a reader will understand the two-design-system boundary, the platform's real Chart of Accounts placement for BIM contributors, and the current (research-stage) state of BIM-specific console surfaces.

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 — the Command Ledger, Sovereign desktop, and the full vendor OS family as described in the design philosophy
woodfine-bim-library github.com/woodfine (customer) Architects, engineers, real-property operators BIM tokens, IFC components1, 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-bim-library, never in pointsav-design-system.

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

Document-status filename suffixes

Real-property source documents in the platform's working corpus carry filename suffixes such as _FIN (final, shared for approval or coordination) and _JW/_EXE (draft and executed/signed states), an informal convention that predates any platform tooling. Formalising this as an ISO 196502-mapped, machine-read status system — with service-bim inspecting the suffix and routing the document automatically — is a design intent for the BIM ingestion pipeline, not a built capability today: service-bim exists only as research and design notes, with no shipped ingestion, validation, or audit-routing code.

BIM contributors in the Chart of Accounts

The institutional Chart of Accounts carries a real entry for BIM work: category IT Support, type BIM (reference 6010), matched by keywords including bim, building information modeling, digital twin, revit, and ifc. BIM contributors sit in the same category as other technical-execution roles rather than under Compliance or Real Estate, where different categories apply.

BIM-adjacent operating-system surfaces

BIM-domain work on os-console — the Command Ledger is at the research stage — a design document exists (app-console-bim), no code has shipped. The intended shape, per that research: a single routing-and-coordination terminal (app-console-bim) distinct from an authoring surface (app-workplace-bim) — the split matches the platform's console/workplace distinction elsewhere, view-and-link versus create-and-edit. app-console-bim would query elements, link work orders, and create issues; it would not edit BIM geometry. For portfolios spanning multiple properties, a stateless aggregation layer (app-orchestration-bim) is intended to federate queries across property archives rather than store data itself. The research document's current technical direction favors browser-based IFC rendering (evaluating xeokit-sdk and @thatopen/components) over a native Rust geometry kernel — none of this is committed or built, and the direction may change before implementation starts.

See also

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

  2. 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 ↩

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. 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. The full trademark notice appears in the footer of every page on this site.

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 →