Saphan StudioDocs
The console

The console

The owner's view of the record: the screens, the small number of acts, and which of them are signed with your passkey.

For the owner and whoever reads the fleet on their behalf.

After reading it you can find any screen, know what each one is for, and decide an act from the card the console hands you.

Before you start: an installed machine with an owner — the console is behind a sign-in, and first run is how a machine gets one.

The console is the owner's view of the record — the signed, append-only account of everything the fleet did: which stream ran on which machine, what it cost, which gate a human decided and how, what a role said and what it returned.

It is served by saphan-gateway — by default at http://127.0.0.1:7656/console. A plain /console opens Today; every screen lives under /console/app/. The pages in this section describe that console. The last four pages describe the previous console, served by the projection server (saphan server start, or the saphan-server daemon); see Screens and routes for which console answers where.

Where a screen or a part of one is drawn but its values do not come from the record, the screen marks it as sample data, and this section says so on that screen's own paragraph.

PageWhat it answers
What the console isThe boundary: what it reads, what you sign in it, and what stays your terminal's.
Signing in and finding your waySigning in, the sidebar, Simple and Advanced, search, the bottom panel, and how to read any screen.
Today, Stuck and your notesToday, Stuck, Ideas and Notepad — what waits for your hand.
RolesAdvisor, Master and Scribe: a role's screen, its sessions, and what the console does not do there.
DevelopmentTrains, Runs, Source map, Pull requests, Event Log, Bugs, Reports, Prompts.
Rules, costs and the recordRules, Costs, Documents and Audit.
The fleetAgents and Sessions.
SettingsWhat is yours per user, and what is an operator's act on the host.
Screens and routesEvery screen, its address, its group, and where its data comes from.
What it does not protect againstThe limits, stated as limits.

What this section does not cover

⚠ Most acts are still your terminal's, so no page here is a substitute for Working with git — that is where the acts live. ⚠ There are no pictures of the current screens in this section yet; the text is the description.

On this page