agent trace
…
…evidence receipts
what this screen is, and is not
This is a visible agent trace: what Baymax called, read, wrote, held, and verified. It is not hidden chain-of-thought.
This is a closed-loop ER simulation, not a deployed clinical system. The action engine commits a Bed Ops disposition to durable SQLite; it does not write to a hospital EHR.
The patient corpus is synthetic. The only real-world data is openFDA adverse-event reporting, which is a population safety signal — it does not prove causality for any individual patient.
A green follow-up means the case left dated, owned work behind and that row was re-read from the store — not that anyone was followed up. Baymax drafts a referral and proposes windows; sending it and booking a slot need a human and are not implemented. Changing a medication or dose, and deciding admission or discharge, are forbidden to it outright.
The screen renders outputs/trace_<case>.json
exactly as the backend wrote it. It cannot colour a stage green that the trace calls
yellow, and it has no steps of its own.
Trace contract: baymax.trace.v1 ·
baymax/trace.py