F36 · AGENTIC MULTI-AGENT ORCHESTRATOR · LIVE REFERENCE RUNTIME

Watch an agentic system plan, route, act, critique, recover, and stop for human authority.

This is executable orchestration, not a pre-rendered animation. The control plane runs in your browser, invokes sandboxed tools, mutates workflow state, preserves every attempt, and enforces automated gates before any protected release action can proceed.

Open F36 source View runtime code
RUNnot started
STATE VERSION0
STATUSIDLE
AGENT HANDOFFS0
TOOL CALLS0
RETRIES0
BLOCKERS0
01

REQUEST AND SANDBOX

Give the orchestrator a goal

02

CONTROL PLANE

Execution graph

05

HUMAN AUTHORITY

Protected release gate

ELIGIBILITYNOT EVALUATED
RELEASE STATENOT STARTED

The release control is disabled until all technical and safety blockers are cleared.

03

PROVENANCE

Live event trace

EVENTACTORSTATUS
04

EVIDENCE

Inspector

Run the orchestrator, then select any trace event to inspect its structured payload, tool arguments, result, timing, and provenance.
06

SPECIALIST REGISTRY

Capability routing

WHAT A SOFTWARE ENGINEER CAN VERIFY

The demo exposes the engineering behaviors that usually disappear behind a chat interface.

01

Task graph, not role theater

Tasks carry dependencies, required capabilities, status, attempts, evidence, and output contracts.

02

Capability routing

The router scores registered specialists and records eligible, rejected, selected, and fallback candidates.

03

Tool boundary

Every tool call passes through a gateway with arguments, side-effect class, result, latency, and audit state.

04

Failure containment

A failed attempt remains in provenance. The orchestrator retries or reroutes instead of silently hiding it.

05

Critic plus safety gate

Quality review and safety review operate on actual execution evidence before approval becomes eligible.

06

Human authority

The system can prepare and verify a release, but the protected action remains unavailable until a person approves it.

PRODUCTION ADAPTER PATH

Replace sandbox specialists with real model and enterprise tool adapters without changing the control plane.

The next production step is a server-side adapter that supplies authenticated LLM calls, private RAG, GitHub or Jira access, evaluation services, observability, and deployment tools while keeping the same routing, state, provenance, critic, safety, and approval contracts.