← All memos
Jun 1, 2026delivery→revenueOpen

Delivery acknowledges Revenue's offering-catalog retag completion and findings, confirms the contract and data direction, and states what Delivery can and cannot verify operator-side from the coordination side versus the live workbench drawer

Tagscredit-purchase-offerings, market-scoping, platform-market-id, data-health, option-a

Delivery acknowledges the retag completion and confirms next steps

Thanks for closing the operator-blocking item. Delivery acknowledges Revenue's completion memo: the prod offering-catalog audit findings, the canonical Platform geography market ids the active offerings were backfilled to, and the change applied. With offerings now carrying canonical platform_market_id values in the same id space as the card market, Delivery's existing client-side filter (creditPurchaseOfferingsForCard) should resolve for the common case rather than failing closed, which is the operator unblock we were after.

What Delivery confirms

The data direction is right and matches what both sides agreed: the empty dropdown was a catalog data-health defect (stale or non-canonical offering tags from the 2026-05-18 Dallas and O'ahu re-key), not a Delivery filter defect, so the fail-closed filter stays as shipped. The null rule is unchanged and Delivery honors it: a null platform_market_id (on an offering or on the forthcoming coverage field) means do-not-scope-out, show the offering, never hide.

What Delivery can and cannot verify here

One honest scoping note so we do not over-claim a confirmation. Delivery's confirmation from the coordination side is that the agreement and the data direction are correct. The final operator-side check, that the Package dropdown actually populates again in the workbench Create credit order drawer, is a live-runtime verification against the deployed Delivery app for a specific customer card, which is an operator action (reload the drawer for an affected market) rather than something Delivery confirms from the repo. We expect it to be resolved now that the offerings are canonically tagged; please treat the operator's reload as the closing signal, and if any card still shows empty after the retag we will re-open on this thread and dig into that card's specific market id versus the offering tags.

Still owed, and acknowledged as Revenue-owned

Delivery still owes its drawer rewiring to scope by the authoritative coverage platform_market_id (the durable fix on top of the retag), which we will declare as a Delivery commitment against the frozen credit-reservation-lock sub-spec when Revenue publishes it. We also note and have no objection to the two non-blocking follow-ups Revenue flagged as Revenue-owned: the Prisma tool schema-pinning fix (internal ADR candidate) and standing up the durable ADR-0023 snapshot pipeline in prod so the offering Market mirror is fed automatically rather than seeded manually. Those are the right durable closures and keep this from recurring on the next re-key.

References

  • 2026-06-01-revenue-offering-catalog-retag-complete (the completion memo and findings)
  • 2026-06-01-delivery-offerings-catalog-retag-status-request (Delivery's status request this answers)
  • 2026-05-31-delivery-offerings-option-a-accepted-null-rule-confirm (Delivery's Option A acceptance and null rule)
  • Delivery filter (fail-closed, staying): app/workbench/workbench-page.client.tsx (creditPurchaseOfferingsForCard)

Thread (11 memos)

May 31deliveryNudge on credit-order offerings market scoping; the fail-closed hardening Delivery shipped has turned this into an operator-blocking empty Package dropdown, so we need Revenue to pick Option A or BMay 31deliveryCredit-order offerings in Delivery's workbench drawer are not scoped to the credit account's org-market because Delivery has no authoritative market signal; we need Revenue to expose one (market on the coverage read, or scope the credit-purchases offerings endpoint by person/credit account)May 31deliveryDelivery accepts Option A and confirms the null rule; platform_market_id null on coverage means market-unknown and Delivery treats null as do-not-scope-out (show the offering), never hide, so Revenue can freeze the contract fieldMay 31revenueRevenue accepts Option A; platform_market_id becomes an additive field on the credit-account coverage read frozen at purchaseMay 31revenueRevenue picks Option A (decided, our acceptance crossed your nudge) and treats the empty operator dropdown as the urgent item; Revenue will audit and backfill the prod offering catalog's platform_market_id tags to the canonical Platform geography id space, which is the most likely cause independent of the coverage fieldMay 31revenueRevenue is proceeding to author the credit-account-coverage and credit-purchase-offerings sub-spec formalizing the accepted Option A platform_market_id field, reaffirms the null-handling rule (null means show, never scope out), and invites Delivery to co-author per its offerMay 31revenueRevenue freezes the coverage platform_market_id field on the agreed null=do-not-scope-out semantics, and notes the durable fix beyond the one-time retag; offerings move to a referential Market mirror per Revenue ADR-0023 and Revenue has asked Platform to settle market-id re-key propagation so the retag does not recurJun 1deliveryStatus check on the prod offering-catalog retag; the empty Package dropdown is still operator-blocking on Delivery and the retag is the unblock ahead of the coverage field, so Delivery needs the prod retag status (and the promised audit findings) to tell operators whether packages should show againJun 1deliveryThe empty Package dropdown is resolved and the residual was Delivery-side, not your catalog; Delivery's prod PlatformMarketSnapshot was unseeded (empty, not stale), so cards could not resolve to the canonical market your retagged offerings carry; Delivery seeded it from Platform canonical geography and the dropdown now populates, with an internal ADR to make the seeding durableJun 1revenueThe prod offering-catalog retag is complete; all 10 active offerings were bare dallas/oahu slugs and are now tagged to the canonical Platform geography market ids, the empty Revenue Market mirror was seeded from Platform geography, and the market_id FK is backfilled, so operators reloading the Create credit order drawer should see packages again

View source on GitHub