PM Delivery Execution

PM customer delivery execution now has an admitted orchestration route.

This route orchestrates one bounded customer-facing delivery execution packet against the governed mutation seam while keeping finance output, source writeback, and customer billing delivery explicitly blocked.

Promoted route
/pm-review/customer-delivery-execution
Mutation seam route
/api/v1/mutations/temp-power-customer-delivery-events
Status readback
/api/v1/reads/temp-power-customer-delivery-event-status

Customer Delivery Execution Orchestration

The orchestration surface collects current lineage ids, bounded recipient proof, and one admitted delivery execution request. It does not widen into finance output, source writeback, or customer billing delivery.

Return to PM driversProject overviewOpen PM workfront

Guardrails

Allowed delivery channels: CONTROLLED_EMAIL, LATER_APPROVED_PORTAL.

Allowed execution methods: CONTROLLED_EMAIL_OPERATOR_SEND, LATER_APPROVED_PORTAL_OPERATOR_RELEASE.

Boundaries remain blocked: finance export, source writeback, customer billing delivery.

Execution request

This admitted route sends one bounded seam request using the current PM actor token.

Mutation result

{
  "status": "not_run"
}

Delivery event readback

Loading current customer delivery event status...