How to read this page
- Every step is one screen, or one moment, in a real run. The label under the title names where it happens, and the step reads in the same order each time: what is happening, the evidence, and then what to look for in it.
- Screenshots are real pictures of the Munitas console, the web app that people open in a browser. Click any picture to enlarge it.
- Every name of a person, patient or card holder in the example data is invented, and every screenshot is unedited apart from being cropped to the part that matters.
Words used on this page
- Organisation
- A company or hospital group that uses Munitas. Each organisation sees only its own data.
- Department
- A team inside an organisation that owns some of its data, such as Cardiology.
- Dataset
- A named collection of records, such as a table of patient admissions.
- Version
- One sealed state of a dataset. Changing the contents means making a new version, never editing an old one.
- Sealed
- Finished and closed for good, so that it can never be edited.
- Access level
- How restricted a dataset is. Raw is the most restricted, and nobody may read it without permission. Published is the most open.
- Custodian
- A person who holds the data custodian role, which allows deciding who may read data. A custodian decides for the departments they are an approver for.
- Request
- A written ask to read one dataset for one stated purpose. The custodian of the department that owns the dataset decides it.
- Purpose
- The reason a person states for reading data. A lease covers that purpose only, unless the custodian chooses otherwise.
- Lease
- Permission, given by the custodian, to read one dataset for one stated purpose and for a limited time.
- Agent
- A program registered on Munitas, with a named owner, that Munitas runs on somebody’s behalf instead of a person reading data directly.
- Container
- An isolated environment, with no network access of its own, where Munitas runs an agent.
- Run
- One execution of an agent or a pipeline, started for a stated purpose.
- Principal
- Munitas’s word for whichever person or program is being checked.
- Fingerprint
- A value worked out from the exact contents of a file. It changes if even one byte changes, so it shows that a file was not altered.
- Deploy
- To make one version of an agent the one that runs when somebody starts a run. Only one version of an agent is active at a time.
A run waits until a custodian grants permission
An agent is a program registered on Munitas, with a named owner, that Munitas runs on somebody's behalf. Registering an agent gives it no right to read data. When it needs a Raw dataset, its run waits until the custodian of the department that owns the dataset decides.
radiology-intake-triage ranks radiology documents so that the most urgent ones reach a human reviewer first. It belongs to Radiology, so the custodian of Radiology decides what it may read, and no other department's custodian does.
An agent's code is kept as sealed versions, the same way a dataset is. When it runs, the agent acts under an identity of its own, shown here as its runtime identity.
Devi chooses a zip of a small project. The model field says none, because the code calls no AI model, and the only tool it may use is read_dataset_version. The list of tools is a declaration. What limits the agent is that every read it makes is still checked against the same rules as a person's.
read_dataset_version.The version is identified by a fingerprint of its own code, which changes if any part of the code changes, and it is sealed on arrival. The platform runs it in a container, an isolated environment with no network access beyond its own requests for access.
After deploying the new version, Devi names a purpose for a run and chooses radiology-reports, a Raw dataset that Radiology owns. Munitas warns before the click, not after.
The run is recorded and goes nowhere until the custodian decides. That is not a failure. It is the same pause that a person's request would meet.
Okonjo is the custodian of the Radiology department. The request names both people involved: Devi asked, on behalf of the agent's own runtime identity, to read the Radiology dataset. Nothing from Cardiology appears in this list.
Okonjo's grant covered one purpose and was not a standing credential. Devi starts a second run on the same dataset for another purpose, and it waits again. This is what Raw data always gets. Reviewed data, which is no longer Raw, can be granted more widely.
Okonjo grants the second request, which this page does not show as its own screen, and the waiting run resumes by itself. Under each green label is the text that the agent's code printed. The sample agent prints one fixed result.
contains an unusually urgent phrase, flagged for a human reviewer first.