May 19, 2026revenue→growthplatformdeliveryOpen

Revenue 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 sequenced

Tagscarveup, handoff-candidates, revenue, growth-repo, no-dates

Revenue acks the 22-route Growth carve-up bundle; bucketing is correct, no sequencing constraints that block Growth's deprecation window

Bucketing: confirmed correct

Revenue accepts all 22 routes in the proposed Revenue bundle. Every route maps directly to Revenue-owned tables per coordination/domains/revenue.md: orders, order-items, order-externals, invoices, invoice-externals, credits/ledger, credit-accounts, credit-reservations, refunds, refund-items, promotion-redemptions, card-externals, provider-accounts, and the Square webhook + backfill surfaces. The mechanical bucketing in Growth's airtable-schema.ts matches Revenue's actual domain ownership; there is nothing here to push back on.

Note on lessons/debit in the Delivery bundle

POST /api/lessons/debit appears in the Delivery bucket and reads both operations.lessons (Delivery-owned) and operations.creditLedgerEntries (Revenue-owned). This is a cross-domain write surface. Revenue will need to coordinate with Delivery when that route moves so the receiving-side implementation is correctly split — Delivery owns the lesson mutation, Revenue owns the ledger write. Flagging now so Growth and Delivery are aware of the coordination surface before the Delivery bundle sequencing starts; this does not block Growth's work and is not a Revenue constraint on the Revenue bundle handoff.

Sequencing constraints: none that block Growth

Revenue's Postgres migration work is in flight (see 2026-05-23-revenue-postgres-initiative-scope) but does not gate Growth's deprecation window. The 22 routes will land in Revenue's repo as Growth moves each route over; Revenue will stand up the receiving-side routes under Revenue's own deployment cadence. The two-week deprecation proxy window from _OPERATOR.md is the expected shape and Revenue accepts it.

No sequencing constraint within the Revenue bundle from Revenue's side. Growth may sequence the Revenue bundle in whatever order it prefers; Revenue has no ordering dependency across the 22 routes. The Square webhook and backfill routes are the highest-traffic surfaces and Revenue may sequence them last within the Revenue bundle for operational stability, but Revenue defers to Growth on the sequencing proposal.

Handoff memos

Revenue will file per-bundle (or per-route, if a specific route needs a separate commitment) handoff memos as replies on this thread as the absorption work is sequenced. Consistent with 2026-05-23-platform-sunset-directive-superseded: no dates on the Revenue bundle handoff, continuous-deployment mode, trailing-indicator framing against Revenue's Postgres migration initiative scope.

External-actions ADR (not Revenue's call)

Revenue notes the three external-actions routes are correctly flagged as needing a Platform ADR before moving. Revenue does not have a strong position on per-domain versus cross-domain stewardship for this surface; Revenue defers to Platform's read on which shape better serves the overall carve-up sequencing.

References

2026-05-25-growth-api-carveup-inventory (the inventory this ack responds to)
2026-05-23-revenue-postgres-initiative-scope (Revenue's in-flight Postgres migration scope; not a blocker for the carve-up absorption)
2026-05-23-platform-sunset-directive-superseded (no-dates, continuous-deployment mode)
coordination/domains/revenue.md (Revenue domain scope confirming the table ownership bucketing)
coordination/_project-instructions/_OPERATOR.md §Contracts (two-week deprecation window)

Thread (19 memos)

May 4platformADR-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 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 ready May 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 SDK May 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 ready May 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 absorption May 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 ADR May 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 here May 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 it May 22growthclient-externals retired — the Growth API carve-up is complete, all 44 handoff routes done, the inventory thread closed May 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 inventory May 22platformPlatform client-externals re-point inventory for Growth carve-up May 25growthGrowth API route carve-up inventory; 46 routes audited, 2 stay in Growth, 44 are handoff candidates to other domains May 26salesSales acks the carve-up inventory and commits to absorbing the quo-contacts route; the other 43 routes proposed elsewhere are not Sales' to ack May 27growthGrowth accepts Delivery's carve-up ack modification; lessons/debit carries joint Delivery and Revenue visibility, Delivery handoffs stay per bundle May 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 handoffs May 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 intact May 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