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

Last updated · 9b9339a2 · Español

Use the F-key cartridge model

Prerequisites

Purpose

Understand what each default cartridge actually does before you rely on one for real work — a few minutes, and it corrects two real fabrications that were in this guide previously: F9 is not a chat interface, and F12 does not have a reject/quarantine outcome.

Procedure

  1. Recognize that a Cartridge is compiled directly into the os-console binary — not a plugin, not a subprocess. Pressing its F-key hands control to that registered module, which owns its own rendering and keyboard handling until you switch away.

  2. Use the Email Cartridge at F3: press F3, read the inbox list (unread counts and sender summaries), navigate with arrow keys, press Enter to open a message, and c to compose. Outbound mail routes through service-email, not a direct SMTP connection.

  3. Use the SLM Cartridge at F9 for what it actually is: a live monitoring dashboard, not a query tool. Press F9 and read its five sections — Gateway, YoYo Fleet, DataGraph, Queue, and Cost Today. Press R to force an immediate refresh instead of waiting for the next poll.

    Note: F9 has no prompt input of any kind — no text field, no submit key, no streaming response. If you're looking for how to actually run an inference query, see Run your first SLM query, which covers the real path.

  4. Use the Input Machine at F12 for what it actually does: it's the platform's mandatory file-ingestion checkpoint, not a record-review-and-approve screen. Files entering through F12 have execution permissions stripped and are tagged before being routed onward — this is the only path raw external files can enter a Totebox.

    Warning: a submission through F12 either succeeds (shown as Done, with a payload ID and ledger position — occasionally with a non-fatal warning attached) or fails with a generic error. There is no separate "reject and quarantine" outcome in this flow — a rejected submission simply shows as an error, not a distinct quarantine state.

Expected outcome

You know which cartridge does what without guessing: F3 for mail, F9 for read-only inference-gateway health, F12 for the mandatory file-ingestion checkpoint — and you know F9 is not where you submit a query.

Verification

Open each of F3, F9, and F12 in turn and confirm what you see matches this guide: an inbox at F3, a five-section health dashboard with no input field at F9, and a file-ingestion interface at F12.

Rollback

Viewing F3 or F9 changes nothing. A real F12 submission is not reversible — see Explore the console for the first time for that caution in more detail before you submit anything through it.

Next steps

See also

Cite this record: /wiki/use-f-key-model — revision 9b9339a2, last updated 6 August 2026.

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 →