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

Glossary and Reference

← All revisions

93edcda6 · PointSav Digital Systems ·

fix(index-topics): apply protocol-index-topic.yaml's scope_note (replaces what_this_is_not) across all 3 Index Topics per the ratified DESIGN-TOKEN-CHANGE — removes the H2 heading and roadmap/backlog language, shortens 71-89 words to 18-27; also removed reference/_index.md's Correction note (leaked internal frontmatter field names and 'MOC page' jargon, zero reader value, per register-documentation.yaml's new Provenance Notes rule). EN+ES, verified live via curl.

View the full record as of this revision →

@@ -16,15 +16,6 @@ editor: pointsav-engineering
paired_with: _index.es.md
---

**Correction (2026-08-04):** superseded a legacy MOC page (`slug: _index`, `type:
reference`, no `index_type`/`index_scope`) that listed only 10 of this category's 23
real articles — 13 were never added as the category grew. This is the same content
rebuilt against the Index Topic mechanism, with every current article included.
**Resolved, not silently dropped** — the legacy page's own 2 sections that no longer
apply (BIM/real-property reference, since that content moved to the projects wiki;
the 2 wikilinks now pointing to categories rather than articles) are not carried
forward, since both were already stale pointers, not real content.

**Reference material** on this platform serves two different needs: a reader who wants one term defined precisely, and a reader who wants to understand the vocabulary well enough to read everything else in this wiki without stumbling. Both needs live here — general computing concepts defined in plain language, the full platform glossary, orientation for a reader who hasn't picked a starting point yet, and the standards this wiki itself is written to.

<!-- START-HERE-HIGHLIGHT: engine reads this block to render the single "start here" card
@@ -72,9 +63,8 @@ forward, since both were already stale pointers, not real content.
- [[wiki-provider-landscape|Wiki provider landscape]] — a structural audit of why no existing provider has closed Wikipedia's gap
<!-- END AUTO-GENERATED -->

## What this is not

This page is not itself a definition source — for a specific term, go to the glossary directly rather than searching this list. It is not exhaustive of every reference-shaped fact in the wiki: architectural definitions live with their subject (`substrate/`, `security/`), not here. It does not distinguish platform-specific from general-computing terms visually — both live in this category because a reader consulting one is often also consulting the other.
For a specific term, go to the [[glossary-documentation|glossary]] directly. Architectural
terms are defined with their subject, not listed here.

## See also
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 →