Reference table

The platform systems

Lists the Pensieve systems including Gate, Atlas, Forge, Vault, Nexus Manager and Cirith Manager, with the responsibility each one carries.

Pensieve is a set of systems that share one foundation. This page lists each system and the responsibility it carries, from the care systems through the hospital model and access, to the connective, workflow and intelligence systems, and the shared platform beneath them all.

The care systems

Four systems carry a patient from arrival to a settled account. Gate opens the visit, Atlas holds the record, Forge carries the orders, and Vault runs the money.

System	Responsibility
Gate	Registers patients, opens visits, and runs the visit lifecycle from arrival to discharge.
Atlas	Holds the patient record, the one place a patient's clinical data lives.
Forge	Carries an order from placement to completion, over a fixed catalogue, with a frozen snapshot of each placed order.
Vault	Runs billing and revenue, from a raised charge through invoice, payment and settlement.

The model and access

Two systems describe the hospital and decide who may act within it. Nexus Manager models the hospital, and Cirith Manager resolves access from that model.

System	Responsibility
Nexus Manager	Models the hospital: sites, units, locations, beds, services, assets, people and roles.
Cirith Manager	Decides, for every action, whether a person may take it, and keeps the access log.

The connective systems

Three systems reach the hospital's own machines and studies. orophin is the on-site bridge, Westron is its console, and the image study viewer reads studies in the browser.

System	Responsibility
orophin	The on-site bridge that carries connections to the hospital's own machines over one outbound path.
Westron	The console where staff configure and monitor the connections orophin carries.
image study viewer	Reads imaging studies in the browser, tied to the right patient and order.

The workflow and intelligence systems

The remaining systems run repeatable work, forms, alerts, messaging, analysis, safety and quality, and locally built tools. Vigil runs the hospital's safety and quality work, holding reporter identity separately. Each reads the same governed data underneath.

System	Responsibility
Cadence	Runs a repeatable multi-step process and shows which step each case is on and what is next.
Quest	Turns due work into scheduled tasks and shows each member of staff their own due list.
Glyph	Builds and runs forms, with validation, calculation, sign-off, and a locked completed form.
Sentinel	Holds the alert ledger, decides when an alert fires, and tracks acknowledgement and escalation.
Raven	Sends a message over the right channel within consent, and keeps the delivery log.
Falcon	Turns hospital activity into governed metrics, and shows the lineage of every number.
Vigil	Runs the hospital's safety and quality work: incidents, investigations, mortality reviews, complaints and accreditation evidence, with reporter identity held separately.
Durin	Composes new tools and desktop widgets on the platform's governed data.

Staff meet these systems inside Chamber, the staff desktop. A person signs in, lands in the Chamber, and reaches the tools their role and relationships allow.

The shared platform

Beneath the systems sits one shared foundation that every system routes through. This is what holds the systems together as one platform rather than a bundle.

Capability	What it provides
One record	Every system reads and writes one patient record rather than keeping copies.
One authorisation decision	Each read and each write resolves against one access decision.
One audit entry per change	A committed change carries its audit entry, written with it.
One event log	Systems react to one another through events rather than direct calls.
One entry and exit path	Every request enters through one path, and every outside connection leaves through one path.
Enforced boundaries	Automated checks hold each boundary as the platform is built.

One foundation, many systems

A system carries its own responsibility and reaches the others only through the shared foundation. That is why a rule written once in the foundation holds across every system above it.

Read the organising idea behind this arrangement in the shape of the system, or the vocabulary these systems share in core concepts.