Skip to content

The workspace

Staff log in and land in the Chamber.

The Chamber is a desktop of tools. A persistent bar across the top, a dock of full-screen tools, and pinnable widgets. Staff open a tool the way they open an app on a Mac.

SCREENSHOTFull still of the Chamber: the desktop shell with the global bar, the dock of tools, and one tool open. Real product UI.SCREENSHOT, 4/3

One surface

One workspace holds every tool.

Every tool opens in the same shell, over the same record, under the same login. There is nothing to install and nothing to reconcile between windows.

The interface is a projection of permission

What a person sees in the dock, and inside each tool, is a projection of their permissions. They see only the tools, screens, and patient data their role allows. The product a user sees is literally a projection of what they’re entitled to.

The dock

Full-screen tools, and the widgets you keep in view.

The dock holds the tools as full-screen applications.

Gate to admit, Atlas to read the record, Forge to order, Vault to bill. Open one, and it fills the workspace.

Around them sit pinnable widgets.

The small, always-on views a role wants at hand (a bed count, a task list, an alert feed) without leaving the tool you’re in.

SCREENSHOTThe dock of tools with one tool open and two pinned widgets on the side: a live bed count and a task list. Real product UI.SCREENSHOT, 4/3

Three parts, one surface

What’s on the screen.

  • The global barA persistent bar across the top: the patient in context, search, and the actions that follow you between tools.
  • The dockThe tools as full-screen applications. A person sees only the ones their role is entitled to open.
  • Pinnable widgetsSmall, always-on views a role keeps in sight (a bed count, a task list, an alert feed) pinned beside the open tool.

Governed at the data

The dock isn’t a menu someone remembered to hide.

Hiding a button was never the mechanism.

What a person can open, see, and do is decided by the platform’s one authorization check, Cirith, on every read and every write. The restriction lives at the database read path, so a user physically cannot query records they aren’t entitled to.

The Chamber simply shows the result.

A workspace shaped to exactly what the person is allowed to do.

How authorization works

DIAGRAMTwo staff roles side by side: the same Chamber rendering a different dock and different record access for each, driven by the authorization check.DIAGRAM, 4/3

Powerful. Responsible. Pensieve.

Get started