Weekly source to connector review
An approved weekly text variant can be prepared as one canonical connector draft. On the Social connectors panel, select the bound account, source week and approved variant, inspect the revision/copy/account, then choose Prepare for review. Reload retains the operation and its source provenance in the existing review queue. Weekly approval never approves the connector operation. Existing human approval and dispatch remain separate actions.
POST /v1/orgs/:orgId/projects/:projectId/social-connectors/week-handoffs accepts exactly operationId, weekId, postId, channelId, expectedRevision and bindingId. social_connector_prepare_week invokes this same route through canonical MCP internal HTTP. Neither accepts copy, platform or account as caller authority. Status/readback tools retain their existing behavior.
Preparation checks the canonical 21-slot parent, completed child and supplied producer receipts, current project/org authority, exact current revision, approved channel, supported text-only publish capability and exact selected account. The weekly x platform maps to connector twitter; other platforms must match literally. Media-bearing and media-required variants remain HELD. Separate hashtags remain HELD because this slice has no canonical serialization combining them with connector text; put the exact intended inline copy through weekly review instead. Whitespace requiring connector trimming is also held rather than silently changed. Proposed weekly times are bound into the revision but never become a connector schedule.
One org/project/post/channel/revision has one review operation across all weeks, credentials, operation IDs and connector bindings. A new operation requires a newly edited and approved source revision. The API does not create a second operation to retry a missing receipt, cancelled operation or changed credential. Use the original operation for readback/reconciliation. Operation identity also binds the actual delegated principal and binding generation/account/provider. Reusing an ID with different input or principal conflicts.
The existing operation row and versioned audit receipt commit atomically. A reserved publish conversationId marker preserves the source fence when provenance is partial or missing. It is internal metadata and is never passed as a provider conversation. Receipt damage is UNKNOWN, disables approval/dispatch, and cannot create a replacement. Non-handoff operation behavior, UNKNOWN/executing account fence and hourly limits remain unchanged.
Human approval and execution re-read the receipt, binding and canonical source under the existing connector binding lock and producer row locks. Creator role loss, key revocation/pause/expiry/resource/ceiling changes, Stop, account generation changes and source edits block future effects. Execute also retains the existing current human approval-actor permission check. The existing durable execution claim remains the final effect boundary; this slice does not redesign races after that claim or the provider executor.
Preparation admits sessions and current ordinary user-custody org keys within existing outreach preparation policy. Runner/user-scoped keys are refused. User tokens, token-derived keys and service-custody principals remain HELD pending maintained parent-chain admission; no human createdBy substitution is used to admit those principals. Keys cannot approve or execute. No model, generation, account discovery, timer, schedule, tool execution or external publication occurs during preparation.
Root authorized the exact three-hunk parent composition on 2026-10-20: the shared auth plugin now registers preparation in the outreach key family and OUTREACH_DARK_ROUTES, retaining early 404 behavior when either outreach flag is disabled. The existing MCP discovery assertion includes the preparation tool. REST and MCP preparation use the mounted canonical route; keys still cannot approve or execute. The maintained MCP registrar exposes outreach tools for org credentials with both outreach flags enabled; platform-admin sessions have no org context in that catalog. The task-local root-registration.patch retains the exact authorized parent patch for audit.
This is a weekly-to-review handoff. Generic deterministic workflow-node execution, real provider credentials, actual vendor scope verification and qualified relay ingress remain separate prerequisites.