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

Revision as of · c13a438b

Historical revision — this record as it stood on 7 August 2026, not the current version. View the current record →

SystemsIndex

PointSav builds a family of purpose-built operating systems that share a common seL4 and Rust substrate. Each does one job, contains no features it does not need, and communicates through a common Diode-based protocol discipline. The result is a family that can be audited component by component, upgraded independently, and deployed in any configuration without unexpected coupling between systems.

Start here: OS family — eight operating systems, one substrate — the entry point for readers new to the family; it explains the common substrate, the Capability-based security model every OS inherits, the Diode standard that governs how they communicate, and the seL4 microkernel substrate that anchors them all.

The archive layer

The core record-keeping systems at the foundation of every deployment — where the canonical record lives and how it is coordinated across a fleet.

  • Sovereign vault and service host — The archive layer: one isolated, kernel-level vault per entity, storing records as inert flat files with no delete operation, exposed only through the Diode on command from os-console or os-orchestration.
  • Totebox orchestration — The coordination layer that manages multiple Totebox data-archive containers, keeping software execution engines isolated from passive corporate ledgers across deployments.
  • VM-* architecture and OS family — The five named VM types (Totebox, MediaKit, Orchestration, PrivateGit, Infrastructure) and how each maps exactly to one os-* source binary.
  • Scaling coordinated development across many Totebox Archives — The coordination bottlenecks that appear past twenty archives, and the path toward per-archive process isolation.
  • os-totebox: the sovereign WORM data vault — os-totebox's intended end-state design as a Type I bare-metal seL4 OS: the WORM data vault enforced by a compiled capability graph rather than a policy an administrator could override.
  • How service-* Become seL4 Protection Domains on os-totebox — How os-totebox is designed to map its Rust service binaries onto seven seL4 Protection Domains, with capability confinement guaranteeing a compromised service-slm PD can never reach the storage-holding service-fs PD.

Operator surfaces

The systems through which a human operator interacts with the platform — keyboard-driven, F-key-structured, and built around muscle memory rather than discoverability.

  • os-console — the Command Ledger — The human-facing surface: a Command Ledger and single Rust binary that connects to a Totebox and renders its state through a keyboard-driven, cartridge-based, F-key-structured interface.
  • os-console: The Totebox Orchestration Browser — The browser-analogy explainer for os-console's design philosophy: cartridges as tabs, machine pairing as the certificate store.
  • Input machine — The mandatory document ingest gate in os-console, bound permanently to F12 and backed by service-input on the Totebox Archive.
  • Sovereign desktop — The free desktop operating system: a native-Rust sovereign desktop that pairs with a Totebox archive and serves as the adoption gateway to the commercial product line.
  • Fleet aggregator — The Fleet Aggregator for multi-entity portfolios: one operator sees, queries, and commands many Totebox archives at once.

Network control and infrastructure

The systems that manage the network fabric, the bootstrap path, and the underlying compute substrate.

  • OS network admin — The control plane for a fleet: manages the pairing registry, Diode rules, and mesh routing policy; commands broadcast as 16-byte binary packets across the WireGuard mesh.
  • Private git OS — Private Git hosting for sovereign version control within a fleet.
  • Browser workbench — The browser-based file editor included in os-privategit: a three-column interface for working with archive files without a terminal session.
  • os-infrastructure — PPN node operating system — The OS layer for PPN nodes: managing WireGuard tunnels, hosting guest VMs for other platform services, and running the Genesis Protocol node-join ceremony.

Publishing and media

The public-facing OS that hosts the company's marketing surface, internal wiki, and compliance newsroom on a single sovereign appliance.

  • OS mediakit — The guest OS image for the vm-mediakit tier, isolating knowledge wikis, marketing sites, the proofreader, and BIM orchestration from the vault and orchestration tiers. Ubuntu 24.04 today; a seL4 Microkit image is the planned long-term form.

See also

  • Architecture — cross-cutting platform architecture and the three-ring model
  • Services — the autonomous services that run within and across operating systems
  • Infrastructure — fleet deployment topology and cloud operational runtime
  • Substrate — the substrate disciplines and microkernel primitives the OS family inherits
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 →