MedReception

Agent Studio

Author, test and operate the AI receptionists — with the behaviour that matters expressed as typed objects a machine can check, not as prose in a prompt box.

Scaffold — API online, schema in design
Grounding

Facts, with provenance

Katie once produced confident, wrong opening hours. A prompt forbidding invention did not stop it; only real facts did. So facts are objects with sources, and a node cannot answer from an unsourced claim.

Guardrails

Loops end deterministically

“Required variable still null after three turns” is a state-machine fact, not something to hope the model notices. The runtime decides, and the fallback is declared.

Publishing

Broken pathways don’t ship

A transfer node nobody could reach took 0 of 45 calls while the agent kept promising it. That is now a publish-blocking check, not an incident.

Inheritance

Every value explains itself

Settings resolve platform → tenant → agent → pathway → node. Five layers is a lot of places to hide, so each effective value carries the layer it came from.

What comes next

  1. Schema migrations — pathways, nodes, edges, variables, facts, guardrails, versions.
  2. Publish validation — the checks that block a bad pathway from going live.
  3. Pathway builder — the canvas, once the model underneath is settled.
/health API docs Status