Technology
Clinical Corvus separates clinical control from the runtimes used to execute models and tools. The goal is to keep policy, state, evidence, and response shape stable when providers or libraries change.
Principles
- Corvus owns the clinical control plane.
- Clinicians retain the final decision.
- Longitudinal state and episode state have separate boundaries.
- PHI is not shared with third parties by default.
- Evidence and uncertainty remain visible in the response.
- Each surface shows only the traceability its execution path produces.
Architecture map
| Layer | Responsibility |
|---|---|
| Frontend | Workspace, dashboards, draft review, and context display. |
| API | Authentication, tenant, clinical data, tasks, usage, and policy. |
| Corvus control plane | Question profile, task sequence, budgets, gates, CaseState, and AgentResponse. |
| AI runtimes | BAML for structured functions and Langroid in selective agent or task paths. |
| Retrieval | Local corpus, BM25, vectors, bibliographic sources, and governed web fallback. |
| State | Longitudinal context, episode state, working memory, and learned preferences. |
| Rails | Evidence, patient context, provenance, and response state. |
Execution paths
The canonical task pipeline uses /api/agents/tasks/* for governed discussion and research actions. Clipboard, Plan, Academy, and some helper actions have their own contracts. They must not be described as if they produce the same provenance.