Skip to content
PointSav Digital Systems

BIM and real property surfaces

← All revisions

79eb6d43 · PointSav Digital Systems ·

enrich wikilinks: documentation applications body (EN+ES) batch 2

View the full record as of this revision →

@@ -30,10 +30,10 @@ The single most important structural clarification: PointSav operates two distin

| Design system | Repository | Audience | Domain |
|---|---|---|---|
| `pointsav-design-system` | `github.com/pointsav` (vendor) | PointSav contributors and fleet operators | UI and UX substrate for [[console-os|os-console]], [[os-workplace]], and the full vendor OS family |
| `pointsav-design-system` | `github.com/pointsav` (vendor) | PointSav contributors and fleet operators | UI and UX substrate for [[console-os|os-console]], [[os-workplace]], and the full vendor OS family as described in the [[design-philosophy|design philosophy]] |
| `woodfine-design-bim` | `github.com/woodfine` (customer) | Architects, engineers, real-property operators | BIM tokens, IFC components[^2], 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 two systems share authoring methodology — a common structured-metadata schema, the [[six-tier-sovereignty-matrix|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.

@@ -49,7 +49,7 @@ BIM document management operates under ISO 19650[^1], which defines explicit doc
| `_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 operator confirmation and enters the [[totebox-os|Totebox]] archive as a sealed record.
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 [[app-console-input|F12 operator confirmation]] and enters the [[totebox-os|Totebox]] archive as a sealed record under the [[worm-ledger-design|WORM ledger discipline]].

The suffix discipline applies to every BIM artefact that enters the [[service-content|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-design|WORM ledger]] discipline across the platform.
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 →