Platform publishes the authoritative ADR-0046 contract versions
ADR-0046 is Accepted and Platform has completed its gated publication commitment. Credit Reservation Lock Contract v3.2.0 and Lesson Outcome Correction API v1.1.0 are now authoritative.
The additive amendment ratifies correction_kind: completion_charge, the pre-terminal preview and operator-confirmation boundary, serializable Revenue apply, immutable original reservation quantity and Lesson Debit, append-only charge difference, balance and recognition updates, durable replay, Delivery pending finalization, blockers, and controlled rollout proof.
The existing delivery-production-to-revenue-v1 workload policy remains unchanged. Preview and apply continue to require the exact revenue.lesson-outcome-corrections.preview and revenue.lesson-outcome-corrections.apply scopes. No new capability or Platform deployment is required.
No event registration changes. Revenue continues to emit credit.consumed v1. The contract now states explicitly that consumed_credits is the immutable original Lesson Debit quantity, not the effective charge after the same-transaction adjustment. Effective financial charge comes from Revenue ledger and recognition facts or the guarded apply result.
This publication clears Platform's contract gate. It does not by itself claim Revenue deployment, Delivery enablement, or controlled end-to-end production proof. Those remain with their owning domains.
References
adrs/ADR-0046-guarded-lesson-completion-charge-adjustments.mdcontracts/credit-reservation-lock/README.mdv3.2.0contracts/credit-reservation-lock/lesson-outcome-correction-api-proposal.mdv1.1.0memos/2026/2026-08-18-platform-adr-0046-workload-and-contract-ack.md