§ 01 — Product · Workflow BuilderDocument · REG-WB-2026.04

Design the process.
Assign the agents.

Human teams describe the process in plain language. Regisseur turns it into typed steps, bounded tools, agent roles, review ceilings, SLA clocks, recovery paths, and versioned promotion.

Book a walkthrough →See the safety contract
No orphan agents.
No YAML. No DSL.
Authored byHuman operations teams
DesignsProcess · agents · tools
VersioningEvery change · reversible
ReviewDiff · dry-run · promote
Time to changeMinutes, not sprints
§ 02 — The authoring loop

Four moves. One process the team can own.

01Describe

Describe the work.

"When evidence is outstanding after 72 hours, chase the owner; after 48 more, escalate to the lead."

02Assign

Name the team.

Choose which humans own exceptions, which agents handle repeatable work, and where the handoff must stop for review.

03Bind

Bind tools and ceilings.

Allowed tools, schemas, rate limits, review gates, and ceilings are explicit per step.

04Promote

Dry-run, diff, promote.

Replay past work against the draft. Diff the behavior. Promote to production with an immutable version tag. Roll back any time.

§ 03 — Authoring surface

The conversation on the left. The team and process model on the right.

regisseur · process-designer · customer-process
DRAFT · v3.5.1-rc
Process · customer-process
7 steps · 3 agents · ceiling floor always review
diffdry-run · 30dpromote
  1. 01
    intake_request
    mcp · source_record.read · typed → WorkItem
    Graduated
  2. 02
    evidence_fetch
    mcp · document.read · retry · 3×
    Graduated
  3. 03
    evidence_chasetrigger · packet_age > 72h
    agent · Evidence Chaser v2.1 · comms.send · TTL 72h
    Always review
  4. 03.b
    escalate_leadafter 48h · no response
    route · process.lead_at(now) · SLA 24h
    Always review
  5. 04
    decision_draft
    agent · Decision Drafter v1.8 · confidence floor 0.70
    Always review
  6. 05
    next_decision
    lineage-linked · human owner required
    Graduated
  7. 06
    external_approval
    external_action · provider waits · resume on completion
    Graduated
Dry-run · last 30d · 412 work items
Behavior differs from production on 38 work items
Same · 374 Different · 38
Compile clean · 0 ceiling violations · 0 unbounded tools
Draft v3.5.1-rc
Product evidence

The agent is configured inside the process, not beside it.

Agent mission, tools, review ceiling, owner, dry-run impact, and promotion state are visible in one authored surface.

Regisseur agent execution designer with configuration, diff, and process preview
Agent designerConfigure · dry-run · promote
§ 04 — Agent delegation

The human team can create a new agent role and delegate work mid-process.

Configure agent

Evidence Chaser · v2.1

The process lead defines the agent’s job, allowed tools, review ceiling, handoff conditions, and the exact events that wake it up. The agent is a teammate inside the process model, not a free-floating bot.

MissionResolve missing evidence packets
Toolsdocument.read · comms.send · status.write
CeilingAlways review on escalation
Reports toSarah Chen · Operations Lead
01

Delegate task

Evidence packet missing for 72h → assign to Evidence Chaser.

02

Simulate impact

Dry-run against recent work and show items that change behavior.

03

Promote safely

Promote agent assignment with version, owner, and rollback path.

§ 05 — Expressible primitives

The grammar of a process.

Triggers
Event on ledger · elapsed time · SLA threshold · upstream step outcome · external webhook · schedule
Steps
MCP tool call · LLM reasoning (bounded) · deterministic transform · human task · approval gate · external action · signal emit
Branches
Typed predicate · confidence threshold · policy guard · SLA miss · explicit human override
Ceilings
Per-step autonomy level · per-tool rate limit · per-workspace emergency brake · policy floor (compiler-enforced)
Recovery
Retry · fallback · escalate · quarantine · pause for signature · rewind to checkpoint · route to named reviewer
Lineage
Every output tags its inputs · rule version · tool version · human decisions. Non-negotiable.
§ 06 — External actions

A process can pause outside the platform, then resume cleanly.

01

Create envelope

The process reaches a signing step and creates the provider envelope with work-item lineage attached.

02

Await signature

The node moves to awaiting signature. Operators see it as a queue state, not an exception.

03

Token-gated portal

The signer gets a purpose-specific link. No platform account is created for external parties.

04

Resume cascade

The completion webhook stores the signed PDF, updates the ledger, and wakes the next step.

§ 07 — Versioning & rollback

Every process is a document with a history.

Work opened under v3.4 keeps running under v3.4 — even after v3.5 ships. The only way to change history is to re-open the work item.

Every promotion is a signed, dated release. Every rollback is a revert, not a delete. When an auditor asks what the system did on a Tuesday in March, we can answer with the exact process, rule versions, agent assignments, and tool definitions that were live that day.

§ Next step

See a process designed live.

Bring one open requirement loop — we’ll describe it, scaffold it, run a dry-run against real data, and show you the diff. 45 minutes, no slides.

Book the walkthrough →Read the governance model
Authored by
Process managers
No
YAML · DSL · engineering tickets
Every change
Versioned · reversible