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.

os-console — the Command Ledger

← All revisions

7f641fc7 · PointSav Digital Systems ·

editorial(systems): fix os-console's F-key/cartridge-registration table + F12 fabrication (Track-B) — confirmed via os-console/main.rs's own chassis.register() calls: real registered set is People/Email/Content/Search/Slm/System/Input (7), NOT bookkeeper (2 static HTML files, no Cartridge trait, unregistered); app-console-gis doesn't exist as a crate at all; F5 belongs to the real app-console-search cartridge, not minutebook (also has no source); dropped fabricated F12 execution-permission-strip/Chart-of-Accounts-tagging claim, replaced with the just-verified real service-input SHA-dedup+coarse-label mechanism, cross-referenced to input-machine.md; register-clean EN+ES

View the full record as of this revision →

@@ -11,7 +11,7 @@ status: active
audience: vendor-public
bcsc_class: current-fact
language_protocol: PROSE-TOPIC
last_edited: 2026-07-31
last_edited: 2026-08-22
editor: pointsav-engineering
paired_with: os-console.es.md
aliases: [console-os, os-console-architecture, os-console-platform, topic-os-console-architecture]
@@ -31,7 +31,7 @@ short_description: "os-console is the human-facing surface of the PointSav platf

- `os-console` ships today as a `ratatui`/`crossterm` terminal application, not the seL4-isolated or GPU-native rendering pipeline described in its roadmap — those are planned, not current. Reserve "kernel-enforced" and similar claims for that future state.
- Cartridges are compiled directly into the binary — not loaded dynamically, not launched as subprocesses. `app-console-keys` (the chassis) and `app-console-input` (F12) are the only mandatory cartridges; everything else is optional.
- Per the platform's own project registry, 5 of 12 possible cartridges are `Active` today (bookkeeper, email, keys, slm, system); 3 are `Scaffold-coded` (content, input, people); the remaining 4 are `Reserved-folder` placeholders (bim, help, mesh, minutebook — vault is also reserved).
- `os-console`'s own startup code registers 7 cartridges today: people, email, content, search, slm, system, and input (F12, mandatory). Several other `app-console-*` directories exist on disk but have no working implementation behind them yet — see the F-key map below for which.
- Both modes (Direct and Aggregate) use the same binary; the aggregator does not require a different Console.
- All default service endpoints resolve to localhost addresses — the binary is operable without a configuration file and has no hard dependency on any external network.

@@ -75,31 +75,36 @@ Cartridges are registered at startup via `chassis.register(Box<dyn Cartridge>)`.

## The F-key map

The console presents twelve addressable slots via F-keys. F12 is fixed as The Anchor — the [[input-machine|Input Machine]] — and is never moved. F12 is mandatory per [[architecture-decisions|SYS-ADR-10]]: it 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 [[archetypes-and-chart-of-accounts|Chart of Accounts]], and are routed onward.
The console presents twelve addressable slots via F-keys. F12 is fixed as The Anchor — the [[input-machine|Input Machine]] — and is never moved. F12 is mandatory per [[architecture-decisions|SYS-ADR-10]]: it is the only surface through which raw external files can enter a Totebox. Files submitted through F12 are read once, deduplicated by content hash, tagged with a coarse routing label, and forwarded to `service-fs` — see [[input-machine|the Input Machine article]] for the exact mechanism.

| F-key | Cartridge | Domain | Crate state |
|---|---|---|---|
| F1 | `app-console-help` | Help overlay | Reserved-folder |
| F2 | `app-console-people` | Identity and contacts — [[service-people|service-people]] | Scaffold-coded |
| F3 | `app-console-email` | Communications — [[service-email|service-email]] | Active |
| F4 | `app-console-content` | Editorial — proofread, draft, verify — [[service-content|service-content]] | Scaffold-coded |
| F5 | `app-console-minutebook` | Governance — minutes, resolutions | Reserved-folder |
| F6 | `app-console-bookkeeper` | Financial ledger | Active |
| F7 | `app-console-bim` | Building information management | Reserved-folder |
| F8 | `app-console-gis` | Geographic information | Reserved-folder |
| F9 | `app-console-slm` | AI management and adapter marketplace — Doorman / `service-slm` | Active |
| F10 | `app-console-mesh` | Network mesh management | Reserved-folder |
| F11 | `app-console-system` | Live `os-*` service health and pairing status | Active |
| F12 | `app-console-input` | The Anchor — Input Machine (SYS-ADR-10) | Scaffold-coded |

Crate state is per the platform's own project registry, cross-checked against this article's own claims — earlier drafts of this content understated the active set (naming only 4 of the 5 currently `Active` cartridges). `app-console-vault` (not F-key-mapped) is also `Reserved-folder`.

### Active cartridges today
Seven cartridges are registered in `os-console`'s own startup code today; the rest are unclaimed slots with no working implementation behind them.

| F-key | Cartridge | Domain | State |
|---|---|---|---|
| F1 | — | Help overlay | Unclaimed — `app-console-help` has no source files |
| F2 | `app-console-people` | Identity and contacts — [[service-people|service-people]] | Registered |
| F3 | `app-console-email` | Communications — [[service-email|service-email]] | Registered |
| F4 | `app-console-content` | Editorial — proofread, draft, verify — [[service-content|service-content]] | Registered |
| F5 | `app-console-search` | Search | Registered |
| F6 | — | Financial ledger | Unclaimed — `app-console-bookkeeper` is two static HTML files, no `Cartridge` implementation, not registered |
| F7 | — | Building information management | Unclaimed — `app-console-bim` has no source files |
| F8 | — | Geographic information | Unclaimed — no crate of this name exists in the monorepo |
| F9 | `app-console-slm` | AI management and adapter marketplace — Doorman / `service-slm` | Registered |
| F10 | — | Network mesh management | Unclaimed — `app-console-mesh` has no source files |
| F11 | `app-console-system` | Live `os-*` service health and pairing status | Registered |
| F12 | `app-console-input` | The Anchor — Input Machine (SYS-ADR-10) | Registered |

State reflects the console's own startup registration calls, not the crate's presence on disk — a directory existing under `app-console-*` does not mean it is wired into the running console. `app-console-vault`, `app-console-exchange`, and `app-console-market` (not F-key-mapped) are also unclaimed; `app-console-minutebook`, once assumed to hold F5, has no source files either.

### Registered cartridges today

- **F2 — People (`app-console-people`).** Identity and contact lookups against `service-people`.
- **F3 — Email (`app-console-email`).** `EmailCartridge` connects to Exchange Web Services (EWS) via the `service-email` backend and presents three views: an inbox list (threaded message summaries with unread counts), a read view (full message body with attachment indicators), and compose/send (plain-text composition with `To:` and `Subject:` fields). Plain mode (no Kitty/Sixel) is supported for terminals that lack graphics protocol support.
- **F6 — Bookkeeper (`app-console-bookkeeper`).** HTML-plugin pattern (view + cartridge); activated 2026-04-22 as a framework pilot.
- **F4 — Content (`app-console-content`).** Editorial workflow against `service-content`.
- **F5 — Search (`app-console-search`).** Search across the connected Totebox's indexed content.
- **F9 — SLM (`app-console-slm`).** `SlmCartridge` renders a live health dashboard for the [[doorman-protocol|local inference gateway]], polling the gateway health endpoint every 10 seconds and displaying Tier A/B/C availability and circuit-breaker state, entity count from the local data store, and corpus queue depth with daily cost summary. The operator can force a manual refresh with `R`.
- **F11 — System (`app-console-system`).** `SystemCartridge` provides the operator panel for Totebox session management. Its primary function in the current phase is displaying pending-pair approvals — staging sessions awaiting Command Session sign-off before a commit is promoted.
- **F12 — Input (`app-console-input`).** The Anchor; see [[input-machine|Input Machine]] for the full ingest mechanism.

## Terminal capability negotiation

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 →