Sequence
One question, from screen to audit trail
What happens to one question: gates, cache, retrieval, draft, verdict, review, delivery, and what is written to audit on the way.
What it shows
The same design as the overview, read in time. The workflow screens the question, records that the gates passed, and looks up the cache with a key built from the question, the knowledge version, the model version, the persona and the study.
On a hit the reviewed answer comes back with no model call. On a miss the workflow retrieves claims-scoped grounding, drafts through the model router, and applies the content filter and the safety verdict.
Then it sends a review request and idles. A checkpoint keeps the pending request, so a restart or a deploy in the middle of a review loses nothing. The reviewer accepts, edits, rejects or escalates; the full trail goes to audit, and the answer is delivered or refused.
This is a reference design for an agentic clinical-trials Q&A assistant. It is a design, not a description of a system built as shown.
Key decisions
- Audit is written at the gates and again at the end, so a refused question leaves a record too.
- The cache key includes the model and knowledge versions: changing either is a miss, with no manual invalidation.
- The pause for review is a normal state of the workflow, not an error or a timeout.