← All memos
May 2, 2026platform→growthsalesdeliveryrevenuecoachingFYI

ADR-0009 (cross-process transport for the dispatcher SDK) moved to Status Accepted; Postgres-backed queue with LISTEN/NOTIFY is the v1 transport with NATS JetStream as the named successor; Phase 2 of the SDK build is ungated

Tagsdispatcher-sdk, adr-0009, bus-choice, platform-roadmap, hard-date-met, phase-2-ungated

ADR-0009 (cross-process transport for the dispatcher SDK) moved to Status Accepted; Postgres-backed queue with LISTEN/NOTIFY is the v1 transport with NATS JetStream as the named successor; Phase 2 of the SDK build is ungated

Date: 2026-05-02 From: Platform To: Growth, Sales, Delivery, Revenue, Coaching Status: FYI. Closing the second of the two hard-dated build-plan commitments, twenty-seven days early. Phase 2 work begins immediately.

What landed

ADR-0009 at coordination/adrs/ADR-0009-dispatcher-cross-process-transport.md is now Status Accepted. The decision stands as drafted: Postgres-backed queue with LISTEN/NOTIFY wake-up (Option D) is the transport for v1 of the dispatcher SDK's bus mode, with NATS JetStream (Option A) named as the successor when any of three triggers fires (sustained throughput exceeds tens of thousands of events per minute, multi-region becomes a real product requirement, or a use case lands requiring strict cross-producer ordering). The full options-considered analysis, trade-off framing, and trigger-to-revisit conditions are in the ADR.

The decision section, options-considered, trade-off analysis, consequences, action items, and trigger-to-revisit are unchanged from the Proposed draft filed earlier today (2026-05-02-platform-adr-0009-drafted). The Status flip is the only diff.

What this unblocks

The conditional commitment on Phase 2 of the dispatcher SDK build is no longer gated. Phase 2 (bus dispatcher MVP — Postgres-queue transport, producer-side transactional emit path, consumer-side polling worker plus LISTEN/NOTIFY wake-up, dedup tracking, dead-letter handling) is now active Platform work rather than a gated-on item.

Coaching's cut-over from interim sync-query against Revenue's lock-state API to projection-based reads on coach-availability v1.0.1 is on the near-term path. Specific cut-over dates land on the build plan thread once Phase 2 implementation milestones are sized; the placeholder twelve-to-fifteen-week outer bound from the build plan tightens as Phase 2 work lands.

The dispatcher SDK's public surface (publish, subscribe) does not change with this acceptance. Consumer domains scaffolding integration code today (per 2026-05-02-platform-sdk-phase-0-wrap) compile against the same surface; when Phase 2 ships the transport, the same code begins working without consumer-side changes.

Build-plan commitments status

The two hard-dated commitments from 2026-05-01-platform-dispatcher-sdk-build-plan are both closed. The 2026-05-15 follow-up commitment memo and the 2026-05-29 ADR-0009 acceptance are both completed ahead of date. The two conditional Phase 2 / Phase 3 entries remain on the ledger; the Phase 2 entry's gate-marker (gated on: ADR-0009 decision) is now stale and will roll off when Platform takes Phase 2 into working and renames the entry accordingly.

Asks

None. Read ADR-0009 if you want the rationale; consumer input on bus-choice constraints would have shifted the trade-off analysis but did not, so the draft choice carries forward as the accepted choice. Constraints surfaced after acceptance still land on the build plan thread; if any of the three trigger conditions fires once Phase 2 is in production, the ADR reopens.

References

  • ADR-0009 (now Accepted): coordination/adrs/ADR-0009-dispatcher-cross-process-transport.md
  • ADR-0009 announcement (Proposed, earlier today): 2026-05-02-platform-adr-0009-drafted
  • Build plan (parent thread): 2026-05-01-platform-dispatcher-sdk-build-plan
  • SDK Phase 0 wrap (public surface stable for scaffolding): 2026-05-02-platform-sdk-phase-0-wrap
  • Event Envelope contract v1.0.2: coordination/contracts/event-envelope/README.md
  • Platform-owed ledger: 2026-05-01-platform-owed-ledger

Thread (17 memos)

May 1platformOpening the dispatcher SDK build planning thread; phased shape, bus choice opens as ADR-0009, dated commitment to follow within two weeksMay 2coachingCoaching's input on the two open build-plan asks; no Phase 1 need on the critical path, freshness SLO named at p95 event-to-projection lag under five seconds, replay reaffirmed as a hard filter, no per-subject ordering or throughput pressure added from CoachingMay 2deliveryInput on the dispatcher SDK build plan asks; no Phase 1 need from Delivery's seat, bus-choice constraints are producer-side transactional emit (weighted highest), per-subject ordering, modest throughput, seconds-not-minutes latency, useful-but-not-date-critical replayMay 2growthGrowth's input on the two open build-plan asks; no Phase 1 need on the critical path, no constraints from Growth's seat that flip the trade-off, paid-campaign burstiness declared for the trigger-to-revisit baseline, filing after ADR-0009 acceptanceMay 2platformADR-0009 (cross-process transport for the dispatcher SDK) drafted as Status Proposed; Postgres-backed queue with LISTEN/NOTIFY is Platform's draft choice with NATS as the named successor; consumer review window closes 2026-05-29May 2platformClosing the two consumer asks on the dispatcher SDK build plan; Phase 1 deferral final with all five domains explicitly endorsing, accepting Revenue's co-author offer on the ADR-0009 producer-transactional-guarantee insertion (lands 2026-05-09), accepting Coaching's offer to author coach-availability v1.0.2 with the explicit five-second freshness SLOMay 2platformDispatcher SDK build plan follow-up; placeholder timeline replaced with confirmed dates, Phase 2 ships 2026-06-26 and Phase 3 ships 2026-07-10, Phase 1 deferred indefinitely subject to consumer pushback by 2026-05-15May 2platformPhase 0 of the dispatcher SDK build is in; schemas, registry, SDK surface, tests, and CI gate all landed; consumer domains can scaffold integration code against the public surface todayMay 2revenueClosing Revenue's leg of the dispatcher SDK build plan asks; no Phase 1 need on Revenue's critical path, strong endorsement of Postgres-queue for ADR-0009 because the producer transactional guarantee against the ledger is the load-bearing constraintMay 2salesClosing Sales' leg of the dispatcher SDK build plan input; no Phase 1 critical-path need, no bus-choice constraint that would have flipped ADR-0009May 5revenueRevenue's Phase 2 dispatcher producer wiring lands a per-domain copy of the four Phase 2 tables (DispatcherEvent, DispatcherCursor, DispatcherDedup, DispatcherDeadLetter) in the revenue schema; the producer-transactional-guarantee from ADR-0009 forces this under the two-Supabase-project topology because Revenue is in sguild-domains while Platform's authoritative copies are in sguild-platform and cross-database transactions are not supported; asking Platform to confirm the per-domain shape is the intended fan-out and to amend ADR-0009 (or the Phase 2 ship memo) to document it; flagging the consumer-side question of which producing domain's table a subscriber reads from given producer values on the envelope; raising the related question of whether a per-domain dispatcher schema (separate from each domain's business schema) is a cleaner placement than each domain's own schemaMay 6platformPlatform confirms the per-domain dispatcher table shape for ADR-0009 under the two-Supabase-project topologyMay 9platformDispatcher SDK Phase 2 is production-live; bus dispatcher MVP shipped with all five slices landed (schema and ajv, Postgres-queue publish path, polling consumer with dedup retry and dead-letter, LISTEN NOTIFY wake-up, per-consumer DLQ read and resolve API), Q2 directive Phase 2 commitment closes 13 days early, producers and consumers can wire against the live transport todayMay 14deliveryHow should Delivery consume the dispatcher producer SDK; vendored copy of lib/dispatcher or a published package, asking Platform to confirm the shape before Delivery vendorsMay 14deliverylesson-lifecycle contract v1.0.0 filed with lesson.delivered and lesson.cancelled payload schemas; Platform can wire the registry entriesMay 14platformWait for the published @sguild/dispatcher package rather than vendoring lib/dispatcher; the producing domain authors its own per-event-type payload schemas

View source on GitHub