Platform acknowledges ADR-0041 and confirms the multi-line close preserves the existing one-account reservation lifecycle
Platform position
Platform acknowledges ADR-0041 and approves the additive offer_items shape published in sales-ordering-surface v2.5.0. The change composes multiple Revenue-owned Order Items into one Order. It does not change the credit-reservation-lock lifecycle, scheduling ownership, or the account scope from which the first-lesson reservation is funded.
The invariant remains one canonical OrgMarket Credit Account for the request's Person, Organization, and Market, plus one credit reservation bound to one first lesson. Purchased credits from every validated line enter that account before Revenue runs the existing deterministic pending-reservation allocator. The Order's credit_reservation_id remains provenance and scoped-read correlation, not a line-specific or exclusive funding target.
Contract and event impact
No credit-reservation-lock state, transition, funding sub-state, ledger entry type, event type, or event payload amendment is required. The existing credit.purchased, credit.reserved, credit.funded, credit.locked, and first-lock customer.handoff facts retain their current meanings. Multi-line commercial detail remains authoritative on the Revenue Order and Order Items rather than being copied into reservation lifecycle events.
The v2.5.0 same-Organization, same-Market, same-currency validation is load-bearing. A future cart spanning Markets or Organizations, or a close binding more than one lesson, would cross the current one-account and one-reservation boundary and requires a new contract and architecture decision.
Rollout boundary
Platform's acknowledgment completes the architecture approval and allows ADR-0041 to move to Accepted. It does not declare the Revenue capability production-ready. Revenue's declared deployment and controlled-close proof remain open, including proof that one reserved close produces one reservation, one bound lesson, one Order, and one provider invoice containing every selected line. Sales may implement against v2.5.0 now, but production enablement remains gated on that Revenue proof.
References
- ADR-0041:
adrs/ADR-0041-multi-line-sales-ordering-close.md - Sales proposal:
2026-08-02-sales-multi-package-scheduling-close-proposal - Revenue approval and implementation:
2026-08-02-revenue-multi-line-sales-ordering-approved - Sales Ordering Surface Contract:
contracts/sales-ordering-surface/README.mdv2.5.0 - Credit Reservation Lock Contract:
contracts/credit-reservation-lock/README.mdsections 12.10 and 13.11