Regulated work
Validate the workflow and the checks, not the model.
An AI model's answer is never exactly the same twice, so you cannot validate it like normal software. The workflow around it can be fixed. You validate the workflow and its checks once. Every AI draft must pass them, on every run, before a person signs.
Six design rules.
The workflow is fixed
A workflow is a written file. Before any work starts, it is turned into a fixed list of steps that can be shown and reviewed. Its version is locked, so the workflow you approved is the one that runs.
The checks are fixed
Each step can have a check script with clear rules for pass and fail. The same input always gives the same answer. A step without a clear result counts as failed, never as passed.
A named person signs
The agent drafts. A signed-in person approves at the points your procedures require. The approval and the person are recorded.
Everything is recorded
Every step, check result and approval goes into a record that is only ever added to. Your auditors can follow any piece of work from start to finish.
It runs in your account
The agents, the data, the backups and the encryption keys stay in your own cloud account. Agents use the AI model through your own agreement with the provider, such as a business associate agreement under HIPAA.
Agents get only what they need
Agents hold no keys to your systems. Each works in its own space, and changes that matter wait for a person.
The rules we design for.
This is how we design for these rules. It is not a certification and not a regulator's position. Your quality and compliance teams decide how it applies to you.
HIPAA
The US law for patient health information. Patient data stays in your account and goes only to vendors under a business associate agreement.
21 CFR Part 11
The FDA rule for electronic records and signatures. Designed so that signatures happen at named approval points, with the signer and the meaning of the signature recorded.
GxP
Good practice rules for regulated work, such as good manufacturing or clinical practice. Designed so that the workflow and its checks are validated once, with a validation pack for each release.
SOC 2
An audit of a company's security controls. The record of every step and approval is the evidence.
What a check cannot do.
A script only tests what it can measure: a field is filled, a reference points to an approved document, a deadline is met. It cannot judge whether a medical or scientific conclusion is right. That stays with a second reviewer and with the person who signs. Checks are also kept out of the agent's reach, so the agent cannot change the test it has to pass.
More detail: Validate the workflow, not the model
Industries we work in.
Life sciences
Pharma, biotech, medical devices and clinical research.
Healthcare
Providers, digital health, pharmacy and health systems. Where most of our shipped work is.
Payers
Health plans, insurers and the administrators between them.
Financial services
Fintech, lending and payments, with the same discipline: approval limits and a record of every action.
Tell us which work you want to hand off first.
Book a call