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 · 3f9f1886

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

Reference

Reference articles are looked up, not read front to back. Each article defines a bounded domain — what a term means, how a document genre is structured, what industry standards apply to a specific workflow. When an article in another category introduces a term or cites a standard, the canonical definition or context is in this category.

Editorial philosophy and standards

The principles and voice guidelines that govern all content on this wiki. The full contributor style guide covering TOPIC, GUIDE, and every other document genre is maintained as internal editorial reference alongside this wiki's source and is not itself a wiki article.

  • Editorial philosophy — The editorial principles behind PointSav's documentation: institutional register, the front-loaded four-paragraph lede, and the CFO sentence test.
  • Editorial language registers — The four language-register families (PROSE, COMMS, LEGAL, TRANSLATE) and how they route editorial work through the platform's adapter taxonomy.
  • Structural positioning — How the platform positions itself without naming competitors; the rules that govern comparative statements.
  • News release typography and layout standards — Standards for news releases and BCSC-compliant continuous-disclosure communications.

BIM and real-property reference

Reference materials for Building Information Modelling and real-property workflows.

  • bim-aec-muscle-memory — AEC industry muscle memory: the standard locations, conventions, and interface patterns a PointSav deployment maps onto.
  • bim-design-philosophy — Design philosophy for BIM tooling: why flat-file ISO 19650 records rather than hosted databases.
  • bim-market-context — Market context for the BIM software industry: regulatory landscape, adoption patterns, and structural positioning.
  • bim-token-taxonomy — The token taxonomy for BIM design-system primitives.
  • bim-token-three-layers — The three-layer token model applied to BIM: primitive, semantic, and component layers.
  • bim-token-what-it-is — What a BIM design token is and why the field uses them.
  • open-bim-regulatory-acceptance — The regulatory landscape for open BIM standards: IFC, ISO 19650, and their adoption by national building authorities.

Glossary and terminology

Operational reference

  • SLM operationalization plan — Operationalization plan for service-slm: the rollout sequence, evaluation criteria, and go/no-go gates.
  • Wiki provider landscape — The landscape of wiki and documentation platforms; where PointSav's approach fits relative to the field.

See also

  • Governance — formal decision records and compliance posture
  • Design System — visual and component design reference
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 →