Overview

The frame

The dashboard is what this is, what it never stores is what it is not, the connection is what makes any pane show anything, and roles and permissions is what you can see.

PartWhat it is
barThe top strip: wordmark, project, environment
status bandThe saffron strip under it: endpoint, facts
railThe left column: the kinds
indexThe middle column: the things of the chosen kind
recordThe right column: one thing, in full

Rail, index and record together are the body. Any one of the three is a pane.

The triad is meaning, not layout

The rail names a kind of thing. The index lists the things of that kind. The record fills the body with its details.

Left to right, always, whatever the things are.

Which is why the index is not a submenu: it lists rows, not destinations.

Search and filter an index

Every index has one search box, with a filter icon inside it. The icon opens one panel under the box, listing every filter that kind offers. While any filter is on, the icon turns saffron and carries a count, and a line under the box says what is applied: Showing Status: Open · Assigned to: To me.

Each filter is one section of the panel: its name, where it runs, and its choices. A choice is one of several, and picking one replaces the last. Any comes first and is where every filter starts, except the few that open elsewhere and say so on their own page. Choices apply as you pick them. Clear filters and Done end the panel.

Where it runsWhat it means
All of themSent to your Worker as the route’s own query, so the rows that come back are its answer over everything it holds
This page onlyNarrows the rows already read. Used where the route takes no such filter

A lookup is a field, not a choice. Where a route looks something up by an exact value, such as a purchase’s holder or a suppressed address, the panel draws a field for it. A value the route would not take is not sent, and the panel says so rather than counting it as applied. An address or a search term goes in the body of a read, never in a URL, which every request log on the way records; on a Worker too old to take it in a body, the field is drawn locked, naming the package to upgrade.

The search box and the filters combine. Where the route searches, as the user list does, the text goes to your Worker a moment after you stop typing. Everywhere else it matches the rows read, and on an index that reads a page at a time it says it matches only what was read. An index that pages reads one page first; More reads the next, and End of the list. says there is none.

What you see depends on what you composed

The dashboard composes its navigation and its calls from your Worker’s manifest, rather than from settings somebody maintains.

So a Worker that does not compose payments has no purchases pane — and that is a fact the client discovers rather than a feature somebody remembered to hide.

Run pithy add support and a working support pane appears on the next visit — panes and the calls behind them, with nothing for either side to configure.

Composed-but-empty is not the same as not installed

A capability with no management surface reports an empty list rather than being absent.

Composed, but nothing to administer and not installed are different facts, and a client that cannot tell them apart renders the wrong thing for both.

Knowing a capability is installed is not enough to call it

Every mount point is configurable. A dashboard that hardcoded /payments would 404 against exactly the adopters who customized anything.

Each capability builds its manifest entry from its resolved config, so the paths name where things actually are.

Grayed out, not offered and refused

Each declared route names the scope it needs, and the manifest reports what you granted.

So an action you did not grant is unavailable rather than a button that answers 403.

Everything here is live

Nothing is cached. Your users, purchases, audit events and support mail are fetched from your Worker, rendered, and discarded.

The moment we held a copy, we would have become the thing this architecture exists to avoid.

The panes

Your data: Users · Organizations · Purchases · Subscriptions · Entitlements · Ledger · Leaderboards · Game sessions and results · Ratings · Matchmaking and invites · Repositories · Audit trail · Support inbox · Email jobs and suppressions · Feedback · Cohorts

Your project: Connection · Capabilities and versions · Migrations · Secrets · Vector · Turnstile · Usage · Delivery · Tokens · Reconciliation · Revenue integrity · Cache · Alerts

Compliance: Access · Access attestation · Audit explorer · Evidence · Privacy · Reports

Yours: Settings and profile · Notifications

ESC