Sovereign desktop
os-workplace is planned as the free desktop tier in the PointSav family. What exists today is a
family of independent Rust and Tauri desktop applications — the workplace apps — that an operator
downloads and runs directly on their own computer. The os-workplace crate that would bind them
into one unified, branded environment is still a one-line placeholder, not built infrastructure.
The strategy behind the free tier is deliberate: an operator installs the workplace apps because
they are fast and cost nothing; once daily work happens inside the PointSav ecosystem, the
commercial os-orchestration aggregator becomes a logical next step. This
article covers the real applications that exist today, the ratified plan for how a workplace
machine joins the network, and the strategic rationale for a free desktop tier.
The workplace apps
The apps are Tauri desktop applications — a Rust backend paired with an HTML/JS/CSS WebView,
targeting macOS 10.13 High Sierra and later. Two of the nine crates below are pure Rust with no
WebView. Each app is independent: an operator can install one without the others, and none
require the unified os-workplace shell to run.
| App | State | What it does |
|---|---|---|
app-workplace-memo |
Active | Document editor; produces a self-contained .html file with fonts embedded, printing to a flawless PDF via the OS print dialogue 1 |
app-workplace-presentation |
Active | Slide editor, built on the same offline-first, no-cloud design as Memo |
app-workplace-workbench |
Active | A thin WebView window onto the locally running app-privategit-workbench HTTP server; it does not itself start, stop, or manage that server |
app-workplace-proforma |
Active | Spreadsheet for institutional financial analysis; produces a self-contained .json file carrying formulas, formatting, and an audit chain |
app-workplace-pdf |
Scaffold-coded | PDF viewer and print tool using the pdfium-render crate (Google PDFium, Apache-2.0) |
app-workplace-gis |
Scaffold-coded | Desktop viewer for location-intelligence data; loads a MapLibre GL tile viewer against gis.woodfinegroup.com or a local tile server over the PPN |
app-workplace-bim |
Reserved-folder | Planned BIM authoring editor (Revit/AutoCAD muscle memory); a research document only today — no Cargo.toml or source exists yet |
app-workplace-aibridge |
Built, not yet registry-tracked | The AI section-edit bridge core — lets an operator hand one section of a document to an external AI session and apply only that section's result; enforces SYS-ADR-07 by refusing structured schemas (proforma, GIS, BIM data) at every entry point |
app-workplace-http-prototype |
Built, not yet registry-tracked | An axum server exposing the workplace apps over the WireGuard PPN while native Tauri builds await a macOS build host; the Memo editor is the only surface it currently serves, the rest are listed pending |
Deployment: joining the network
Ratified 2026-05-23 (DOCTRINE.md §IV.f); implementation pending. os-workplace runs on the
operator's own personal computer — today, a MacBook — and is planned to deliver
app-workplace-desktop, the unified operator desktop surface that would bind the apps above into
one environment. It hosts os-console as a co-resident application, not through
Type 2 virtualization — the two are independent layers sharing the same machine. The machine joins
the PointSav Private Network as a direct WireGuard peer in the
10.42.20.0/24 range; the node-* instance of os-console it hosts inherits that membership
rather than getting a separate address. Deployment instances use the station-* prefix. The first
two planned are station-workplace-jennifer-1 and station-workplace-mathew-1, both awaiting the
WireGuard network rollout and the app-workplace-desktop build. os-workplace does not connect
to the orchestration gateway directly — only indirectly, through the
os-console instance it hosts.
Pairing with the Totebox
os-workplace is the operator's local environment. Data lives in the operator's
os-totebox. Machine-based pairing establishes hardware-bound trust between the
workstation and the archive — see Machine-based authorization for the mechanism. There are no
usernames or passwords; the pairing is the permission.
Why a free desktop is strategic
Three reasons make os-workplace a structural commitment rather than a marketing gesture:
- Adoption funnel. A free, fast set of desktop apps is intended to introduce the operator to
the F-key discipline of
os-consoleand the security model of the Diode, so the commercial products feel familiar from day one. - Reference implementation. Every line of code written for the workplace apps is reviewable in the public monorepo. Customers can audit the substrate before they buy commercial aggregation against it.
- Ecosystem gravity. A growing community of workplace-app users is intended to create an independent constituency of contributors, packagers, and translators that no commercial-only product can replicate. The contributor model describes the roles and rights for community participation.
See also
- OS family — eight operating systems, one substrate — the eight-OS family and where os-workplace fits
- Sovereign vault and service host — the data partner; the archive os-workplace pairs with
- console-os — the co-resident TUI-first surface that carries os-workplace's network connection
- Machine-based authorization — the pairing model that replaces usernames and passwords
- PPN architecture overview — the WireGuard network that station-* deployments join
-
ISO 19005-1:2005 — Document management — Electronic document file format for long-term preservation — Part 1: Use of PDF 1.4 (PDF/A-1). https://www.iso.org/standard/38920.html ↩