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

VM-* architecture and OS family

← All revisions

3f571a87 · PointSav Digital Systems ·

fix(applications,systems,patterns): correct app-orchestration-command misattribution, retire 2 redundant articles

View the full record as of this revision →

@@ -6,6 +6,7 @@ short_description: "The PointSav platform organises runtime deployments under fi
category: systems
type: topic
content_type: topic
index_group: the-archive-layer
status: active
bcsc_class: public-disclosure-safe
language: en
@@ -18,7 +19,7 @@ The PointSav platform organises its runtime deployments under a set of named VM 

This correspondence is not incidental. The platform is designed to be deployed the same way by a builder running a development environment as by a customer running a production system. The five VM types map directly to the five ways customers and community members engage with the platform.

**Correction (2026-08-02, revised):** several specific claims below don't match the real codebase. (1) `os-orchestration` (VM-Orchestration's named source binary) is a real crate on canonical but currently an empty placeholder scaffold (retracted from an earlier "not built" claim — see [[app-orchestration-command-branch-model]]); its "PointSav Protocol (PSP)" aggregation mechanism remains confirmed fabricated, zero code footprint even on canonical. (2) `service-proofreader` is not a real crate name — the real proofreader implementation is `app-console-content/src/proofreader.rs`, described in its own `Cargo.toml` as "os-console F4 Content Cartridge," which undercuts this article's own placement argument that its callers are MediaKit-resident: its real caller is `os-console`. (3) `app-privategit-design-system` is misnamed — the real crate is `app-privategit-design` (no "-system" suffix). (4) The genesis-node roles below are inverted relative to the real provisioning scripts: `infrastructure/virt/provision-vm-infrastructure-cloud.sh` states outright that "GCP is the canonical genesis-seed for the internet-facing hub" (not Laptop A), and `provision-vm-infrastructure-onprem.sh` shows Laptop A peers with the GCP hub via `--genesis` while Laptop B uses a distinct `--genesis-hub` flag for the on-prem LAN — not the plain `--join <short-code>` this article assigns it. **Flagged, not resolved** — needs correcting the binary/crate names and the genesis-role sequence; the Phase 2/3 Microkit/NVMM roadmap section is already correctly hedged as "intended" and needs no change.
**Correction (2026-08-02, revised):** several specific claims below don't match the real codebase. (1) `os-orchestration` (VM-Orchestration's named source binary) is a real crate on canonical but currently an empty placeholder scaffold (retracted from an earlier "not built" claim — the related `app-orchestration-command` crate is real and substantial, see [[personnel-permissions]]); its "PointSav Protocol (PSP)" aggregation mechanism remains confirmed fabricated, zero code footprint even on canonical. (2) `service-proofreader` is not a real crate name — the real proofreader implementation is `app-console-content/src/proofreader.rs`, described in its own `Cargo.toml` as "os-console F4 Content Cartridge," which undercuts this article's own placement argument that its callers are MediaKit-resident: its real caller is `os-console`. (3) `app-privategit-design-system` is misnamed — the real crate is `app-privategit-design` (no "-system" suffix). (4) The genesis-node roles below are inverted relative to the real provisioning scripts: `infrastructure/virt/provision-vm-infrastructure-cloud.sh` states outright that "GCP is the canonical genesis-seed for the internet-facing hub" (not Laptop A), and `provision-vm-infrastructure-onprem.sh` shows Laptop A peers with the GCP hub via `--genesis` while Laptop B uses a distinct `--genesis-hub` flag for the on-prem LAN — not the plain `--join <short-code>` this article assigns it. **Flagged, not resolved** — needs correcting the binary/crate names and the genesis-role sequence; the Phase 2/3 Microkit/NVMM roadmap section is already correctly hedged as "intended" and needs no change.

## VM types and their purposes
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 →