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

PPN distributed VM fabric

← All revisions

e0a49aba · PointSav Digital Systems ·

editorial(infrastructure): rehedge ppn-distributed-vm-fabric — per-node layer not built either (Track-B) — re-verified: neither per-node (virtio_balloon/cgroups) nor any of the 4 distributed components has code; fixed 'Complete' table status to Planned, dropped internal script-filename citation per register-documentation.yaml; EN+ES

View the full record as of this revision →

@@ -17,13 +17,13 @@ editor: editorial

The **PPN Distributed VM Fabric** is the planned extension of the per-node PPN hypervisor layer to a multi-node resource pool. Where the current hypervisor layer manages CPU and RAM within a single physical node, the distributed fabric is intended to allow VMs to borrow compute from other nodes in the mesh and to place and migrate VMs across the fleet without per-move operator involvement.

This topic describes the planned architecture. The per-node layer — `virtio_balloon`, cgroups v2 weights, and the `vm-prove.sh` proof — is implemented and proven as of 2026-05-28. The four distributed components described below are planned milestones; none is built yet. (Correction, 2026-08-02, verified against canonical `origin/main`: this "implemented and proven" claim is itself wrong — no `virtio_balloon` or cgroups/`cpu.weight` code exists anywhere in `os-infrastructure` or `service-vm-fleet`, on either branch. `vm-prove.sh` is confirmed real, but it's a standalone manual QEMU-monitor demo script, not an integrated hypervisor mechanism — it doesn't prove what this article claims it proves. Flagged, not resolved — the "Complete" status in the table below and the linked [[ppn-hypervisor-resource-pool]] article need the same correction.)
This topic describes the planned architecture. Neither the per-node layer nor the four distributed components below is built yet. `virtio_balloon` and cgroups v2 weights have no code anywhere in `os-infrastructure` or `service-vm-fleet` — a real, standalone demo script exercises the underlying QEMU balloon mechanism manually via the QEMU monitor, but it is not an integrated hypervisor mechanism and does not by itself demonstrate that the per-node layer is built.

## Current state: per-node only
## Current state: neither layer is built

The implemented hypervisor layer allocates CPU and RAM within one physical node. The pool is bounded by that node's hardware. Expanding a VM's memory means taking from the same node's free pool. Placing a VM on a different node requires stopping it, transferring the disk image, and restarting — a manual operation the Totebox Orchestration layer is intended to automate.
The intended per-node layer would allocate CPU and RAM within one physical node. The pool would be bounded by that node's hardware; expanding a VM's memory would mean taking from the same node's free pool. Placing a VM on a different node today requires stopping it, transferring the disk image, and restarting by hand — a manual operation the Totebox Orchestration layer is intended to automate eventually.

The `virtio_balloon` mechanism proven in `infrastructure/virt/vm-prove.sh` operates entirely within a single node. No network communication is involved. No reboot of host or guest is required for balloon operations — inflation, deflation, and cgroups v2 weight changes are all dynamic adjustments to a running system.
The `virtio_balloon` mechanism the demo script exercises operates entirely within a single node and requires no network communication — a property that would carry over once the mechanism is integrated. No reboot of host or guest would be required for balloon operations: inflation, deflation, and cgroups v2 weight changes are all designed as dynamic adjustments to a running system.

## Component 1 — Virtio-mem lending over WireGuard (planned)

@@ -92,7 +92,7 @@ The per-node layer is the foundation. The distributed fabric is intended to buil

| Step | State | Reserved directory |
|---|---|---|
| Per-node virtio_balloon + cgroups v2 | **Complete** — proven 2026-05-28 | `os-infrastructure/` |
| Per-node virtio_balloon + cgroups v2 | Planned — not started; only the underlying QEMU mechanism has a manual demo | `os-infrastructure/` |
| Ceremony deployment (`service-ppn-pairing` on GCP VM) | Pending | `service-ppn-pairing/` |
| First real node join (`os-network-admin` on Laptop A) | Pending | `os-network-admin/` |
| Genesis Protocol `os-infrastructure` rewrite | Planned | `os-infrastructure/`, `moonshot-hypervisor/` |
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 →