Pipeline reaches external action
A policy-issue step creates an envelope and marks the node awaiting signature.
Regisseur is not a hosted chatbot bolted onto operational work. It is a deployable operating layer: local data plane, workspace providers, signed bundles, token-gated external actions, and runtime-produced demo artifacts.
Execution, audit events, work state, provider calls, and cascade resumes stay inside the deployment boundary.
Core data, signed documents, and default e-signature flows can run without a vendor-hosted data plane.
Existing systems remain authoritative. Regisseur reads, writes, and records through scoped provider contracts.
| Category | Provider choices | Control point | Operational use |
|---|---|---|---|
| SMTP default · Microsoft Graph · SendGrid | Credentials tested per workspace | Invitation and notification delivery | |
| Messaging | Twilio · REST gateway | Signed outbound calls | External party nudges and confirmations |
| Signing | DocuSeal default · DocuSign option | Token-gated embedded signing | Policy issue and signed PDF capture |
| Error reporting | Sentry · GlitchTip · NoOp in dev | Workspace-selected resolver | Operational evidence and incident triage |
A policy-issue step creates an envelope and marks the node awaiting signature.
DocuSeal runs in-stack by default; DocuSign can be selected when a customer requires it.
The signer receives a single-purpose link. No platform account or user JWT required.
Completion stores the signed PDF, updates envelope state, and advances the workflow.
A line of business is a package of process templates, agents, forms, documents, and tools — promoted without hand-rekeying.
Operators dry-run a bundle, inspect import states, resolve conflicts explicitly, and install new versions without mutating history. In-flight work stays pinned to the versions it started with.
We will walk through providers, credential testing, signing, bundle promotion, and the UAT path needed before a live carrier demo.