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 Three-Path seL4 Architecture

← All revisions

a1c7d582 · PointSav Digital Systems ·

editorial(infrastructure): fix ppn-three-path-architecture Option B status overclaim (Track-B) — real os-infrastructure boot code has zero seL4 integration (bare Multiboot2 stub); real seL4 progress is moonshot-sel4-vmm's separate unikernel runtime (Phases H1-H8 complete), not yet wired into the PPN node boot path; rehedged 'Active'/'Current path' to development-priority framing; EN+ES

View the full record as of this revision →

@@ -24,9 +24,9 @@ The PointSav Private Network node stack is designed around the seL4 microkernel.

## Option B — seL4 hypervisor with Linux guest

**Current path.**
**Current development priority — not yet the operating PPN node OS.** The real `os-infrastructure` boot code that would run on a PPN node today has no seL4 integration at all: it is a bare-metal Multiboot2 stub (framebuffer text output, an mDNS peer scan), and all PPN services — WireGuard, fleet management, inference routing — currently run on conventional Linux, not inside a seL4-hosted guest. Real, substantial seL4 engineering exists (a separate unikernel/protection-domain runtime, `moonshot-sel4-vmm`, with console/IPC/serial/UART/panel/network protection domains proven working, including a real HTTP request over VirtIO-net DMA), but it is not yet wired into `os-infrastructure`'s own boot path. The design below is the target this development work is building toward.

seL4 runs as a Type 1 hypervisor at EL2 (AArch64) or with VT-x (x86-64). The CAmkES VMM runs as a seL4 protection domain and hosts one Linux (Debian 12) guest VM. All PPN services — WireGuard, fleet management, inference routing — run inside the Linux guest.
Once built: seL4 would run as a Type 1 hypervisor at EL2 (AArch64) or with VT-x (x86-64). The CAmkES VMM would run as a seL4 protection domain and host one Linux (Debian 12) guest VM. All PPN services — WireGuard, fleet management, inference routing — would run inside that Linux guest.

```
Hardware
@@ -108,7 +108,7 @@ x86-64 support was added in Microkit 2.1.0. This architecture is a valid develop

| Option | seL4 as | Linux | Trusted computing base | Verification | Status |
|---|---|---|---|---|---|
| B (current) | Hypervisor | Guest VM | seL4 + VMM + Linux | AArch64 integrity | Active |
| B (current priority) | Hypervisor | Guest VM | seL4 + VMM + Linux | AArch64 integrity | Development priority; not yet integrated into `os-infrastructure`'s boot path |
| C (planned) | Hypervisor + WireGuard PD | Guest VM (limited) | seL4 + VMM + WireGuard PD + Linux | AArch64 integrity | Planned/intended |
| A (planned) | OS (all components) | None | seL4 only | AArch64 all CIA (in progress) | Planned/intended |
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 →