Documentation · The Lagstyr handbook
Reading your console
Your console is a set of server-rendered pages behind a sign-in. It holds no database and no authority of its own: every page is a read of your installation’s kernel, and every change you make through it is a proposal the kernel validates and routes for approval. The console says so itself, on its operations page: “the console holds no authority of its own.”
Everything in it works without JavaScript. If your browser blocks scripts, nothing is lost.
Five sections, named for what you are doing
The navigation is grouped by verb, not by department, and the first group is the work only a person can do.
| Section | What lives there |
|---|---|
| Decide | What needs your attention, your notifications, pending and decided proposals, and the spot-checks on agent actions. |
| Operate | Work queues, tickets, external effects, cash and commitments, and operating outcomes. |
| Govern | Authority, obligations, conflicts, policies, board resolutions, action classes, optional packs, AI systems, policy exceptions and access. |
| Investigate | Agents, a party’s brain page, sources, integrations, and the operations index, for when you have a question rather than a task. |
| Tools | Agent chat, the task designer, and the glossary. |
The labels in this book are the English ones. Your console may show them in another language; see Access, people and language.
Authority, projection and evidence are kept apart
Every page tells you which kind of thing it is showing. A record is authoritative: a decided proposal, a policy version, an access grant. A projection is derived from records at read time and may lag them: a brain page, the operating outcomes, the worklist queues. When a projection is stale the page says so, and says that a rebuild is queued. A figure never pretends to more authority than it has.
Absence is always written down
The console never leaves a cell blank. A field nobody filled in reads not declared, and the console is deliberate about the difference: a blank consequence field and a declared-harmless one look the same to a reader in a hurry, and they are not the same thing. A read that failed reads Unavailable, and the console is equally deliberate that unavailable is not empty. A queue that could not be read is never counted as clear.
Lists are windows, not pages
A long list shows its first rows and says so: Showing the first N rows, with the ordering named. There is no second page. Where a page offers a filter, the filter is how you see the rest; where it does not, the window is the design, and the page tells you more rows matched than are shown.
When a page says no
A refusal in the console is information, not an error. If you submit a decision on a proposal somebody else decided a moment earlier, you land on a page headed Nothing to decide, not a red warning. If you type an address the console does not serve, it tells you that nothing was changed. Read refusals as carefully as successes; they are written to be trusted.
Your session
You sign in through your organisation’s identity provider. A local password exists only as an emergency path, and the console says which kind of session you hold. A session idles out after a period without activity and ends after eight hours regardless.