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 · 36eaf5c9

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

The Flat-File BIM Leapfrog

The Flat-File BIM Leapfrog

PointSav’s Building Design System achieves a structural competitive advantage by adopting five architectural constraints that are individually simple but collectively occupy a market category hyperscalers cannot enter without cannibalizing their own revenue models. By prioritizing flat-file storage, open standards, a Rust-based offline-first architecture, and the EUPL license, Foundry delivers a BIM substrate that is inherently owned by the asset holder rather than rented from a cloud vendor.

Structural Constraints as Competitive Moat

The strategy is predicated on five foundational architectural decisions:

  1. Flat-File Storage: All building data resides in human-readable, plain-text files.
  2. Open Standards: Strict adherence to ISO-standardized IFC, IDS, and BCF.
  3. Rust + Tauri: A high-performance, memory-safe execution environment.
  4. Offline-First: Full functionality without mandatory internet connectivity.
  5. EUPL-Licensed: Open-source legal protection that is procurement-friendly for governments.

Production Maturity of the Open BIM Stack

As of 2024, the open BIM standards stack has reached sufficient maturity for commercial-grade infrastructure. IFC 4.3 (ISO 16739-1:2024) extends the schema from buildings to civil infrastructure, including bridges, rail, and waterways. The canonical serialization (IFC-SPF) remains a plain-text format (ISO 10303-21) that is readable in any standard text editor.

Foundry canonicalizes on IFC-SPF today, with intended opportunistic mirroring to ifcJSON. While IFC 5/IFCX is in development, the PointSav architecture is designed such that future migration is intended to be a serialization swap rather than a core rewrite.

Flat-File Definition and Taxonomy

"Flat-file BIM" refers to a directory of plain-text and standardized binary files accessible without proprietary SDKs.

Format Standard Role
IFC-SPF (.ifc) ISO 16739-1:2024 Authoritative geometry + semantics
IDS 1.0 buildingSMART (2024) Validation contract
BCF 3.0 buildingSMART Collaboration history
Per-element YAML Local Convention Sensor and work-order metadata
glTF 2.0 ISO/IEC 12113:2022 Visualization cache

The .ifc file serves as the authoritative spatial state, while YAML sidecars handle dynamic data such as sensor readings and lease references.

Five Differentiated Capabilities

1. Asset-Anchored BIM

The digital twin travels with the property deed. Unlike multi-tenant SaaS models where data is "rented," a flat-file twin is owned like the physical building—permanently and transferably.

2. Offline-Capable Field Operations

By construction, cloud-authoritative twins are unusable in air-gapped facilities, basements, or remote construction sites. Foundry preserves full BIM functionality without network dependency.

3. Vendor-Obsolescence Survival

Buildings have a 50-year lifespan; proprietary formats often last fewer than five. A flat-file substrate ensures data remains readable for decades after the software vendor disappears.

4. Direct IoT Integration

Per-element YAML sidecars ingest sensor data via local MQTT brokers. This eliminates sensor-count-based token charges and satisfies strict data residency requirements (GDPR, HIPAA).

5. Unified Asset Archive

The building, lease, and ledger converge into a single portable archive. The Totebox Archive is the first architecture where a building’s legal, financial, and spatial identity are a single, portable artifact.

Regulatory and Security Alignment

The architecture satisfies mandatory open-standard requirements for US federal agencies (GSA, VA), EU member states, and Singapore’s CORENET X. It is uniquely positioned to meet ITAR air-gapped requirements and EU Data Act sovereignty mandates.

Strategic Trade-offs

PointSav acknowledges that real-time multi-user design workshops are currently faster in synchronous cloud SaaS. Additionally, while the substrate is designed to be AI-ready, a generative BIM authoring tool is not planned for the v0.0.1 release. These are deliberate trade-offs to prioritize an offline-first, vendor-independent posture.

Copyright © 2026 Woodfine Capital Projects Inc. Licensed under Creative Commons Attribution 4.0 International.

Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.

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 →