Ai Condor

13-ai-condor

Condor is the current agentic runtime. It is a distinct subsystem from TUCAN (06-ai-tucan), not a rename of it — Condor ships its own tool registry, HMS access layer, HITL approval gate, SSE/AG-UI frame pump, RAG-over-tools resolver, run spine, and frontend surface. TUCAN is on a deprecation path; Condor is where new agentic work lands, so the two carry separate layers rather than sharing one.

The migration itself is documented in Condor Engine — Ported Agentic Runtime; the per-subsystem topics below document Condor as it stands today, not as a diff against TUCAN.

Topics in this layer

• Condor Engine — Ported Agentic Runtime (Tucan→Condor Migration)
• Condor Tools Registry — the Descriptor-Driven Clinical Tool Catalog
• Condor HMS Tool Layer — Client, Id-Alias Proxy, Transport Port, Policy
• Condor HITL Approval — the Two-Axis Mutation Gate and the One Suspend Funnel
• Condor SSE / AG-UI Frame Pump — Emitter → Mapper → Wire → Consumer
• Condor RAG Tool Search — Per-Turn Candidate-Set Resolution
• Condor Diagnosis Engine — Deterministic Route Dispatch, Decompose, Plan Compilation
• Condor Session Lifecycle, Run Spine and Telemetry
• Condor Sandbox & Builder — Docker Workspace + Low-Code Agentic Definitions
• Condor Web Surface — the ddx-web Frontend for the Condor Engine

Reading order

Start with Condor Engine for the runtime shape, then Tools Registry → HMS Tool Layer for how the model reaches clinical data, then HITL Approval for what it is allowed to change. SSE / AG-UI Frame Pump and Web Surface are the emitter/consumer pair — read them together; the frame-prefix contract in the pump topic is load-bearing for both.