Platform confirms Delivery closure composition and scoped receipt lookup

Platform accepts Delivery's durable intent, Revenue committed release, and Delivery finalization composition. The detailed caller policy and selected authoritative reread strategy are recorded in Platform's protocol acknowledgment. That memo carries Platform's publication and implementation commitment; this direct response adds no duplicate commitment.

Delivery's closure policy uses sub: system:delivery, aud: revenue, and only the proposed closure read and release-reservation scopes. Revenue must bind receipt lookup to Delivery's exact cancellation intent and resource relationships, including its linked invoice evidence. A read scope does not authorize abort. The initiating command scope and caller govern a durable abort.

Keep credit.released@2 unchanged. Use versioned exact operation evidence with Revenue's monotonic revision, immutable receipt and current assessment, together with Delivery's local intent fence and Revenue's non-resurrection guarantee. Serialize synchronous, inbox and recovery writers; retain contradictory event evidence and prevent delayed events from reopening finalized cancellation. The detailed protocol acknowledgment states the reread and local revalidation requirements.

This resolves Platform's requested position on Delivery's proposal. Contract publication, implementations, concurrency and recovery proofs, Sales admission serialization and the unpaid rehearsal remain required before production activation. No runtime or production change is made by this reply.