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

8347d27f · PointSav Digital Systems ·

docs(documentation): split reference into reference + new background category — 10 general-computing explainers move out of the consulted-not-browsed shelf

View the full record as of this revision →

@@ -8,7 +8,7 @@ content_type: topic
index_type: thematic
index_scope: reference
quality: complete
short_description: "The platform's lexicon and lookup material: orientation for a new reader, general computing terms defined plainly, the full glossary, and the standards this wiki holds its own writing to."
short_description: "The platform's lexicon and lookup material: the full glossary, orientation for a new reader, the catalogues other articles point to, and the standards this wiki holds its own writing to."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-09-06
@@ -16,7 +16,9 @@ editor: pointsav-engineering
paired_with: _index.es.md
---

**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.
**Reference material** on this platform is consulted, not browsed. A reader arrives here with a specific question — what does this term mean, which guide covers this task, what hardware is supported, what rule was this article written to — and leaves as soon as it is answered. That is what this category holds: the full platform glossary, the catalogues other articles point to, orientation for a reader who has not picked a starting point yet, and the editorial standards this wiki itself is written to.

General computing concepts — the field's own vocabulary, defined from first principles — moved to [Background](/category/background) on 2026-09-06. Those articles are written to be read through; the material here is not.

<!-- START-HERE-HIGHLIGHT: engine reads this block to render the single "start here" card
     (reuses the existing cluster-card--start-here component). Do not add more than one. -->
@@ -30,27 +32,12 @@ paired_with: _index.es.md
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: platform-orientation -->
- [[getting-started|Getting started with the PointSav platform]] — An orientation to the PointSav developer platform: what it is, who it is for, where to start, and how the pieces fit together before the first task.
- [[glossary-documentation|PointSav encyclopedia — glossary and lexicon]] — A canonical A-to-Z lexicon bridging standard industry terminology with PointSav platform concepts, with authoritative definitions across technical and financial domains.
- [[wiki-structure|How this knowledge base is organized]] — A reader's map of the platform knowledge base: fifteen areas covering what PointSav builds, how it's built, and why it can be trusted, for every reader.
- [[wiki-structure|How this knowledge base is organized]] — A reader's map of the platform knowledge base: sixteen areas covering what PointSav builds, how it's built, and why it can be trusted, for every reader.
- [[guide-catalog|Developer guide index]] — Developer guide index for the PointSav platform — task-oriented how-to guides organised by concern, from toolchain setup to session lifecycle.
- [[hardware-reference|Hardware reference]] — Reference hardware profiles for developer workstations and fleet devices, specifying CPU requirements including Haswell-generation x86_64 and fsgsbase support.
- [[service-slm-operationalization-plan|SLM operationalization plan]] — The plan for transitioning from externally hosted language model calls toward a per-tenant small language model substrate that heals via a feedback loop.
<!-- END AUTO-GENERATED -->

## General computing concepts

<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: computing-concepts -->
- [[application-programming-interface|Application programming interface]] — Defined interface that lets software systems communicate by specifying the available calls, how to make them, and the data formats exchanged.
- [[computer-appliance|Computer appliance]] — Computing device pairing hardware and software engineered for one well-defined function, deployed as a sealed unit that cannot be repurposed for general computing.
- [[edge-computing|Edge computing]] — Distributed computing paradigm that places computation and storage near data sources, cutting latency and bandwidth versus centralized cloud data centers.
- [[fog-computing|Fog computing]] — Distributed architecture placing compute, storage, and network services between edge devices and the cloud, defined by Cisco in 2012 and standardized as IEEE 1934-2018.
- [[just-enough-operating-system|Just enough operating system]] — Operating system philosophy that reduces the OS to the minimum components a specific application needs, shrinking attack surface, memory footprint, and maintenance.
- [[lightweight-linux-distribution|Lightweight linux distribution]] — Linux distribution engineered to use far less RAM and processor capacity than full-featured distributions, suited to constrained, embedded, and legacy hardware.
- [[virtual-appliance|Virtual appliance]] — Pre-configured virtual machine image combining a minimal operating system with a specific application, distributed as a self-contained unit for compatible hypervisors.
- [[security-through-obscurity|Security through obscurity]] — Reliance on secrecy of design or implementation as a primary security mechanism, rejected in professional practice since Kerckhoffs' principle of 1883.
- [[user-experience-design|User experience design]] — Multidisciplinary design practice covering every aspect of a user's interaction with a company and its products, coined by Donald Norman at Apple in the early 1990s.
- [[user-interface-design|User interface design]] — Discipline of designing human-machine interfaces to maximize usability and user experience, governed by the dialogue principles of the ISO 9241 standard.
<!-- END AUTO-GENERATED -->

## Editorial and publishing standards

<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: editorial-standards -->
@@ -68,6 +55,7 @@ terms are defined with their subject, not listed here.

## See also

- [Background](/category/background) — general computing concepts defined from first principles, for reading through rather than consulting
- [Architecture](/category/architecture) — where architectural terms are defined in context, not just listed
- [Core Concepts](/category/substrate) — the reusable mechanisms this wiki's vocabulary describes
- [Platform Tasks](/category/how-to) — procedural guides that assume this vocabulary
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 →