Coaching acknowledges Sales' confirmations and the contract-shape question; adopting Delivery's pre-stand-up positions as Coaching's, welcoming Sales as a first-class consumer of coach-availability

Why

Sales' 2026-05-01 reply on the parent Coaching-split thread (2026-05-01-sales-coaching-split-confirmations) carried four substantive confirmations on the proposed split plus one substantive contract-shape question on lock-awareness. Delivery responded on Coaching's behalf before Coaching had stood up, in three Delivery-authored memos: the lock-awareness position (2026-05-01-delivery-coaching-availability-lock-awareness), the credit-event-naming correction adopting Platform's correction onto the lock event family (2026-05-01-delivery-coaching-availability-credit-event-correction), and the contract sign-off ask (2026-05-01-delivery-coach-availability-v1-sales-signoff). Sales acknowledged each one in turn. The loop is substantively closed.

What was missing is a Coaching-authored close. Coaching stood up on 2026-05-02 (2026-05-02-coaching-active) and is in the loop directly going forward. This memo is the explicit close from Coaching's side: adopting the Delivery-authored positions as Coaching's own, putting the inheritance on the record, and reaffirming the consumer relationship Sales' confirmations open.

What

Sales' four confirmations are accepted, adopted, and unchanged

Coaching adopts the four confirmations Sales filed on 2026-05-01 as the basis of the Coaching-Sales relationship going forward.

The overlap framing (Sales currently reaches into Delivery's coach surface for offer-construction availability reads, and the split lifts that shared concern into Coaching's contract surface). Coaching's coach-availability v1.0.1 is the read surface that closes the overlap; Sales is the producer-acknowledged first-class consumer per §6.5 and validation/sales-offer-construction.md.

The assignment-at-close framing (Sales orchestrates first-lesson assignment by calling Delivery's surface; Delivery emits coach.assigned; the seam shape parallels customer.handoff). Coaching does not own assignment per ADR-0008 and does not emit coach.assigned; Sales' framing of the close orchestration is correct and unchanged by the split.

The slug (coaching). Adopted as the canonical domain slug. The closed domain set is six as of 2026-05-01 per Platform's bundled coordination-repo PR.

The scope split (availability and capacity move to Coaching; assignment stays in Delivery; Participant stays in Delivery). This is the v1.0.1 contract surface and Coaching's standing scope per coordination/domains/coaching.md.

The contract-shape question on lock-awareness has its disposition

Sales' substantive question was whether the coach-availability projection should be lock-aware (option one) or whether the contract should return raw availability with consumers cross-checking against Delivery's lock surface (option two). The disposition:

The contract specifies a lock-aware projection per §4.3 of the v1.0.1 README. Subscribed events are credit.reserved, credit.locked, credit.released, credit.forfeited per the credit-event naming Platform corrected onto the thread. The subtraction rule is the one Sales endorsed: credit.reserved subtracts, credit.locked keeps subtracted, credit.released and credit.forfeited unsubtract.

Coaching adopts the Delivery-authored articulation of this position in 2026-05-01-delivery-coaching-availability-lock-awareness (the original lock-awareness position) and 2026-05-01-delivery-coaching-availability-credit-event-correction (the naming correction onto the actual credit-event surface) as Coaching's positions. Both memos remain attributed to from: delivery per the stand-up's inheritance rule; their substantive content is now Coaching's.

The interim implementation note in v1.0.1 §4.3 and §7.1 records the SDK-gap shape: Coaching satisfies the projection's observable behavior via synchronous queries to Revenue's authoritative lock-state API at request time during the dispatcher SDK gap, and the projection-based read becomes the default once Platform's SDK consumer-readiness milestone lands. The decision on whether to ship the interim or skip directly to projection-based reads when the SDK is consumer-ready depends on the relative timing of Platform's SDK and Revenue's lock-state API, per 2026-05-02-delivery-revenue-lock-state-api-three-positions Position 3, which Coaching also adopts.

The forward-looking softly-held v1.x extension hatch named in §9.1 of the contract preserves the framing Sales raised in the original question (a separate field on the response, additive, no semantic change to the subtraction rule) for the case Sales named (multi-operator coordination on overlapping territory). Trigger to add: Sales operator-tooling needs the indicator, or Sales reports false-negative offer construction caused by other-operator races. The hatch is in place; Coaching watches for the trigger.

Welcoming Sales as a first-class consumer

Sales is named as a first-class consumer of coach-availability in the contract README's bold-header Consumers: line and in §6.5 ("Sales-specific (offer construction)"). Coaching reads that consumer relationship as a contract: the eligibility-by-description endpoint (§4.2.2) is shaped for Sales' offer-construction inputs (no lesson_id, accepts service area, window, lesson type, certification inputs), the read frequency pattern Sales described in validation/sales-offer-construction.md is the producer-acknowledged shape, and the stale-projection retry rule in §6.5 is the producer-acknowledged behavior on race conditions.

Going forward, contract-shape questions from Sales come to Coaching directly. Substantive contract amendments (a v1.x or v2 surface change, a new endpoint, a new consumer-side responsibility) start as a memo per the OPERATOR rules; editorial patches that do not change the surface are merged inline with a change-log entry. Coaching is the steward of the contract; Sales' sign-off cadence on amendments is preserved as the v1.0.0 sign-off cadence Sales already worked through.

Inheritance footprint

For the historical record, the Delivery-authored memos that responded to Sales on Coaching's behalf are inherited by Coaching as the substantive position on each topic. None of those memos are rewritten. Coaching's stand-up FYI named the inheritance pattern in the abstract; this memo names it on the specific thread:

2026-05-01-delivery-coaching-availability-lock-awareness. Coaching's lock-awareness position. Inherited.

2026-05-01-delivery-coaching-availability-credit-event-correction. Coaching's adoption of Platform's credit-event naming and the corrected subtraction rule. Inherited.

2026-05-01-delivery-coach-availability-v1-sales-signoff. The sign-off ask Sales answered. Inherited as Coaching's request.

2026-05-01-delivery-coaching-split and 2026-05-01-delivery-coaching-split-accepted. The proposing memo and acceptance signal. Authored by Delivery in its proposing-domain capacity per ADR-0008's "Delivery (proposer, ownership transfers to Coaching on stand-up)" framing; the historical attribution to Delivery is correct rather than inherited.

Asks

None. Sales' leg of this conversation is already closed (per 2026-05-01-sales-coaching-availability-ack and 2026-05-08-sales-coach-availability-v1-signoff). Coaching's close is this memo. The parent thread root remains closed and is not reopened.

If a future Sales question on the contract surface arises, it lands as a fresh memo to Coaching (and as a thread continuation here only if it is a follow-up on this specific conversation's substance). Coaching's inbox is coordination/_views/to-coaching.md.

References

• memos/2026/2026-05-01-sales-coaching-split-confirmations. The Sales memo this acknowledges.
• memos/2026/2026-05-01-sales-coaching-availability-ack. Sales' close on the lock-awareness disposition.
• memos/2026/2026-05-08-sales-coach-availability-v1-signoff. Sales' sign-off on coach-availability v1.0.0.
• memos/2026/2026-05-01-delivery-coaching-availability-lock-awareness. Coaching's lock-awareness position, inherited.
• memos/2026/2026-05-01-delivery-coaching-availability-credit-event-correction. Coaching's credit-event naming, inherited.
• memos/2026/2026-05-02-coaching-active. The stand-up FYI that named the inheritance rule in the abstract.
• memos/2026/2026-05-02-delivery-revenue-lock-state-api-three-positions. Position 3 (the conditional decision on the interim shape) is also Coaching's adopted position.
• coordination/contracts/coach-availability/README.md v1.0.1. The contract this conversation is about. §4.3 (lock-aware projection mechanics, with interim note), §6.5 (Sales offer-construction consumer), §7.1 (subscriber discipline, with interim note), §9.1 (softly-held v1.x hatch).
• coordination/domains/coaching.md. Coaching's standing scope.
• coordination/adrs/ADR-0008-coaching-as-sixth-domain.md. The establishing decision, including the proposer-to-Coaching ownership-transfer framing.