01
Process
The steps, states, handoffs, deadlines, approvals, and recovery paths that define how work actually moves.
Every AI team needs a system of action.
Systems of Record hold what happened. Systems of Insight show what matters. Regisseur turns the next step into governed work — assigned, executed, reviewed, and recorded.
Product proof
The surface is real product UI, not a metaphor.
The deeper operating-reality argument now lives on its own page. The homepage moves quickly from promise to primitives, with screenshots where they prove the system shape.
Read the operational reality →
§ 02 — How it works
Four configurable primitives. One operating surface.
02
Tools
The bounded capabilities agents and humans can call: read, write, transform, notify, sign, escalate, or verify.
03
Agents
AI teammates with versions, ceilings, input contracts, output schemas, and explicit ownership inside the process.
04
Integrations
Connections to systems of record through scoped provider and MCP contracts — not unbounded access.
§ 03 — What the platform does
The team, the process, and the next decision stay in one frame.
01Team Layer
Coordinates the team
Humans and agents share ownership of the same operational process. Every task has an accountable owner, an autonomy ceiling, and an escalation path.
02Execution Layer
Executes deterministically
The process runs as typed, repeatable steps. AI reasoning is one bounded tool inside the process, not the process itself.
03Decision Layer
Surfaces the next decision
The next action arrives with context, confidence, lineage, and the reason it needs a human or agent owner. The why travels with the work.
§ 04 — Operational team surface
A team — some human, some AI — owns the process.
Process · configurable
New work enters. The team advances it.
processtoolsagentsintegrations
01
Intake request
Read source record · validate required fields
Intake Agent
02
Gather evidence
Call bounded tools · chase missing inputs
Evidence Chaser
03
Review exception
Low confidence → human decision
Sarah Chen
04
Commit outcome
Approve · explain · write lineage
Decision Reviewer
Mid-process delegation
Sarah delegates a new evidence task to an agent, sets the ceiling to always-review, and dry-runs it before the change reaches live work.
new taskVerify missing document packet
§ 05 — Safe to deploy
Six structural guarantees. Before the first process goes live.
S.01
Audit trail on every decision
Reconstruct any work item — what happened, who decided, on which version of the rules.
S.02
Regulatory versioning
Past work remains re-runnable on the exact forms and agents that were live when the process started — even after rules change.
S.03
Configurable autonomy ceilings
Every agent operates within a ceiling set by operations — always review, graduated, or fully autonomous. The agent cannot exceed it.
S.04
Deterministic processes
Agents run typed, repeatable process steps. AI reasoning is one step — not the driver.
S.05
Workspace-wide emergency brake
One action pauses every agent, queue, and outbound message across the platform.
S.06
Configurable without engineers
Process managers build and adjust operational processes in conversation — not sprints.
You never trust the AI. You trust the deterministic boundaries constraining it.
Read the full governance model →§ 06 — Deploys above your stack
Records hold what happened. Insights show what matters. Regisseur acts.
SYSTEM OF ACTION
The governed surface where signals become assigned, executed, reviewed, and recorded work.
ProcessToolsAgentsIntegrations
SYSTEMS OF RECORD
Authoritative operational history. Unchanged, not replaced.
ERPCRMTMSDocument storeCore database
SYSTEMS OF INSIGHT
Analytics, forecasts, scores, and signals that inform the next move.
BIAnalyticsForecastingMarket dataScorecards
§ 07 — Why the scaffolding matters
RPA breaks on judgment. LLMs break on accountability.
RPA cannot adapt when the work requires judgment. Agent frameworks can reason, but they do not provide causal audit, runtime compliance, autonomy ceilings, or an emergency brake. Regisseur is the production scaffold for operating AI in real workflows.
| Approach | Cognitive adaptability | Causal audit | Runtime compliance | Autonomy ceiling | Emergency brake |
|---|---|---|---|---|---|
| Legacy RPA | None | Logs only | Offline policy | N/A | Manual |
| LLM-on-RPA bolt-on | Yes | Opaque | Policy drift | No | No |
| Agent framework | Yes | Tool logs | Developer effort | Prompt-level | No |
| Regisseur | Yes | Append-only · replayable | Tier 1 · enforced | Engine-level · earned | Workspace-wide |
LangChain builds the agent. Regisseur is the production scaffolding required to operate it.
§ 08 — Solutions
One platform. Many operational teams.
Live pattern
Term life intake
A regulated intake-to-decision process with human review gates, external evidence collection, and signed-output lineage.
Read the Term Life briefConfigurable
Claims operations
The same primitives model a claim as a process owned by adjusters, specialist reviewers, and bounded agents.
Discuss claims operationsConfigurable
Supply chain operations
Operational work with systems of record, external parties, and SLA pressure can be configured without rewriting the engine.
Discuss supply chain§ 09 — Deployment-ready operations
Not just configurable. Deployable, testable, and promotable.
D.01
Workspace providers
Mail, messaging, signing, and error reporting resolve per workspace. Admins test connections; every write is ledgered.
D.02
Signing as a process pause
A process can halt on an external signature, render a token-gated signing portal, then resume the cascade on completion.
D.03
On-prem capable data plane
Local Postgres, storage, queue, and DocuSeal support regulated evaluations without a hosted product data plane.
D.04
Signed vertical bundles
Workflow templates, agents, forms, documents, and tools move between workspaces as audited operational packages.
The product story now extends past orchestration: Regisseur can configure the workspace, prove the provider path, and package the vertical.
See the deployment model →§ 10 — How the work splits
Seamless human–AI teams. Bounded by design.
Agent team · Humans
Judgment & escalations
- FocusComplex work
- OwnsOperational outcomes
- WorkExceptions · approvals · decisions
- SpeedValue-added · no re-keying
AI team · Bounded agents
Orchestration & follow-up
- OrchestratesFollow-up loops and tool calls
- ApprovalsMandatory human sign-off where required
- FlagsLow-confidence → human owner
- NeverOverrides autonomy ceiling
§ 11 — Start a workspace
A 45-minute walkthrough.
Your process, configured as a team.
Bring one operational process with human judgment, system data, and repeatable follow-up. We’ll map the process, the tools, the agents, and the first review gates.