Reading the document you are approving
The console's document page: where it is, what it shows about a document, and where the rest is described.
Before you decide a gate, read what you are deciding on. The console served by saphan-gateway
gives every document of the record a page of its own, so the order, the executor's status and the
review verdict can be read in the browser, behind the same sign-in as the rest of the console
(signing in).
- Find the document. The Documents screen (
/console/documents) lists the documents the record holds; see screens and routes. - Open it. A document's page has an address of its own,
/console/doc/<id>, so it can be quoted and sent to somebody else who signs in to the same console. - Read the header before the text. The page names the document's kind, who wrote it, whether and by whom it is signed, when it was written, its path, and the stream — and, where there is one, the track — it belongs to. The text below is the document itself; a switch shows it raw.
The page reads; it does not decide. Recording a gate decision is a separate act, described in recording a decision from the console.
⚠ What is not described here: how fresh the list is relative to files written by a running leg, and what the page shows for a document the record names but cannot open. Read the console section for the screens themselves, and check a surprising page against the file on disk before you act on it.
Reading the gateway's answers
Per operation: what it answers, how fresh it is, and the field you must read before the numbers.
Metrics export: what you get
Three metrics from the record to any OTLP collector you run, the rule that governs every label on them, and the metrics a monitoring team usually asks for that this deliberately refuses.