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

40b0c4ab · PointSav Digital Systems ·

feat(track-b): sample Glossary and Reference Index Topic — supersedes stale legacy MOC page (had only 10 of 23 real articles), 3 thematic groups (platform orientation, general computing concepts, editorial and publishing standards) covering all 23, Start Here on glossary-documentation, EN+ES, index_group tags on all 23 articles, 0 lint errors

View the full record as of this revision →

@@ -1,49 +1,83 @@
---
schema: foundry-doc-v1
title: "Reference"
slug: _index
title: "Glossary and Reference"
slug: reference-index
category: reference
type: reference
type: topic
content_type: topic
index_type: thematic
index_scope: reference
quality: complete
short_description: "Definitional materials for contributors across all audiences: style guides for each document genre, editorial philosophy, BIM and real-property reference corpus, glossary, and platform-specific terminology."
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."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-05-15
last_edited: 2026-08-04
editor: pointsav-engineering
paired_with: _index.es.md
---

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.
**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.

## Editorial philosophy and standards
**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.

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.
<!-- 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. -->

- [[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-standards]] — Standards for news releases and BCSC-compliant continuous-disclosure communications.
- [[preprint-notice-convention]] — What the mandatory preprint notice on every JOURNAL research paper means: a working draft, not yet peer-reviewed, subject to revision.
**Start here:** [PointSav encyclopedia — glossary and lexicon](/wiki/glossary-documentation) — the canonical A-to-Z definition of every platform-specific term, the page most other articles link to on first use.

## BIM and real-property reference
<!-- END-START-HERE-HIGHLIGHT -->

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

BIM and real-property reference articles (AEC muscle memory, BIM design philosophy, BIM market context, BIM token taxonomy, the BIM token three-layer model, what a BIM token is, and open-BIM regulatory acceptance) now live on the projects wiki at projects.woodfinegroup.com/building-design.
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: platform-orientation -->
- [Getting started with the PointSav platform](/wiki/getting-started) — what the platform is, who it's for, and where to go first
- [PointSav encyclopedia — glossary and lexicon](/wiki/glossary-documentation) — the canonical term-by-term definition source
- [How this knowledge base is organized](/wiki/wiki-structure) — a reader's map of all thirteen documentation-wiki areas
- [Developer guide index](/wiki/guide-catalog) — every how-to guide, grouped by developer concern
- [Hardware reference](/wiki/hardware-reference) — reference hardware profiles for workstations and fleet devices
- [SLM operationalization plan](/wiki/service-slm-operationalization-plan) — the plan for moving from external model calls to a per-tenant local model
<!-- END AUTO-GENERATED -->

## Glossary and terminology
## General computing concepts

- [[glossary-documentation]] — The master glossary of PointSav platform terms: canonical definitions, disambiguation notes, and cross-references.
- [[hardware-reference]] — Hardware specifications and reference configurations for PointSav deployments.
- [[root-files-discipline]] — The canonical set of files permitted at a repository root and how misplaced files are handled.
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: computing-concepts -->
- [Application programming interface](/wiki/application-programming-interface) — how software systems communicate through a defined set of calls
- [Computer appliance](/wiki/computer-appliance) — hardware and software sealed together for one well-defined function
- [Edge computing](/wiki/edge-computing) — placing computation near the data it operates on, rather than in a central data center
- [Fog computing](/wiki/fog-computing) — the layer of compute and storage between edge devices and the cloud
- [Just enough operating system](/wiki/just-enough-operating-system) — reducing the OS to only what a specific application needs
- [Lightweight linux distribution](/wiki/lightweight-linux-distribution) — Linux builds engineered for far less RAM and CPU than a full distribution
- [Virtual appliance](/wiki/virtual-appliance) — a pre-configured VM image combining a minimal OS with one application
- [Security through obscurity](/wiki/security-through-obscurity) — why secrecy of design is not treated as a security mechanism here
- [User experience design](/wiki/user-experience-design) — the discipline covering every aspect of a user's interaction with a product
- [User interface design](/wiki/user-interface-design) — designing the human-machine interface itself, governed by ISO 9241
<!-- END AUTO-GENERATED -->

## Operational reference
## Editorial and publishing standards

- [[service-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.
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: editorial-standards -->
- [Editorial language registers](/wiki/editorial-language-registers) — the three prose registers this wiki writes in, matched to audience
- [Editorial philosophy](/wiki/editorial-philosophy) — why every article teaches understanding rather than just retrieving facts
- [News release typography and layout standards](/wiki/news-release-standards) — formatting rules for corporate news syndication
- [Preprint notice](/wiki/preprint-notice-convention) — what the mandatory notice on a working research paper actually means
- [Root files discipline](/wiki/root-files-discipline) — the canonical, enumerated set of files every repository root keeps
- [Structural positioning](/wiki/structural-positioning) — how this platform differentiates without naming competitors
- [Wiki provider landscape](/wiki/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.

## See also

- [Governance](/governance/) — formal decision records and compliance posture
- [Design System](/design-system/) — visual and component design reference
- [How It's Built](/category/architecture) — where architectural terms are defined in context, not just listed
- [Building Blocks](/category/substrate) — the reusable mechanisms this wiki's vocabulary describes
- [How You Run It](/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 →