0044. Send approval is optional per workspace and off by default, with pause and rollback
- Status: Proposed. The sections “Approval is optional per workspace” and “Also decided by the maintainer” are Accepted: the maintainer decided them on 2026-11-18, and they are not reopened.
- Date: 2026-11-18
- Amends: ADR 0033 (approval is no longer always on), ADR 0016 (no activation confirmation where approval is off), ADR 0005 (the server-side confirmation of sending actions applies only where approval is required), ADR 0011 (a new
waitingreason), ADR 0017 (pause and rollback next to stop), ADR 0026 (who may pause), ADR 0031 and ADR 0041 (Proposed; approvers matter only where approval is required) - Depends on: ADR 0041 (Proposed) for the owner’s session that changes the setting. Until it is built, the operator changes it (see “Changing the setting”).
Context
Section titled “Context”ADR 0033 makes every sending workflow version wait for a person to open a mailed link before it goes live. The link reaches the approver’s mailbox, a channel the API credential does not give, so the user’s own AI cannot approve its own change.
The product is for an indie developer working alone (ADR 0014). That developer is the only approver, and their AI makes most edits. Every edit of a live sending workflow costs them a mail and a click to approve a change they asked for a moment earlier. ADR 0033 accepted that friction. In use it is the main cost of the product’s main path, and a person who approves every mail by reflex is not a strong check either. Teams, where the person who asks for a change is not the person who approves it, still want approval.
Facts about the code at 9d08d1a:
- Send approval is built (plan rows A1 to A4b, A6):
workflows.activate,sendApprovals.get, the view and decision endpoints,responseandemaildelivery, and approvers in the control plane. The executor contract suitetesting/contracts/src/send-approvals.tscovers it. Other suites go live through the helperapproveLatestVersionincore/testing. - There is no
workflows.stop(ADR 0017), no pause, and no way to go back to an earlier live version. The operator’s kill switches (ADR 0011, ADR 0024) are not built. The interim emergency stop is the operator deleting a workspace’s sending domains. waiting:plan_limit, its return toqueued, its 72-hour skip, and the budget reservation inclaimSendare designed in ADR 0011 and ADR 0013 but not built: the due work of a waiting message only clears its deadline, and a message has no record of when it first enteredwaiting. Pause (below) is the firstwaitingreason that is built.claimSendchecks, in order: the run is not stopped (isRunStopped, a pure function of the workflow and run records), the customer is eligible (unsubscribe, suppression), and the sender is verified. Each failure is a finalskipped.workflows.activateis annotateddestructive: false, and its output’ssendApprovalis required and nullable (null when the workflow went live without an approval).- Nothing records who made a version live. The decider on a send approval is the only such record. The audit log is not built.
- Only project keys exist. Users, roles, sessions on
apiactions, and MCP grants come with ADR 0040 and ADR 0041 (Proposed). - No invariant of ADR 0007 mentions approval. Approval came from ADR 0005’s “sending actions require user confirmation”, resolved by ADR 0033.
Decision
Section titled “Decision”Approval is optional per workspace
Section titled “Approval is optional per workspace”Decided by the maintainer on 2026-11-18. This section is Accepted.
- Each workspace has the setting
sendApprovalRequired: on or off. It is off by default, for every new workspace and every existing one. - When it is on, ADR 0033 applies unchanged: a sending version goes live only after an approver approves it through a mailed link.
- When it is off, a sending version goes live when
workflows.activateis called, with no approval and no mail. - Reason: the target user works alone. Approving every edit their own AI makes is friction without a second person’s judgement. Teams can turn it on.
- Pause and rollback are part of the decision: that they exist is Accepted, while their design in the sections below is Proposed. They make a bad change cheap to stop and undo once it is live, in place of preventing it before it is live.
Also decided by the maintainer
Section titled “Also decided by the maintainer”Decided on 2026-11-18, after review of this ADR. This section is Accepted.
- No notification when approval is turned off. The workspace’s other owners and admins are not mailed. The change is recorded (below).
- No send cap after an unapproved change. A cap on the sends of a version that went live without approval was proposed and rejected. Plan limits and sender protection bound volume (see “What approval off exposes”).
- Rollback follows the setting. Where approval is on, a rollback needs an approval like any other change of the live version, as ADR 0033 requires. Where it is off, it needs none. Pause, which needs no approval in either mode, is the emergency path.
The setting
Section titled “The setting”- It is stored on the workspace in the control plane:
workspaces.send_approval_required(default false). Each change also appends a row tosend_approval_setting_changes(workspace, new value, principal reference, time) in the same statement batch, so every change is kept, not only the last, until the audit log exists. - It is per workspace, not per project or per workflow, because approvers are per workspace (ADR 0033, ADR 0041).
- The default is the same on the managed service and on self-hosted installations: off. The cloud mode adds no other default and refuses nothing about it. There is no deployment-wide switch that forces it on; a self-hoster who wants it on turns it on for each workspace. A deployment-wide default is revisited if self-hosters ask for one.
- It governs the approval of workflow versions, of rollbacks, and of the template versions they reference once templates are their own resources. It does not change test sends, which go only to verified test recipients in either mode.
- Sends to a recipient chosen at call time (a transactional send API, still open) follow the same setting: ADR 0033’s approved template is required only where approval is on. Such a send reaches any address with any content, so its abuse controls are decided in the transactional send API’s ADR, not by this setting.
Changing the setting
Section titled “Changing the setting”workspaces.setSendApproval{ required: boolean }is anapiaction withprincipal: "user",target: "workspace", and roleowner(ADR 0041). It returns the workspace’s setting. Calling it with the current value changes nothing and returns the setting (idempotent).- Only an owner’s session can call it, in either direction. A project key and an MCP grant answer
forbidden, even withadmin, and even when the grant’s user is an owner. A grant acts as its user, and the user’s AI holds the grant, so the AI could otherwise turn off the check that exists to hold it back. Turning approval on is harmless, but one rule for both directions is simpler and leaves the AI nothing to toggle. - It stays an MCP tool and answers
forbiddenthere, as ADR 0041 decides for everyuser-only action. - An owner, not an admin, because the setting decides whether admins’ approval counts at all, so it sits above what admins manage, with the other powers ADR 0026 reserves to owners (billing, the workspace itself, sending domains, managing admins).
- Until ADR 0041’s session principal is built, the operator sets it through an operator endpoint,
PUT /operator/workspaces/:workspaceId/send-approvalwith{ "required": boolean }, in the manner of ADR 0035 and of the approvers endpoint of ADR 0033. It is retired in the change that buildsworkspaces.setSendApproval, together with the approvers endpoint that ADR 0041 retires. sending.get(below) reports the setting to any caller withread, so the AI can tell the user whether a change will need approval.
Amendment (2026-11-19, ADR 0041, Accepted): there is no owner role. workspaces.setSendApproval needs role admin and stays principal: "user", so only an admin’s session changes the setting, in either direction. The bullet above that puts it with owners rather than admins is replaced: any admin can turn approval off for the other admins, which is the maintainer’s accepted trade-off for small teams (ADR 0041, Roles). Row P5’s tests become: an admin’s session changes the setting in both directions; a member’s session answers forbidden; a project key and an MCP grant answer forbidden in both directions, on REST and MCP, even with admin and even when the grant’s user is an admin; the change records its user. Elsewhere in this ADR, including the header’s “owner’s session”, the Accepted “no notification” item, and row P5’s title, read owner as admin.
Activation in each mode
Section titled “Activation in each mode”workflows.activate’s handler reads the setting first, through its own ControlStore read, sendApprovalRequired(workspaceId). It is separate from the ApprovalRecipients source of SendApprovalDeps, which still chooses who gets links and is called only when the setting is on.
| Setting | Latest version | Result |
|---|---|---|
| either | not sending | activated or published at once, as today |
| on | sending | ADR 0033: a pending send approval and links; no_approvers and the daily mail cap apply |
| off | sending | activated or published at once, after the sender check |
- With the setting off, the sender check of ADR 0034 still applies: a
fromaddress outside the workspace’s verified sending domains is refused withsender_not_verified. That check is sender protection, not approval.no_approversandrate_limited(the approval mail cap) do not apply, and the recipients are not read. SEND_APPROVAL_DELIVERYonly decides how links reach approvers where the setting is on. On a self-hosted installation withresponsedelivery, the setting on returns thecallerlink inapprovalLinkas today, and the setting off returns no link and goes live. The cloud mode still refusesresponse.- The output schema is the same in both modes. With the setting off,
sendApprovalis null andapprovalLinkabsent, and the returned workflow shows the new live version. workflows.activate,workflows.rollback,workflows.resume, andsending.resumeare annotateddestructive: true, because each can start real mail or change what is sent. MCP clients that honour annotations then ask the user before calling them. That is a hint a client may ignore, not a server-side check.destructiveis used rather thanopenWorldHintbecause it is the annotation clients use to ask for confirmation;openWorldHintonly says a tool reaches outside entities, and is still open for every tool (ADR 0031).- A change of the setting applies to requests that start after it commits. A
workflows.activatethat read the old value a moment before still completes under it. That window is one request long and is accepted, so the send path never reads the control plane.
Pending approvals when the setting changes
Section titled “Pending approvals when the setting changes”- Turned off: pending approvals stay pending. Nothing goes live because the setting changed. A pending approval can still be approved or declined through its link, with every check of ADR 0033. The next
workflows.activateorworkflows.rollbackof the workflow takes effect at once and marks that workflow’s pending approvalcancelledin the same transaction. The approval expires after 24 hours otherwise. No project store is written when the setting changes, so a workspace with several projects needs no fan-out. - Turned on: live versions stay live. No approval is asked for retroactively. The next activation, publication, or rollback of a sending workflow needs an approval. Runs already started are not affected.
Who changed what: the record
Section titled “Who changed what: the record”Versions stay immutable, and each change of what is live is recorded. Both hold in either mode.
- A principal reference names who made a change:
{ kind, id }, wherekindis one of:project_key: the key’s ID, never the key;user: a session’s user ID;grant: the MCP grant’s ID (its user is on the grant);approver: the deciding approver’s ID, for a change made by an approval;operator: an operator endpoint.
core/authalready knows the principal, and passes its reference to the command with the scope.- A live change is one append-only row in the project store, written in the transaction that makes the change: the workflow (null for a pause or resume of the whole project), the kind (
activated,published,rolled_back,paused,resumed, andstoppedonce stop exists), the live version before and after, the activation epoch, the principal reference, the send approval’s ID when an approval made it, and the time. Who saved a version is not recorded separately: a version matters only once it goes live, and the live change records who made it live. - Live changes are behaviour state, not only history: rollback reads them to find its target. They are indexed by
(workflow, epoch), and they are exempt from retention and pruning while their epoch is the workflow’s current one. When the audit log exists, each live change and each change of the setting is also written to it through the outbox, idempotent on the row’s ID; that copy is never read back as the source. liveChanges.list{ workflowId?, limit?, cursor? }(anapiaction, scoperead, rolemember) returns the project’s live changes, newest first, or one workflow’s withworkflowId(a project pause or resume is listed with every workflow’s changes). It is how the user and their AI see what went live or was paused, when, and by whom, and what a rollback would restore.
Pause and resume
Section titled “Pause and resume”A pause holds sending without losing anything: runs keep running, and their send steps wait.
workflows.pause{ id }andworkflows.resume{ id }act on one workflow.sending.pause{}andsending.resume{}act on all sending of the project.sending.get{}returns the project’s sending status: whether its sending is paused, by whom and since when, and the workspace’ssendApprovalRequired.- The pause state is stored in the project store (on the workflow record, and in one project row), so
claimSendchecks it in its own transaction and never reads the control plane. - A workflow in any status can be paused,
draftandstoppedincluded. A pause is cleared only by resume: activation, publishing, rollback, and stop leave it as it is, so a workflow paused as a draft and then activated stays paused. - While a workflow or its project is paused:
- triggers still start runs, and runs still advance through delays and conditions. New runs are not stopped; this is revisited if held backlogs prove a problem in use;
claimSendkeeps its order and adds the pause check last: the run is not stopped (including a withdrawn version, below), the customer is eligible, the sender is verified, and then, if the workflow or project is paused, the message moves towaiting:pausedinstead of being claimed. The final skips come first, so a held message is one that would otherwise be sent. The check comes before the budget reservation, so nothing is reserved or billed;- outbound webhook deliveries are held in the same way when the webhook step is built.
- A message records when it first entered
waiting(first_waiting_at, new state on messages, shared withwaiting:plan_limitwhen that is built). It is set once and never reset, so a pause, resume, and pause again does not restart the 72-hour window. 72 hours after it, a message still waiting for a pause becomesskipped:paused, likewaiting:plan_limit(ADR 0011), so a long pause does not release stale mail later. - Resume moves the workflow’s or project’s
waiting:pausedmessages back toqueued, in bounded batches through the wake mechanism, using an index on messages by(state, reason, workflow). Each batch checks the pause state again first, so a pause after a resume stops the remaining batches. Each released message is rechecked byclaimSendas usual. A message still paused by the other level (a resumed workflow in a paused project) waits again. A resume of a large backlog arrives as a burst; the deliveries queue’s concurrency and rate limit (an item of B4’s deploy gate) bound it. - Who may call them:
| Action | Scope | Role (ADR 0041) | Annotations |
|---|---|---|---|
workflows.pause, sending.pause |
write |
member |
idempotent |
workflows.resume, sending.resume |
admin |
admin |
idempotent, destructive |
sending.get, liveChanges.list |
read |
member |
read-only |
Pausing is the safe direction, so anyone who may edit may pause, the user’s AI included: an assistant that notices its mistake should be able to stop the mail at once. Resuming releases held mail, which is the same effect as making a version live, so it needs admin, as activation does (ADR 0026). Resume needs no approval in either mode, because the content of the live version does not change.
- A pause is the user’s control. The operator’s global and per-workspace kill switches of ADR 0011 and ADR 0024 stay separate, still skip rather than hold, and are still open.
- Stop (ADR 0017) stays the way to discard: it cancels waiting runs and skips queued and waiting messages,
waiting:pausedincluded.
Rollback
Section titled “Rollback”workflows.rollback { id } (scope admin, role admin, annotations destructive) makes the previous live version live again and withdraws the current one.
- Only an
activeworkflow can be rolled back; any other status answersconflict. - Target: the most recent version that was live in the current activation epoch and is neither the current live version nor withdrawn, read from the live changes. If there is none (after the first activation of an epoch, or once every earlier version of the epoch is withdrawn), rollback answers
conflict, and the user pauses or stops instead. So after v1, v2, and a rollback to v1, a second rollback answersconflict. - Approval follows the setting. With the setting off, the rollback takes effect at once, in one project-store transaction. With it on, the rollback creates a pending send approval of the kind
rollback, and takes effect when it is approved. Pausing the workflow stops its mail meanwhile. - Approval kinds. A send approval gains a kind:
activation(ADR 0033’s approval, for activating or publishing the latest version) orrollback.- A
rollbackapproval binds the target version and its definition hash, the re-entry policy, and the live version it rolls back from. - Its decision checks again that the workflow is
activein the same activation epoch, that the live version is still the one rolled back from, that the re-entry policy is unchanged, and that the target is not withdrawn; otherwise it is refused withconflict. Those are its only bound-value checks. - Saving a new latest version does not supersede it: a rollback restores an earlier version, not the latest, so the latest version is not one of its bound values. The derived
supersededstatus of ADR 0033 (the latest version is no longer the approval’s version) applies toactivationapprovals only. - The approval page and the approval mail say “rollback from vN to vM”, and show the target version’s content.
- A
- At most one pending approval per workflow, whatever its kind. A request of the other kind cancels the pending one; a repeated request of the same kind reuses it and sends new links, as activation does today. So requesting a rollback cancels a pending activation approval, and requesting an activation cancels a pending rollback approval. Cancelling an activation approval for a rollback is intended: it is the safe direction, back to a version that was already live, and the activation can be requested again.
- Effect on the restored version: it becomes live, like publishing: the status and the activation epoch do not change, and runs pinned to it keep running. Pending time-trigger fires follow the version-change rule of ADR 0016 and ADR 0017, as on any publication. No sender check runs at rollback: if a
fromdomain of the restored version was removed since, its sends are skipped withskipped:sender_not_verifiedbyclaimSend. - Effect on the withdrawn version: the version the rollback moves away from is added to the workflow record’s
withdrawnVersionsset. Versions stay immutable, andisRunStoppedstays a pure function of the workflow and run records: a run whose version is in the set is stopped. It gains a variant that returns the reason (workflow_stoppedorversion_withdrawn), sotickandclaimSendwrite the right one. Waiting runs exit withexited:version_withdrawn, and itsqueuedandwaitingmessages becomeskipped:version_withdrawn. The check makes this immediate; bounded batches clean up the rows, as for stop. Messages insending,unknown, oracceptedfollow the send state machine. This is the point of the rollback: the bad version stops sending, and the earlier version’s runs (for example a drip sequence in a three-day delay) are untouched, unlike a stop followed by a reactivation, which would stop both. - Entry markers stay. Under the re-entry policy
once, a customer who entered on the withdrawn version keeps the entry marker of ADR 0017, so they do not enter the restored version either.oncemeans once per workflow, whatever version; a rollback does not undo an entry. - A withdrawn version never goes live again.
workflows.activateon a workflow whose latest version is withdrawn answersconflictwith the reasonversion_withdrawn;conflictis added toworkflows.activate’s errors. Saving a new version, even with the same definition, makes a new number that can be activated.
What approval off exposes
Section titled “What approval off exposes”- With the setting off, a leaked key with
admin(or a grant withadminheld by an admin) can send any content to any address from the workspace’s verified domains: it upserts customers with any address, saves and activates a workflow, and tracks the trigger event. ADR 0033’s approval was the barrier against that. - Pause, rollback, and the live-change record are reactive only. They stop and expose the damage after mail has gone out; they prevent none of it.
- What bounds the volume before anyone reacts is the workspace’s plan-limit budget (ADR 0013) and the per-tenant sender protection of ADR 0024 (auto-pause on bounce and complaint rates). Neither is built yet. So on the managed service no workspace with approval off sends real mail until both are built, and until pause and rollback are built; these are items of B4’s deploy gate. This adds no new cap.
Interaction with the core invariants
Section titled “Interaction with the core invariants”None of the six invariants of ADR 0007 mentions approval, so making approval optional changes none of them.
- Versioned workflow definitions: still hold. Versions are never changed. Saving never changes the live version or a started run. Rollback edits no definition: it switches the live version to an existing one and stops the withdrawn version’s runs, as stop does for all of a workflow’s runs.
- Pre-send recheck: a message released by resume passes the full
claimSendrecheck. - Idempotency and unknown outcomes: a message moves between
queuedandwaiting:pausedonly before it is claimed. Pause, resume, and rollback never touch a message insendingorunknown, so none can cause a resend. - Tenant isolation: every new action is a
projectaction throughProjectScope, exceptworkspaces.setSendApproval(WorkspaceScope, ADR 0041). Each gets its isolation case. - Secrets: principal references hold IDs only, never a key, secret, or address (ADR 0032).
Implementation plan
Section titled “Implementation plan”Nothing is built by this ADR. Each row starts with the failing tests named and leaves main working. The order is P2, P3, P4, then P1, so no build turns approval off by default without pause and rollback. Until P1 lands, the setting does not exist and is treated as on, which matches what is built: every sending change needs an approval. Nothing sends real mail yet; B4’s deploy gate holds back real mail from any workspace with approval off until pause, rollback, the plan-limit budget, and ADR 0024’s protection are built.
| Row | Builds | Failing tests first |
|---|---|---|
P2 feat: record who made each version live |
workflow_live_changes in the project store, indexed by (workflow, epoch) and exempt from pruning in the current epoch; the principal reference carried from core/auth to commands (the key’s ID for a project key); liveChanges.list |
each activation, publication, and approval writes exactly one live change in its transaction, with the principal (project_key with the key’s ID, or approver with the deciding approver’s ID and the approval’s ID in its own field); a command whose transaction aborts writes none; no response or log holds a key or an address; the isolation case of liveChanges.list |
P3 feat: pause and resume sending per workflow and per project |
the pause state on workflow records and projects; first_waiting_at on messages; waiting:paused and skipped:paused, with the first built return from waiting and 72-hour skip (shared with waiting:plan_limit when that is built); the pause check last in claimSend, before the budget reservation; resume in bounded batches over an index on messages by (state, reason, workflow); workflows.pause, workflows.resume, sending.pause, sending.resume, sending.get (with sendApprovalRequired, true until P1) |
a paused workflow’s run reaches its send step and the message waits, with nothing reserved or billed; resume sends it once after the recheck, and an unsubscribe during the pause skips it; order in claimSend: a paused message of an unsubscribed customer or an unverified sender is skipped with that reason, not held; a project pause holds every workflow; a resumed workflow in a paused project still waits; 72 hours after first waiting, skipped:paused, and pause, resume, and pause again does not reset that window; a pause between two resume batches leaves the rest waiting; pausing a draft workflow and then activating it leaves it paused (and a stopped one once stop exists); a message in sending or unknown is untouched; pause and resume are idempotent and write one live change each, with a null workflow for the project’s; both resumes are annotated destructive on MCP; a key with write but not admin can pause but not resume; stop skips waiting:paused messages once stop exists |
P4 feat: roll back a workflow to its previous live version |
withdrawnVersions on the workflow record; isRunStopped (core/src/engine/run.ts) treats a run of a withdrawn version as stopped; workflows.rollback, annotated destructive, through a rollback approval (the only path until P1; the path that takes effect at once is behind the setting, which P1 adds); the approval kind (activation or rollback), whose migration sets kind = activation on existing approval rows, with superseded derived for activation only, and the page and mail text “rollback from vN to vM”; isRunStopped’s reason-returning variant; conflict added to workflows.activate’s errors for a withdrawn latest version |
until P1, a rollback goes through approval: it creates a pending rollback approval and changes nothing until it is approved; once approved, after v1 then v2 went live, v1 is live with the epoch unchanged; v2’s waiting runs exit with exited:version_withdrawn and its queued messages are skipped; v1’s runs started before v2 keep running and sending; rollback after a first activation, a second rollback in a row, and a rollback of a workflow that is not active answer conflict; activating a withdrawn latest version answers conflict and saving a new version makes it activatable; saving a new version does not refuse a pending rollback approval, and a change of the live version does; requesting a rollback cancels a pending activation approval and the reverse; rollback writes one live change; under once, a customer who entered on the withdrawn version does not enter the restored one; a restored version whose from domain was removed sends nothing (skipped:sender_not_verified) |
P1 feat: make send approval optional per workspace, off by default |
the setting, exposing the paths that take effect at once; workspaces.send_approval_required in the control plane (migration; existing workspaces get false) and send_approval_setting_changes; ControlStore.sendApprovalRequired(workspaceId); the workflows.activate and workflows.rollback branches; the cancellation of the workflow’s pending approval when a change takes effect directly; the operator endpoint PUT /operator/workspaces/:workspaceId/send-approval; sending.get reports the setting; workflows.activate annotated destructive, and its description and the no_approvers description say approval applies only where the workspace requires it |
with the setting off, a rollback takes effect at once and writes no approval; activating a sending version makes it live at once, mails nothing, and returns sendApproval null and no approvalLink; sender_not_verified still refuses it; a workspace with no approvers can still activate; with response delivery, the setting on returns the caller link and the setting off returns none; with the setting off, a pending approval can still be approved through its link, and a direct activation marks it cancelled; turning the setting on leaves live versions live and the next sending activation pending; the operator endpoint answers not_found for an unknown workspace; each change of the setting appends one row; workflows.activate is annotated destructive on MCP |
P5 feat: workspaces.setSendApproval for owners (after ADR 0041’s session principal is built) |
the user-only, owner-role action; retiring the operator endpoint |
an owner’s session changes the setting in both directions; an admin’s session answers forbidden; a project key and an MCP grant answer forbidden in both directions, on REST and MCP, even with admin and an owner’s grant; the change records its user |
Impact on what is built:
testing/contracts/src/send-approvals.ts: keeps every test, run with the setting on. The suite’s setup gains a way to set it (the contract harness’s control-store fake gains the setting, default off like production). A new describe block covers the setting off, with the P1 tests above.approveLatestVersionand its callers: the contractsproject-executor,operator-alerts,one-click-unsubscribe, andsend-approvalssuites; the node-sqlitesender-replicaandsend-state-machinetests;apps/workers/test/fixture.ts(the parity, isolation, and MCP workflow tests); and a test of the cloud composition root. With the default off,workflows.activatemakes the version live, and there is no pending approval to approve. Each caller either turns the setting on, where approval is the subject, or drops the helper. The parity and isolation tests keep at least one case with the setting on, so both paths ofworkflows.activateare covered on REST and MCP.workflows.activate’s handler: the setting is read before the recipients, which are read only when it is on. The output schema does not change; its description, errors, and annotation do.sendApprovals.viewandsendApprovals.decide: unchanged for activation approvals. They work on any pending approval whatever the setting. A rollback approval adds its own bound values and checks (P4).- B4’s deploy gate item “no active sending workflow exists without an approval” applies only to workspaces with the setting on, and two items are added (docs/architecture.md and the go-live runbook).
Consequences
Section titled “Consequences”- An indie developer’s AI makes a sending workflow live with one call. The checks left before mail goes out are the sender check, plan limits, sender protection (ADR 0024), the recipient cap of time triggers (ADR 0016), and the MCP client’s own confirmation of a tool annotated destructive, which a client may skip. After it goes out, the user or the AI can pause in one call and, with approval off, roll back in one call, and the live changes show who made each change.
- With the setting off, a leaked
adminkey can send any content to any address from the verified domains, and the safeguards are reactive only (see “What approval off exposes”). - With the setting off, the confirmation of ADR 0016, a preview with affected customer counts before a time-triggered workflow goes live, is gone as well: ADR 0033 had already replaced its token with approval.
workflows.preview_triggersstays a read-only preview the AI can show the user, and the per-occurrence recipient cap stays. - With the setting off, nothing on the server tells a person’s change from their AI’s. ADR 0033’s guarantee, that approval needs a channel other than the API credential, holds only for workspaces that turn it on. That trade is the maintainer’s decision.
- The AI cannot turn approval off for a workspace that turned it on: only an owner’s session can, and no key or grant reaches the action.
- New state: the setting and its change rows in the control plane; live changes; pause state and
withdrawnVersionson workflow records; the project’s pause state;first_waiting_aton messages; the kind of each send approval (activationorrollback) and a rollback approval’s from-version; and the reasonswaiting:paused,skipped:paused,exited:version_withdrawn, andskipped:version_withdrawn. - Eight new
apiactions, each with REST, MCP, OpenAPI, docs, and an isolation case (ADR 0005):workspaces.setSendApproval,workflows.pause,workflows.resume,workflows.rollback,liveChanges.list,sending.pause,sending.resume, andsending.get. - Revisited only on evidence or request: whether a pause should also stop new runs, and a deployment-wide default for self-hosters.
Amendment (2026-11-19, the maintainer’s decision that every action that can start sends is confirmed on the server even where approval is off, recorded in ADR 0050, Proposed): workflows.activate of a sending version, workflows.rollback, workflows.resume, and sending.resume first return a preview and a confirmation token and act only on the call that returns it. Where approval is off, a sending version goes live on that confirming call, without approval and without mail; where it is on, the confirming call creates the approval as before. Per ADR 0048, a live change can also be of kind concluded, and an experiment conclusion that ends a holdout needs an approval of kind conclusion where approval is required; rollback does not revert a conclusion.