Platform acknowledges ADR-0046 and confirms existing exact correction scopes
Platform position
Platform acknowledges ADR-0046. The proposed flow preserves the required ownership split. Delivery owns the selected Lesson Type, effective duration and expected credit-cost snapshot, operator confirmation, terminal lesson outcome, and durable finalization retry. Revenue owns the active reservation transition, immutable original debit, append-only charge difference, balance and coverage checks, recognition treatment, durable correction identity, and financial replay result.
The known mismatch must fail closed before Delivery terminalizes. Revenue apply must succeed before Delivery writes its effective completion facts, and a detected mismatch must never fall back to the existing unpriced completion command.
Exact workload authorization
No workload-policy or Platform code change is required. The additive correction_kind: completion_charge mode uses the existing guarded correction endpoints and the existing delivery-production-to-revenue-v1 policy with exactly these operation scopes:
revenue.lesson-outcome-corrections.previewrevenue.lesson-outcome-corrections.apply
The request discriminator does not create a new operation or broaden Delivery to generic Revenue write authority. The policy remains fixed to sub: system:delivery, aud: revenue, tenant tnt_sguild, canonical Organization reach, a five-minute lifetime, and its code-owned exact scope set. Revenue remains responsible for exact route, subject, scope, tenant, Organization, lesson, reservation, correction identity, request semantics, preview freshness, blocker, and idempotency enforcement.
The separate revenue.lesson-outcome-corrections.balance-reconcile capability remains isolated and unchanged. Delivery may select it only for the existing ADR-0040 sole-blocker recovery flow. ADR-0046 does not grant that mutation as part of preview or apply.
Contract and event publication decision
After ADR-0046 is Accepted, Platform will publish an additive Credit Reservation Lock v3.2.0 amendment and advance the Lesson Outcome Correction API sub-spec to v1.1.0. The amendment will ratify completion_charge, its required pre-terminal request facts, preview response semantics, serializable apply and replay rules, Delivery pending-finalization boundary, blockers, and rollout proof requirements. The proposed section is suitable as the basis for that publication.
No new event type, payload version, or registry entry is required. Revenue continues to emit credit.consumed v1 for the active-to-consumed reservation transition. Its consumed_credits field remains the positive quantity posted as the immutable original Lesson Debit, which is the original reservation quantity in this branch. It is not the net effective charge after the same-transaction non-reversal adjustment. The v3.2.0 amendment will make that distinction explicit so event consumers do not reinterpret credit.consumed as a standalone effective-charge fact. Effective financial charge remains derived from Revenue ledger and recognition facts or the guarded apply result.
Delivery's normal terminal lesson event remains the lifecycle evidence for the effective Lesson Type and duration after finalization. Preview, blocked, failed, stale, and pending-finalization attempts do not require a new Platform registry surface.
Remaining gates
This memo clears Platform's ADR acknowledgment and workload-policy decision. It does not make the proposed contract section authoritative, accept ADR-0046 by itself, authorize Revenue deployment, enable Delivery's permanent UI, or claim end-to-end production proof. Finance still owns its recognition acknowledgment, the named ADR deciders own the Accepted transition after all required acknowledgments, and Revenue and Delivery retain their implementation, deployment, recovery, and controlled live-proof responsibilities.
References
adrs/ADR-0046-guarded-lesson-completion-charge-adjustments.mdcontracts/credit-reservation-lock/README.mdcontracts/credit-reservation-lock/lesson-outcome-correction-api-proposal.mdcontracts/service-auth/README.mdmemos/2026/2026-08-18-revenue-adr-0046-implementation-ready.mdmemos/2026/2026-08-18-delivery-adr-0046-ack-and-fail-closed-slice.md