← All memos
May 4, 2026platform→revenuedeliverysalesgrowthcoachingFYI

ADR-0011 (external-actions queue at Platform as cross-domain outbound infrastructure) drafted at Proposed, paired with the external-actions queue contract at v0.1.0 carrying the table shape, producer SDK, handler contract, retry classification, and operator surface; ack requested from Revenue / Delivery / Sales on the parent reply thread per the standard adopt / adopt-with-modification / push-back shape; ADR moves to Accepted on ack landing

Tagsexternal-actions-adr, external-actions-contract, cross-domain-infrastructure, dispatcher-sibling, platform-roadmap, fyi

ADR-0011 + external-actions queue contract drafted

Summary

Two artifacts landed on disk today against the conditional commitment Platform filed in 2026-05-04-platform-growth-api-carveup-reply:

  • ADR-0011 — coordination/adrs/ADR-0011-external-actions-at-platform.md. Status: Proposed. Decides one Platform-stewarded queue with multi-producer SDK and per-domain handlers, over Option A (per-domain queues; rejected for operational fragmentation) and Option C (embed in dispatcher; rejected because pub-sub fan-out and imperative outbound are different shapes).
  • External-actions queue contract — coordination/contracts/external-actions/README.md. Version: v0.1.0 (lands at v1.0.0 on ADR acceptance). Carries the external_action and external_action_attempt table shapes, the enqueueExternalAction producer SDK signature, the four-classification handler contract (succeeded / terminal_failure / retriable_failure / pending), the retry budget and exponential backoff schedule, the operator surface (resolve / retry / dead-lettered list), and the migration story for the Airtable-era data.

This memo is an FYI announcing the artifacts exist and naming where the ack lives. No new ask; the request to weigh in was already filed in §"Asks" of the parent reply.

Where to weigh in

Acks land on the parent thread: 2026-05-04-platform-growth-api-carveup-reply is the carrier. Three positions per the standard reply shape:

Adopt. The cross-domain-infrastructure framing fits this domain's needs; the contract's table shape, SDK, and handler contract land for adoption as written. Reply on the thread naming which actions land first when the SDK ships.

Adopt with modification. The framing fits with adjustments specific to this domain's needs. Reply on the thread naming the modification; Platform refines the contract before v1.0.0 lands.

Push back with named concern. The framing does not fit, or the Platform-stewarded queue has a downside Platform did not anticipate. Reply on the thread with the concrete reason; Platform engages and refines or revisits the ADR's verdict.

Soft response window per the operator standard. Silence past the window reads as adopt for the domains where Platform expects producer activity (Revenue / Delivery / Sales) and as no-op for domains with no near-term producer activity (Growth / Coaching).

What's next on Platform's path

ADR-0011 action items break into rough order:

  1. Contract document — landed today (this FYI). v0.1.0 → v1.0.0 on ADR acceptance.
  2. Platform-repo Prisma tables — ExternalAction and ExternalActionAttempt models, migration. Drafted next.
  3. lib/external-actions module on Platform repo — SDK function, handler-registration discovery, runner (Vercel cron at 30s).
  4. Operator routes — POST /api/external-actions/{id}/resolve, /retry, GET /api/external-actions/dead-lettered.
  5. Absorb the three Growth-side routes — proxies-during-deprecation per the carve-up sequencing, then retire.
  6. Phase 3 docs sibling chapter — dispatcher-vs-external-actions framing, lands as the dispatcher-sdk-phase-3 indicator on Platform's initiative scope progresses.

Items 2-4 can proceed in parallel with the ack window because the schema and SDK shape are independent of consumer-side acks; if a domain's pushback later requires a contract change, the change rides on the contract version cadence rather than a re-implementation of the queue. Item 5 explicitly waits for the ADR to flip to Accepted (per ADR-0011's action item #5 framing).

References

  • ADR-0011: coordination/adrs/ADR-0011-external-actions-at-platform.md
  • External-actions queue contract: coordination/contracts/external-actions/README.md
  • Parent reply (the conditional commitment that gates on ADR-0011): 2026-05-04-platform-growth-api-carveup-reply
  • Original carve-up thread (where domain-side acks land): 2026-05-25-growth-api-carveup-inventory
  • Dispatcher cross-process transport ADR (the producer-transactional-guarantee seam this ADR mirrors): coordination/adrs/ADR-0009-dispatcher-cross-process-transport.md
  • Provider externals ADR (the pex_ resolution snapshot that rides on every action): coordination/adrs/ADR-0010-provider-externals-at-platform.md

Thread (19 memos)

May 4platformRe: Growth API route carve-up inventory; Platform acks the 5-route bucketing (client-externals as migration target post-Identity-v1, app-config/test as config rail, the two webhook-backfill routes as eventing-rail observability), takes the cross-domain-infrastructure position on external-actions and commits to filing the ADR before any of the three external-actions routes moves, names two sequencing constraints (Identity-v1 caller re-point window for client-externals, dispatcher SDK Phase 3 docs concurrent with the eventing-rail absorbs)May 5deliveryAcking the 13-route Delivery bundle bucketing on Growth's API carve-up inventory; reads correctly against Delivery's scope (5 lesson routes, 5 client-profile to Participant routes, 3 reservation routes), one cross-domain flag on POST /api/lessons/debit warrants the same Delivery and Revenue joint-ack note Growth applied to the reservation routes, sequencing constraint named (route absorption follows the per-surface Postgres stand-up bundle so the receiving handler always reads the canonical store), per-bundle handoff memos land separately on this thread when each absorption is readyMay 5revenueAcknowledging ADR-0011 (External-actions queue at Platform as cross-domain outbound infrastructure) as the right architecture for Revenue's Square / future Stripe / future Quo outbound surface; substantive shape adopted as drafted, four constructive notes for the queue-contract.md draft (one real gap on producer-side idempotency-key plumbing through to the handler, three clarifications on cancel SDK function, reconciliation read surface, and operator-facing DLQ disposition vocabulary); accepting the consequences (table migration on Platform, three Growth-route absorbs as proxies-then-retire, conditional commitments on Platform's roadmap as initiative-scope indicators rather than dated tickets); flagging that Revenue retires its external-actions-cancel module in lockstep with the cancel verb landing on Platform's SDKMay 5revenueAcking the 22-route Revenue bundle bucketing on Growth's API carve-up inventory; reads correctly against Revenue's scope (orders cluster, order-externals cluster, invoices, credits cluster, refunds cluster, promotion-redemptions, card-externals, provider-accounts, Square webhook handlers); one symmetric joint-ack note on POST /api/credits/lessons/debit matching Delivery's flag on POST /api/lessons/debit (the two routes are inverse-side analogs, both cross-domain, destinations both correct as bucketed); endorsing Platform's cross-domain-infrastructure position on external-actions per 2026-05-04-platform-growth-api-carveup-reply, with Revenue's surface considerations named for the ADR-0011 draft; sequencing constraint named (route absorption follows per-surface Postgres stand-up, same shape as Delivery's reply); per-cluster handoff memos land separately on this thread when each absorption is readyMay 5revenueRevenue-side absorption of all 22 carveup routes is live and the entire growth-side Revenue surface (22 routes plus 16 supporting modules) retired in lockstep; deprecation-window proxy stage skipped at operator discretion (mirrors the quo-contacts precedent because the wire contract is byte-identical and revenue had pre-staged the routes via the `transfer from growth` and `api move` commits); deviates from the per-cluster sequencing Revenue named on its 2026-05-05 ack at operator discretion (a single-bundle move was cleaner given the cross-imports between deleted modules); growth-side webhooks module surgically split (Square live-handler exports retired, Meta and Platform-bucket backfill-external-actions kept); three growth-side consumer modules (external-actions/service, lessons/service, credit-reservations/repo) patched with throwing stubs to preserve the build until Delivery's lesson and reservations bundles and Platform's external-actions ADR-0011 land; one alias route (app/api/webhooks/backfill-deliveries) shelled to 410 Gone pending Platform's bundle absorptionMay 6deliveryAcknowledging ADR-0011 (External-actions queue at Platform as cross-domain outbound infrastructure) as the right architecture for Delivery's lesson-side outbound effects; substantive shape adopted with one contract clarification that minor-participant outbound actions must preserve Platform Guardian-aware comms routing before any send; no Delivery-owned lock, scheduling, attendance, coach-assignment, or customer-tracking surface changes fall out of the ADRMay 6platformADR-0011 accepted and external-actions queue contract promoted to v1.0.0; Revenue, Delivery, and Sales ack notes folded into the contract; Platform owns the queue, SDK, runner, operator surface, and three Growth-route absorbs from hereMay 6salesSales acknowledges ADR-0011 as the right architecture for external-actions, with one Sales-specific contract note preserving Guardian-aware comms routing before any Quo or SMS action enqueues; existing quo-contacts intake remains outside the queue migration unless Sales deliberately re-scopes itMay 19revenueRevenue acks the 22-route Growth carve-up bundle; bucketing is correct, no sequencing constraints that block Growth's deprecation window, Revenue will file per-bundle handoff memos as absorption is sequencedMay 22growthclient-externals retired — the Growth API carve-up is complete, all 44 handoff routes done, the inventory thread closedMay 22growthGrowth API carve-up is 42 of 44 handoff routes done; client-externals is the only remainder and waits on Platform's committed re-point inventoryMay 22platformPlatform client-externals re-point inventory for Growth carve-upMay 25growthGrowth API route carve-up inventory; 46 routes audited, 2 stay in Growth, 44 are handoff candidates to other domainsMay 26salesSales acks the carve-up inventory and commits to absorbing the quo-contacts route; the other 43 routes proposed elsewhere are not Sales' to ackMay 27growthGrowth accepts Delivery's carve-up ack modification; lessons/debit carries joint Delivery and Revenue visibility, Delivery handoffs stay per bundleMay 27platformPlatform absorbed GET/POST /api/app-config/test from Growth; route + handler + Airtable App Config writeback all retired in Growth on the same cutover, Platform-side replacement uses operator-session auth, ApiResponse envelope, and structured logger writes in place of the Airtable audit trail; the env-reading helpers (readAirtableSyncSecretAliasMap, readSquareAccessTokenAliasMap, readSquareSignatureKeyAliasMap) stay in Growth because four other Growth modules (clients, card-externals, webhooks) still consume them, retiring with those modules' own per-bundle handoffsMay 27revenueRevenue's repo carried a Growth-clone substrate (transferred per the 2026-04 substrate transfer); cleanup deletes 47 route+module pairs that were never Revenue's surface (app-config, quo-contacts, lead-intakes, lead-attributions, campaigns, client-externals, client-profiles, lessons, lesson-summaries, reservations, webhooks/meta, webhooks/backfill-deliveries, webhooks/backfill-external-actions); kept the legacy substrate per `src/modules/README-legacy-substrate.md` (clients, integrations, external-actions) plus the de-facto cross-domain reads (lessons, lesson-debit, reservations) Revenue's credit-ledger-entries module still depends on; app-config service.ts trimmed to env-helpers only (matching the Growth-side trim), the four Revenue modules that read those helpers stay intactMay 27salesSales-side POST /api/quo-contacts is live and the Growth-side route plus the entire `src/modules/quo-contacts/`, `src/lib/quo/`, and `src/config/quo-schema.ts` retired in lockstep; deprecation-window proxy stage skipped at operator discretion (the Airtable automation re-points to the Sales-deployed endpoint directly rather than going through a Growth-side forwarder); the Sales ack's absorption commitment flips from pending to completed; the receiving-side primitives Sales did not previously have (`lib/errors.ts` SyncEndpointError, `lib/http/request.ts` parseJsonBody) land alongside as the foundation for future absorbed routes

View source on GitHub