Skip to content
Historical revision — this record as it stood on 15 May 2026, not the current version. View the current record →

os-console — The Command Ledger

os-console is the human-facing surface of the PointSav platform — a Command Ledger that connects to one Totebox and renders its state to the operator. It does not store data and does not run services; it is a high-fidelity terminal purpose-built around keyboard-driven operator flow. The reference point is the Bloomberg Terminal: a single keyboard, a small set of function keys, and a relentless focus on the operator's context. The binary is written from scratch in Rust for sub-50-millisecond cold start and a 15-megabyte footprint. This article covers how os-console runs, the F-key surface, the rendering stack, and the two operating modes.

How it runs

os-console ships as a single executable. On the host operating system — Windows, macOS, or Linux — it acts as a Virtual Machine Monitor: it uses the host's native virtualisation API to create a small, isolated VM in RAM and boots an seL4 environment inside it.

Host Native VMM API
Windows Windows Hypervisor Platform (WHPX)
macOS Hypervisor.framework
Linux KVM

The operator thinks they opened an application. What they have done is spun up a hardware-isolated secure environment in roughly 50 milliseconds. When the application closes, the secure memory is wiped. Nothing touches the host hard drive.

The F-key surface

The interface organises every entity's reality into a fixed set of pillars. Each pillar is a function key:

Key Pillar Service
F1 HELP [content-wiki-documentation](/wiki/app-console-input) (read-only operating procedures)
F2 PEOPLE [service-people](/wiki/service-people) — the identity ledger
F3 EMAIL [service-email](/wiki/service-email) — the Comm Diode
F4 CONTENT [service-content](/wiki/service-content) — the drafting and synthesis engine
F5 MINUTEBOOK [service-minutebook](/wiki/service-minutebook) — deep records
F6 BOOKKEEPER [service-bookkeeper](/wiki/service-bookkeeper) — the financial ledger
F12 INPUT MACHINE app-console-input — the human-in-the-loop ingestion gateway

F12 is mandatory per sys-adr-10. The Input Machine is the only surface through which raw external files can enter a Totebox. Files dropped into F12 have execution permissions stripped, are tagged against the operator's Chart of Accounts, and are routed to F5 or F6.

The rendering stack

os-console is not a TUI inside a host terminal. It is a standalone graphics application that happens to display text. The stack is owned end-to-end:

Layer Component Notes
Window pointsav-window Custom Win32 / Cocoa / X11/Wayland wrapper
GPU pointsav-gpu WGPU (Vulkan / Metal / DX12 abstraction); licence embedded in binary
Text pointsav-text Signed Distance Field (SDF) glyph renderer 1; infinite-zoom fidelity
Layout pointsav-layout Recursive row/column grid in roughly 500 lines of Rust
Widget logic Forked from ratatui core Logic only; ratatui's renderer replaced by the WGPU pipeline

The result is a terminal interface with variable-weight headers, bloom effects, and smooth scrolling — while remaining purely keyboard-driven and rendering at the fidelity required by ISO 19650 2 document-state suffixes.

Direct mode and aggregate mode

os-console operates in two modes determined by what it pairs with:

Mode Pair Use case
Direct One [Totebox](/wiki/totebox-os) A single entity's deep view; the default for individual operators
Aggregate One [os-orchestration](/wiki/os-orchestration) (which aggregates many Toteboxes) A portfolio view for executives and commercial-tier deployments

Both modes use the same os-console binary. The aggregator does not require a different Console. The complexity lives in os-orchestration.

Single, unified, universal

os-console is one product. There is no "Home" edition and no "Pro" edition. An individual hosting one Totebox uses the same Command Ledger as the administrator of a Reporting Issuer aggregating hundreds. Commercial differentiation is determined by the presence or absence of os-orchestration, never by a tiered Console.

See also

  • totebox-os — the Totebox archive that os-console connects to and renders
  • app-console-input — the F12 Input Machine; deep coverage of the mandatory ingestion gateway
  • diode-standard — why commands flow in one direction through the established pair
  • os-family-overview — the five OS surfaces and how os-console fits among them
  • deployment-patterns — how os-console appears in each of the six canonical deployment configurations
  1. Green, C. 'Improved Alpha-Tested Magnification for Vector Textures and Special Effects.' ACM SIGGRAPH 2007 courses, 2007. https://dl.acm.org/doi/10.1145/1281500.1281665

  2. ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). https://www.iso.org/standard/68078.html

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). 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. See TRADEMARK.md in this repository for the full trademark notice.

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 →