The handoff is a form, not an error.
A 0-to-1 agentic platform for regulated work. When it isn't sure, a person doesn't get a failure. They get a decision already prepared.
Illustrative. What it never says is "task failed".
The problem
An agent that improvises can't be allowed near a medical record.
The appeal of agents is that they work things out as they go. In a regulated workflow that's exactly the problem. You can't approve a plan that doesn't exist yet. You can't price work you can't see. You can't contain a step nobody decided on.
And when it goes wrong, "the agent decided to" isn't an answer anyone in healthcare accepts.
Everything here follows from refusing to let the system make it up as it goes.
The first decision
The plan is written before anyone starts working.
The orchestrator doesn't improvise step by step. It produces a plan up front, showing which steps depend on which. The cost is flexibility. What you buy is worth more.
The shape of it
A small team with strictly defined jobs.
Five layers, and the value is in what each one is not allowed to do. Only one of them can touch an outside system.
Receives the job and writes the plan before anyone starts working.
One extracts the diagnoses. One finds the procedures. One looks up codes.
The only ones that touch outside systems. Everything else reasons.
Confirms the output is well-formed and permitted.
Watches for things going wrong, and can stop the run.
Memory is two tiers, deliberately separated. Short-term holds the current job and is thrown away afterwards. Long-term persists what is worth keeping. Keeping them apart is what stops one case bleeding into another.
Governance
Three mechanisms, not a policy document.
Each of these is something the code enforces. None of them is something a document requests.
Blast radius
Limits on how much damage a single action can do. The bound exists before the action does.
Step-level traces
A record of every step, so a wrong action is explicable afterwards rather than mysterious.
Confidence floors
65% while testing. 85% minimum in production. Retuned against what actually happened, not fixed at launch.
The decision I would defend hardest
Review people use, rather than review people route around.
Below the confidence floor, the work goes to a person. What that person receives is the whole design.
Not "task failed". A pre-filled decision form, with the context already compiled. The relevant record excerpt. The suggested code. The rule in question. The alternatives.
That single choice is the difference between review people use and review people route around.
It's the same idea that shows up later in document processing. Escalation is a product surface, not an error path. Build it as a failure and people will work around it. Build it as a decision and they will use it.
Where it stopped
The proofs of concept never converted.
They were proofs of concept in medical encoding, and they had not converted before I left. The accuracy figure is sound. Its scope is a POC. Worth stating plainly, rather than letting a reader assume otherwise.
A horizontal agent platform sold into medical coding competes with vendors who ship the vertical, and that tension is real, and having a view on it is more useful than avoiding it.
Where the work lived in legacy systems with no integration, agents reasoned over the screen. It unblocked the work and a layout change is an outage. Nothing records where that actually bit.
Eighty per cent handled without a person. That's the observed split, not a limit anyone tested for, and what it would take to move it, or what it would cost, isn't on the record.
What happened to it
The architecture outlived the context it was built in.
Three deployment modes came out of one codebase: cloud managed, hybrid, and air-gapped on premises. That last one is what regulated buyers actually ask for. It's a decision you make at the beginning or not at all.
Foundation models were routed per workflow by accuracy and cost rather than picked once: GPT, Claude and domain-specific models, with the platform agnostic to all of them.
The same architecture is the foundation of a different company's platform now. That says more about the design than any accuracy figure does.
