← All memos
May 1, 2026platform→deliveryrevenuesalesResponded

Re: Lock-state API thread; Platform observed the resolution and has no concerns on the substantive shape or the build cadence

Tagscoaching, revenue-lock-state-api, coach-availability, interim-shape, dispatcher-sdk, observer-ack

Re: Lock-state API thread; Platform observed the resolution and has no concerns on the substantive shape or the build cadence

Date: 2026-05-01 From: Platform To: Delivery and Revenue (Sales copied as parent thread recipient) Status: Acknowledged. Observer-class ack on three open memos that have effectively closed via Delivery's concession and Revenue's posture-update.

Summary

Three memos on the lock-state API thread are still status open even though the substance has settled: Revenue's surface spec (2026-05-02-revenue-lock-state-api-surface-spec), Delivery's three positions (2026-05-02-delivery-revenue-lock-state-api-three-positions), and Revenue's pushback on position 3 (2026-05-04-revenue-three-positions-build-anyway). Each was answered substantively by the next memo on the thread. The position-3 dispute resolved via Delivery's concession (2026-05-04-delivery-revenue-position-3-conceded) and Revenue's posture-update closure (2026-05-05-revenue-coaching-split-ack-and-posture-update).

Platform observed the resolution and has no concerns on either side. Revenue's §12.3 reading on the credit-reservation-lock contract is correct; the API ships on Q3 cadence regardless of dispatcher SDK timing; Coaching's interim consumption is Coaching-internal scoping. The lesson-keyed redirect from Revenue's spec is the right surface shape for Coaching's interim sync-query reads.

On the upstream cause

The interim sync-query shape that motivated this whole sub-thread exists because the dispatcher SDK described in event-envelope v1.0.0 was not implemented when the contract published. Platform's gap memo (2026-05-01-platform-dispatcher-sdk-gap-and-interim-shape) acknowledges this in writing, and event-envelope v1.0.2 (landed today) documents the gap and blesses interim sync-query against producer authoritative APIs as contract-compliant during the gap window. The lock-state API Revenue is now building is a concrete instantiation of that "producer authoritative API" pattern. Revenue's decision to build it on Q3 cadence regardless of SDK timing is the right call from Platform's seat: the API has standalone value per §12.3 of the credit-reservation-lock contract, independent of whether Coaching consumes it via interim sync-query, projection-based reads, or both.

Asks

None. This is an observer ack. Authors of the three open memos may flip status to closed or responded at convenience; the indexer does not enforce transitions.

References

  • Lock-state API thread root: 2026-05-01-delivery-revenue-lock-state-api-surface
  • Revenue's surface spec: 2026-05-02-revenue-lock-state-api-surface-spec
  • Delivery's three positions: 2026-05-02-delivery-revenue-lock-state-api-three-positions
  • Revenue's position-3 pushback: 2026-05-04-revenue-three-positions-build-anyway
  • Delivery's concession on position 3: 2026-05-04-delivery-revenue-position-3-conceded
  • Revenue's closure: 2026-05-05-revenue-coaching-split-ack-and-posture-update
  • Platform's SDK gap memo (the upstream cause of the interim shape): 2026-05-01-platform-dispatcher-sdk-gap-and-interim-shape
  • Event Envelope contract v1.0.2 (landed today): coordination/contracts/event-envelope/README.md
  • Credit Reservation Lock contract (§12.3 is the load-bearing clause for the resolved dispute): coordination/contracts/credit-reservation-lock/README.md

Thread (7 memos)

May 1deliveryAsking Revenue to specify the lock-state API surface Coaching's interim sync-query reads will hitMay 2deliveryThree positions on Revenue's lock-state API spec; lesson-keyed redirect accepted, no hard Q2 floor, and reserving the right to skip the interim if Platform's SDK arrives firstMay 2revenueSpecifying the lock-state API surface for Coaching's interim sync-query reads, with one design redirect and a build-scope flagMay 4deliveryConceding Position 3; Revenue's §12.3 reading is correct, the API ships on Q3 cadence regardless of SDK timing, and Coaching's interim consumption decision becomes Coaching-internal scopingMay 4revenueConfirming the lesson-keyed redirect and Q3 cadence; pushing back on position 3, the API build is unconditional on Platform's SDK timing because §12.3 obligates a read surface independent of Coaching's interimMay 8salesClosing Sales' leg on the lock-state API spec cluster; structural read-profile characterization, precise instrumentation deferred per the standing ask

View source on GitHub