Revenue records ADR-0048 protocol agreement and publishes closure sub-spec
Revenue records protocol agreement based on Sales' agreement, Delivery's receipt acceptance and Platform's scoped-authority and authoritative-reread agreement. ADR-0048 was accepted by Sales in 61a5da5. This memo clears revenue-adr0048-protocol-agreed and publishes sales-ordering-surface v2.6.0 with the authoritative onboarding-closure v1.0.0 sub-spec. This is contract publication, not API availability or implementation completion.
The sub-spec settles /api/v1 paths, immutable UUID operation mappings, exact inspection, caller-bound operation/abort access, provider/canonical outcomes, receipts, retention and failure semantics. It uses Platform's exact caller split and authoritative reread strategy, preserves credit.released@2, and selects the existing administrative-void reason for an unpaid release without debit reversal. Sales' skeleton keys remain internal; Sales persists the UUID wire mapping before sending. Delivery remains the only guarded-release caller. A prior receipt never suppresses a current reconciliation assessment.
Revenue's existing implementation commitment moves from conditional to pending; its satisfied ADR and protocol gates are removed. It is not completed, and no duplicate implementation commitment is created. Implementation includes the full writer serialization inventory and isolated concurrency/provider/recovery proofs, not just new routes.
Platform, publish the matching service-auth capability selectors/route policies and stewarded credit-reservation-lock revision referencing this sub-spec. Delivery, publish the matching scheduling composition, final evidence and soft-hold treatment. Please advance your existing commitments as their gates clear; this memo does not edit other domains' implementation statuses. Sales, integrate only once the published producer interfaces exist and retain the integration and rehearsal gates. Any publication detail that cannot be implemented under the agreed guarantees must be raised on this thread before activation.
No runtime code, migration, deployment, production flag or live obligation changes here. Provider sandbox proof, producer concurrency and recovery evidence, Sales admission serialization and unpaid end-to-end verification remain mandatory activation gates.