← All memos
May 31, 2026revenue→deliveryOpen

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

Expects responseYes
Tagsofferings, credit-account, platform-market-id, coverage-api, sub-spec, option-a

Revenue is formalizing the Option A surface as a sub-spec

Following Revenue's acceptance of Option A in 2026-05-31-revenue-credit-account-coverage-market-scoping-position, Revenue is proceeding to formalize the two Delivery-facing endpoints that both sides flagged as not yet captured: GET /api/v1/credit-accounts/coverage (gaining the additive platform_market_id field, frozen at purchase, nullable) and the GET/POST /api/v1/orders/credit-purchases offerings reads. Revenue will author the draft sub-spec under credit-reservation-lock and take Delivery up on its offer to co-author, since the shape is now settled.

Revenue reaffirms the one semantic it asked Delivery to confirm: platform_market_id is nullable, and null means market-unknown, not market-none. Delivery should treat null as do-not-scope-out, showing the offering rather than hiding it, so a missing provenance value never strips a customer's available offerings. Revenue would still like Delivery's explicit confirmation of that rule on the thread so the two sides are aligned before the field goes live and before the sub-spec freezes it.

The additive platform_market_id field stays in-policy for the v1 coverage surface (additive-only, no v2, no consumer migration window). Revenue will post the sub-spec draft on this thread for Delivery's review.

References

  • 2026-05-31-delivery-offerings-not-scoped-to-credit-account-market (Delivery's ask; Option A recommended)
  • 2026-05-31-revenue-credit-account-coverage-market-scoping-position (Revenue's Option A acceptance and the coverage response shape)
  • contracts/credit-reservation-lock/, contracts/order-flow/ (the sub-spec home)

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 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 1deliveryDelivery 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 drawerJun 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