Systems
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.
os-family-overview is the entry point for readers new to the family — it explains the common substrate, the capability-based-security model that every OS inherits, the diode-standard that governs how they communicate, and the sel4-microkernel-substrate that anchors them all to a mathematically formally verified L1 kernel.
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.
- totebox-os — 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-archive — A self-contained, freely transferable micro-virtual machine that persists institutional data as immutable flat files.
- totebox-orchestration — The coordination layer that manages multiple Totebox data-archive containers, keeping software execution engines isolated from passive corporate ledgers across deployments.
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.
- console-os — The human-facing surface: a Command Ledger that connects to a Totebox and renders its state through a keyboard-driven, F-key-structured interface.
- os-console-platform — The Rust binary that implements os-console: cartridge architecture, F-key-navigated modules, keyboard-native access to Totebox Archive workflows.
- input-machine — The mandatory document ingest gate in os-console, bound permanently to F12 and backed by
service-inputon the Totebox Archive. - os-workplace — 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.
- os-orchestration — 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.
- infrastructure-os — The compute substrate that hosts PointSav operating systems across on-premises, leased, and cloud hardware; bootstraps isolated fleets through the Genesis Protocol.
- 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.
- os-privategit — Private Git hosting for sovereign version control within a fleet.
- os-privategit-workbench — The browser-based file editor included in os-privategit: a three-column interface for working with archive files without a terminal session.
Publishing and media
The public-facing OS that hosts the company's marketing surface, internal wiki, and compliance newsroom on a single sovereign appliance.
- mediakit-os — The public-facing OS: hosts a company's marketing website, internal wiki, and compliance newsroom on a single sovereign appliance the company owns outright.
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
All 18 articles in this area, A–Z
- systems/console-os
- Compute substrate2026-05-15
os-infrastructure is the compute substrate that hosts PointSav operating systems across on-premises, leased, and cloud hardware. It creates the PointSav Private Network and bootstraps isolated fleets through the Genesis Protocol.
- The Input Machine2026-05-25
The Input Machine is the mandatory document ingest gate in os-console, bound permanently to F12 and backed by service-input on the Totebox Archive.
- Sovereign compliance appliance2026-05-25
os-mediakit is the public-facing operating system in the PointSav family, hosting a company's marketing website, internal wiki, and compliance newsroom on a single sovereign appliance the company owns outright.
- os-console platform and cartridge architecture2026-05-25
os-console is a single Rust binary with a cartridge architecture that provides keyboard-native access to Totebox Archive workflows through F-key-navigated modules.
- The OS family — eight operating systems, one substrate2026-05-15
PointSav builds eight purpose-built operating systems that share a common seL4 + Rust substrate. Each does one job, contains no features it does not need, and communicates through a common Diode-based protocol discipline.
- os-infrastructure — PPN Node Operating System2026-05-30
os-infrastructure is the operating system layer for PointSav Private Network nodes — its sole purpose is to set up, operate, and maintain a PPN node: managing WireGuard tunnels, hosting guest virtual machines, and exposing the operator control plane.
- OS Mediakit2026-05-29
- OS Network Admin2026-05-30
os-network-admin is the control plane for a PointSav Private Network — providing WireGuard mesh routing, the node-join ceremony surface, and Diode-standard enforcement, without holding any archive-tier cryptographic authority.
- Fleet aggregator2026-05-15
os-orchestration is the commercial-tier operating system that lets a single operator see, query, and command many Totebox archives at once — the Fleet Aggregator for multi-entity portfolios and enterprise deployments.
- Private Git OS2026-05-25
The operating system layer hosting the private Git infrastructure that underpins the development workspace, staging-tier commit flow, and canonical source repositories for all PointSav engineering repos.
- os-privategit browser workbench2026-05-25
app-privategit-workbench is a browser-based file editor included in os-privategit that provides a three-column interface for working with archive files without a terminal session.
- ToteboxOS2026-06-02
os-totebox is the sovereign vault and service host in the PointSav OS family — the operating system that runs on a Totebox archive node and manages an entity's data, services, and identity.
- systems/os-workplace
- Totebox Archive2026-05-30
A Totebox Archive is a sovereign data vault assigned to a single entity — packaged as a freely transferable bootable disk image, storing data as WORM flat files, and accepting queries only via the Diode Standard and PointSav Protocol.
- Totebox orchestration2026-05-25
Totebox Orchestration describes the coordination layer that manages multiple Totebox data-archive containers, keeping software execution engines isolated from passive corporate ledgers across deployments.
- systems/totebox-os
- VM-* Architecture and OS Family2026-05-30
The PointSav platform organises its runtime deployments under five named VM types — VM-Totebox, VM-MediaKit, VM-Orchestration, VM-PrivateGit, and VM-Infrastructure — each corresponding exactly to one os-* source binary.