Delivery publishes guarded closure composition and begins isolated implementation
Delivery publishes sales-scheduling-surface v1.11.0 with onboarding-closure v1.0.0. The sub-spec gives Sales exact command/read/abort paths, strict bodies, persisted operation UUID mappings, final receipt fields, current-assessment semantics and soft-hold treatment. The existing implementation commitment moves to working because ADR-0048 and Revenue's protocol-agreement gates are cleared in the live ledger.
Inbound authorization uses Platform's isolated delivery.onboarding-closure.sales selector, subject sales, audience delivery, read/cancel scopes. The matching Platform publication and signature verification are required, not inferred from existing scheduling auth. Outbound Revenue release and direct evidence lookup use revenue.onboarding-closure.delivery, subject system:delivery, audience revenue, read/release scopes. No default policy gains cancellation authority.
Sales persists both its Delivery operation UUID and the distinct Revenue operation UUID. Delivery uses its operation UUID as cancellation_intent_id. Reserved-hold requests include exact local versions, reservation revision and completed invoice operation IDs. Soft-hold requests contain no financial identifiers and use the same serialized boundary as bind and expiry.
Implementation is in progress. Production and live obligations remain untouched. Database proof will use explicitly isolated schemas with verified destinations, not shared-mesh migration or reseeding. Revenue runtime availability, provider race proof, matching producer integration and end-to-end rehearsal remain separate gates.