§ Integrations & StandardsDocument · REG-INT-2026.04

Regisseur deploys above your existing stack.

Every external interaction flows through a registered, workspace-scoped tool or provider: revocable, testable, and audited at the call site.

§ 01 — Integration primitives

Any system of record. Bounded by MCP.

System of record

Read where it lives

No shadow repository

Regisseur reads documents, records, tickets, and work items through registered tools. Source systems stay authoritative.

Every retrieval is an audited MCP call; every token is workspace-scoped and revocable.

ProtocolMCP · service token

ScopeWorkspace · object-level

RevocationIndependent

AuditPer-call · ledgered

Structured intake

Typed payloads

Native mappings

Regisseur normalizes domain payloads into typed work attributes for downstream steps.

Payload lineage is preserved end-to-end — every derived value links back to its source field.

IngestNative

MappingTyped attributes

LineageEnd-to-end

Decision rules

Policy gates

Runtime-enforced

Domain rules compile into process gates. Violations fail closed and cite the blocking criterion.

Rules are versioned — in-flight work finishes on the rule set that was live when the work started.

EnforcementEngine-level

VersioningSCD Type 2

ReplayByte-identical

§ 02 — MCP registry

Zero-trust external access. Registered, scoped, revocable.

workspace · operations · mcp registry7 servers · 16 tools · all workspace-scoped

Server	Purpose	Scope	Auth	Status
document.system	Workspace document retrieval	Workspace · read	Service token · rotated 30d	Live
structured.intake	Typed intake payload ingestion	Workspace · write	Mutual TLS	Live
rules.engine	Domain rule lookup and validation	Org · read · versioned	Service token	Live
calculation.service	Scored recommendations and calculations	Workspace · read	Service token	Live
twilio.outbound	Tokenized SMS to external parties	Workspace · write · signed	Signature verification	Live
signing.provider	Embedded signing envelopes and PDFs	Workspace · write	Provider credential	Live
system.writeback	Approved outcome writeback	Workspace · write	Service token · 2-factor	Staging

Every MCP call is logged with arguments, result hash, trace_id, and policy decision. Agents cannot invoke servers not registered in the workspace.

§ 03 — Workspace providers

Outbound systems are configuration, not code forks.

Mail

SMTP default · Microsoft Graph · SendGrid

Invitations, follow-ups, and signing links use the workspace-selected mail path.

Test connection

Messaging

Twilio · REST gateway

SMS and gateway delivery stay bounded by a provider contract and signed outbound call model.

Test connection

Signing

DocuSeal default · DocuSign option

Embedded signing creates an auditable pause and resumes the workflow on completion.

Test connection

Error reporting

Sentry · GlitchTip

Operational evidence can route to the customer-approved reporting provider.

Test connection

§ 04 — Systems of record

Unchanged. Unmoved. Undisturbed.

Systems of record, document stores, CRMs, ticketing queues, billing systems, and data warehouses stay put.

Regisseur reads what it needs, writes what it’s allowed, and leaves the rest alone. Domain experts update Tier 2 agent logic; the Tier 1 engine stays locked; Tier 3 packages carry domain rules.

§ Next step

Map your stack to Regisseur in 30 minutes.

Bring one process, the systems it touches, provider requirements, and the review gates that keep it safe. We’ll sketch the MCP registry, the provider layer, the autonomy ceilings, and the first workflow you could run by week four.

Book the mapping session →Read the governance model

Boundary

MCP-bounded tools

Standard

Typed payloads

Floor

Runtime policy gates

Time to live

Weeks, not months