ACP Case Flow

Live production path: YAML → CompiledPolicy (startup) → specialize on Start → coordinator → plan-orchestrator → Dagster/Ray → recursion. Mock mode uses curated profiles without live vendor calls.

Compiler · CompiledPolicy

loading… Loaded from query-planner at startup / hot-reload — not when you click Start.

Policy hash

—

Compiler

—

Registry / policy / caps

—

Modes

—

Capabilities

—

Failover chains

—

Planner

—

Query modes

Capabilities

Failover chains

Intent · Specialize

waiting for Start Per-request path: Intent AST → LogicalPlan → Physical hints/DAG (from ExecutionPlan.specialize).

Click Start to specialize against the CompiledPolicy above. Case Flow reconstructs an Intent AST from mode + identifiers (coordinator path); NL→AST uses POST /v1/intent/extract.

Flow timeline

Submit a seed request to watch the production flow.

Case state

Status—

Iteration—

Dagster run—

Identifiers—

Case ID—

Demo—

Step payload

Select a timeline step to inspect its payload.

Compiler · CompiledPolicy

Intent · Specialize

1 · Intent AST

2 · Logical plan

3 · Physical (hints + steps)