Skip to content
PointSav Digital Systems

Revision as of · 33df4c92

Historical revision — this record as it stood on 1 July 2026, not the current version. View the current record →

How to explore the console for the first time

The platform console is a terminal application that organises operator-facing tools into a set of function-key slots, each running a distinct Cartridge. When you open the console for the first time, the interface may look unfamiliar — this guide walks you through the layout, how to move between slots, and how to confirm the system is working before you start your first real task.

For the full TUI reference, see navigate-console-tui. For the F-key slot model in depth, see use-f-key-model.

Prerequisites

  • A paired device with appropriate tier access (see pair-a-new-device)
  • The console binary built and available in your PATH, or the workspace binary at ~/Foundry/clones/<archive>/os-console/
  • A terminal emulator that supports 24-bit colour and at least 80×24 characters

Step 1: Launch the console

Start the console from the command line:

os-console

If the binary is not in PATH, run it directly from the build output:

~/Foundry/clones/<archive>/target/debug/os-console

The console opens in full-screen mode. You will see a three-zone layout: a status bar at the top, a main content area in the centre, and a navigation strip at the bottom.

Step 2: Read the status bar

The status bar at the top of the screen shows the system's current state at a glance. Left to right:

  • Identity — the active operator identity (a short name string set at pairing time)
  • Auth state — INPUT, USER, or READ — the access tier of the current session
  • Active slot — the F-key currently active (e.g., F3)
  • SLM tier — the Doorman tier in use: A (DataGraph live), B (SLM only), or C (local fallback)
  • Session duration — time since the console was launched

If the auth state reads READ and you expected INPUT or USER, the device has not completed the pairing sequence for the requested tier. See pair-a-new-device to resolve.

Step 3: Navigate to the Doorman health slot

Press F9 to activate the SLM Cartridge. This slot shows the Doorman health dashboard — the current state of the Tier A/B/C inference circuit.

Each tier shows its status:

  • A — DataGraph — green if the entity store is reachable; OPEN if the circuit has tripped
  • B — SLM — green if the local inference model is loaded and responding; OPEN if it failed to start
  • C — Local fallback — always AVAILABLE unless the local OLMo model binary is missing

Doorman health is the first thing to check when starting a session. A green A and B means the full inference and entity-lookup stack is available. An open circuit on either tier means some features are degraded; the console falls back automatically but you should note which tier is affected.

Step 4: Press R to refresh

While in F9, press R to force a Doorman health refresh. The status line updates within a second. This confirms the console is polling the Doorman service and the keyboard is responding correctly.

Step 5: Navigate to the Input Machine slot

Press F12 to activate the Input Machine Cartridge. This is the mandatory input checkpoint required by SYS-ADR-10 — every operator input that modifies platform state passes through this slot.

You will see a prompt area. Try submitting a simple text note. The console shows whether the input was confirmed (written to the WORM ledger) or rejected (quarantined with a reason code).

Step 6: Review the status bar changes

As you move between slots, the status bar's Active slot indicator changes. Confirm that switching between F3, F9, and F12 updates the indicator correctly. If the indicator does not update, the TUI rendering loop may have encountered an error — exit and restart the console, then check journalctl -u os-console for error output.

Key takeaways

  • The three main zones are: status bar (top), content area (centre), navigation strip (bottom)
  • F9 = Doorman health dashboard; check this first at every session start
  • R refreshes the current slot without switching slots
  • F12 is the mandatory input checkpoint; all platform-state modifications route through it
  • READ auth state means INPUT or USER pairing has not completed for this session

See also

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 →