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

Explore the console for the first time

Prerequisites

  • A paired device (see Pair a new device)
  • The os-console binary available in your PATH, or built locally from os-console/
  • A terminal emulator — 24-bit color and the Kitty or Sixel graphics protocol are used when available and improve the display, but the console degrades gracefully to named colors and text-only rendering without them

Purpose

Get oriented to os-console for the first time: the status bar's live situational picture, the F9 inference-gateway health dashboard, and the F12 input checkpoint every platform-state change passes through — before you start a real task.

Procedure

  1. Launch the console from the command line:

    os-console

  2. Read the status bar at the bottom of the screen. It shows, left to right: your identity as username@tenant; the Machine-Based Authorization link state (MBA LINK ACTIVE, MBA LINK INACTIVE: <reason>, or MBA LINK PENDING); the active slot, shown as its full label (e.g. F9: SLM, not a bare F-key number); and elapsed session time. A [N pending] badge appears only when you have pending pairing requests to review.

  3. Press F9 to open the SLM Infrastructure dashboard. It polls the inference gateway every 10 seconds and shows five sections: Gateway (Tier A throughput, Tier B circuit state, node class), YoYo Fleet (per-node state for cloud GPU burst capacity), DataGraph (entity count and its own circuit state — DataGraph is a separate field, not a fourth tier), Queue (pending, in-flight, paused, done, quarantine, and poison counts), and Cost Today.

    Note: the three inference tiers are Tier A (local model, on this machine), Tier B (Yo-Yo — burst to cloud GPU capacity), and Tier C (external API, narrow-precision tasks against an explicit allowlist). This is not the same three-way split as DataGraph availability, which the dashboard tracks separately.

  4. Press R to force an immediate refresh of the F9 dashboard rather than waiting for the next 10-second poll. The on-screen hint line confirms the shortcut is live.

  5. Press F12 to open the Input Machine — the platform's mandatory ingestion checkpoint. Every operator input that modifies platform state passes through this slot; it cannot be bypassed by a menu or mouse path.

    Warning: F12 is not a sandbox. A submission here is a real write. If it succeeds, it's appended to the platform's immutable WORM ledger and cannot be retracted — don't submit throwaway content to "just see what happens."

  6. Submit a short, genuinely disposable test note if you want to see the flow complete. You'll see one of two outcomes: a confirmation showing a Payload ID and the ledger height/root it was written at (with a warning variant if the submission carried a non-fatal issue), or a plain error panel if the submission failed. There is no separate "quarantine" outcome in this flow — that concept belongs to a different subsystem (the inference queue shown on F9), not to F12.

  7. Move between F3, F9, and F12 and confirm the status bar's active-slot label updates to match each time.

Expected outcome

You can read the status bar's identity, link state, and active-slot fields at a glance; the F9 dashboard shows live Gateway/YoYo Fleet/DataGraph/Queue/Cost data and responds to a manual refresh; and F12 has accepted or rejected a real submission, with the outcome visible on screen.

Verification

  • The status bar's active-slot label changes correctly as you switch between F3, F9, and F12.
  • F9's on-screen "updated" timestamp changes when you press R.
  • A successful F12 submission shows a Payload ID and ledger position; the platform's WORM ledger records it as a genuine, permanent entry.

Rollback

Exploring the status bar and F9 dashboard changes nothing — exit the console at any time with no cleanup needed. A real F12 submission is the one exception: it cannot be rolled back once confirmed, which is why step 6 above is optional and only worth doing with content you're comfortable being permanent.

If the console doesn't respond as expected, exit and restart it. Watch your own terminal's output for errors rather than checking system logs — a plain os-console launched from your own shell isn't running under any system service, so a system log has nothing to have captured.

Next steps

See also

Cite this record: /wiki/explore-the-console — 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 →