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

seL4 capability topology

← All revisions

b19ba68d · PointSav Digital Systems ·

Correction: security/sel4-capability-topology.md PPN paragraph tense-corrected — no seL4 dependency in real PPN VM crates (EN+ES)

View the full record as of this revision →

@@ -10,7 +10,7 @@ status: active
audience: vendor-public
bcsc_class: public-disclosure-safe
language_protocol: PROSE-TOPIC
last_edited: 2026-06-29
last_edited: 2026-07-30
editor: pointsav-engineering
paired_with: sel4-capability-topology.es.md
short_description: "In an seL4 system, security is the shape of the capability graph: if component A has no path to B, A cannot reach B by any means, proved by formal verification."
@@ -65,9 +65,24 @@ Google's Fuchsia OS uses the same capability model and the same vocabulary. Fuch

## PPN application

The PointSav Private Network is planned/intended to use seL4 as the hypervisor layer on AArch64 nodes. In that configuration, the seL4 capability topology governs what components can communicate across the mesh. The WireGuard mesh interface, the pairing ceremony server, and the fleet management service each occupy distinct seL4 protection domains with explicitly granted capability channels. A component without a capability to the WireGuard protection domain cannot modify peer tables — regardless of whether it is compromised.

This is the formal basis for the PPN security model at the hypervisor layer.
The PointSav Private Network is planned/intended to use seL4 as the hypervisor layer on AArch64 nodes. In that configuration, the seL4 capability topology would govern what components can communicate across the mesh.

**Scoped correction (2026-07-30):** the paragraph originally here stated, in present
tense, that "the WireGuard mesh interface, the pairing ceremony server, and the fleet
management service each occupy distinct seL4 protection domains" — inconsistent with
this section's own opening hedge ("planned/intended"). Verified against the real PPN
VM crates: `service-vm-fleet`, `service-vm-host`, and `service-vm-tenant` (the actual
fleet/host/tenant services running today, per `.agent/rules/project-registry.md`) carry
zero seL4 dependency anywhere in source — plain Rust/`axum` services, not seL4
protection domains. `moonshot-hypervisor` (the crate that would host any real seL4
hypervisor layer) has an empty `Cargo.toml` dependency list. Rephrased to the
conditional to match the section's own stated hedge, rather than describing a
protection-domain assignment that does not exist in the running system today. This is
a scoped, single-paragraph fix — the rest of this article (seL4's own external,
published formal-verification properties) is unaffected and was not re-verified beyond
this paragraph.

This would be the formal basis for the PPN security model at the hypervisor layer, once that layer is built.

## See also
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 →