Pipeline reaches external action
A policy-issue step creates an envelope and marks the node awaiting signature.
Configurable for operators.
Deployable for regulated IT.
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.
§ 02 · Local data plane
Run where the regulated data already lives.
Regisseur runtime
Web · worker · queue · ledger
Execution, audit events, work state, provider calls, and cascade resumes stay inside the deployment boundary.
↕
Local services
Postgres · storage · DocuSeal
Core data, signed documents, and default e-signature flows can run without a vendor-hosted data plane.
↕
Systems of record
DMS · policy admin · CRM
Existing systems remain authoritative. Regisseur reads, writes, and records through scoped provider contracts.
§ 03 · Provider layer
One workspace. Multiple outbound systems. One audit trail.
| 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 |
§ 04 · External actions
Signing is a pipeline pause, not a side channel.
Provider creates signer URL
DocuSeal runs in-stack by default; DocuSign can be selected when a customer requires it.
Portal token gates access
The signer receives a single-purpose link. No platform account or user JWT required.
Webhook resumes cascade
Completion stores the signed PDF, updates envelope state, and advances the workflow.
§ 05 · Vertical promotion
Verticals move as signed operational packages.
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. Bundles are signed and accepted only from trusted publishers. In-flight work stays pinned to the versions it started with; when you do promote a template change, cases migrate forward by matching completed steps (on approval, with an audit event) so a mid-case change never strands live work.
§ 06 · Day-2 operations
The un-glamorous half of enterprise software, done before you ask.
The parts nobody demos but everybody needs on day two: shipped, documented, and drilled, not promised.
§ 07 · Own it, don’t rent it
The layer that runs your work is an asset you own, not a feature you rent.
Your organization owns the configuration (process templates, agents, forms, documents, and tools) and runs it inside your own boundary. The orchestration layer is an asset you hold, not a subscription that holds your operation hostage.
McKinsey frames the build-versus-buy decision the same way: the durable advantage comes from owning the layer, not renting access to someone else’s.
§ Next step
Bring your deployment constraints.
We will map the first workspace.
We will walk through providers, credential testing, signing, bundle promotion, and the UAT path needed before a live customer demo.