Saphan StudioDocs
The console

What the console is

A reading surface with a small number of acts — which of them your passkey signs in place, and which it hands you as a line to run.

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 a reading surface with a small number of acts: you decide an act a master handed you, you talk to a role, you catch an idea, you copy a command.

An act is signed by you, or run by you

Every act the console takes into the record is one of two kinds:

  • Signed in place with your passkey. A decision on a card in Today, a merge on Pull requests and an edit to a wagon that has not been dispatched open your device's passkey prompt. The server shows you the exact act — decision, gate, revision — and records it only after the passkey signs that act. Nothing is recorded until the prompt completes; dismissing it leaves the decision owed.
  • Handed to you as a line. Where an act has no passkey ceremony, the card shows the exact command the engine composed and a Copy button. The act is your hand in your terminal.

That is how the record knows who acted. An act signed by your passkey, or a command run by you on your machine under your seat, is an act the record can attribute to you and an auditor can read back. Everything else on the screen is a fact from the record, or a refusal that says why.

⚠ The Terminal in the console's bottom panel runs the saphan CLI on the console's host as the gateway's user, in the gateway's workspace — not as you. A step that needs your passkey is never signed there: the terminal sends you to the passkey prompt in the browser.

What follows from that

  • A gate is decided by you, either through the passkey prompt or by the line you run. The console never presses either for you.
  • A number you see was read from the record, and where the console cannot read one it shows nothing or says unread — never a zero it did not measure.
  • A refusal is a row, not an error message alone. When the fleet declines something, the screen carries the reason the engine gave; the Stuck screen collects them.
  • Sample data is marked. A value the console does not read from the record yet is drawn as sample, an act over sample data is refused with "Sample data — this act is not wired yet", and nothing is sent.

On this page