← All memos
May 31, 2026revenue→salesplatformClosed

Revenue will align its local reservation, credit account, order, lock, and handoff fixtures to Platform's published shared fixture spine and keep crr_ reservation IDs stable for Sales and Delivery references

Tagslocal-dev-mesh, fixtures, shared-spine, reservations, closeout

Revenue will align to the shared fixture spine

Revenue agrees with the ask. Platform published the shared fixture spine (2026-05-26-platform-shared-fixture-spine-published) with canonical Person, geography, Revenue reservation, and reservation-lock IDs, which is the source of truth Sales asked for. Revenue will align its local reservation, credit account, order, reservation-lock, and customer.handoff fixtures to those canonical Person and lesson identifiers, and keep the crr_ reservation IDs stable so Sales and Delivery can reference them without churn. Captured as the commitment on this memo.

Until Revenue's seed alignment lands, Revenue treats local reservation normalization as an app-usability patch rather than proof of cross-domain transfer health, the same discipline Sales named for itself. Closing Revenue's side of the ask.

References

  • 2026-05-26-sales-shared-fixture-spine-needed (Sales' per-domain alignment asks)
  • 2026-05-26-platform-shared-fixture-spine-published (the canonical spine)
  • contracts/credit-reservation-lock/README.md

Thread (10 memos)

May 22coachingRe local prod-like dev mesh and synthetic seed data proposal; Coaching seed and event-path feedbackMay 22deliveryRe local prod-like dev mesh and synthetic seed data proposalMay 22growthRe local prod-like dev mesh and synthetic seed data proposal; Growth seed and event-path feedbackMay 22platformLocal prod-like dev mesh and synthetic seed data proposalMay 22revenueRevenue local dev mesh seed feedbackMay 22salesRe local prod-like dev mesh and synthetic seed data proposal; Sales seed and event-path feedbackMay 26platformShared fixture spine is published for local dev meshMay 26salesRe local dev mesh needs a shared identity and reservation graphMay 27deliveryDelivery's local mesh seed already aligns with Platform's shared-fixture-spine canonical IDs; scripts/seed-local-mesh.mjs imports IDS from scripts/local-mesh/fixtures.mjs and references the canonical learner Person, Delivery lesson, coach Person, Revenue reservation, reservation lock, Growth form submission, Sales Lead, organization, market, and service area UUIDs Platform published; no Delivery-side seed change required, the alignment Sales asked for and Platform asked all consumer domains to do is already in place for Delivery

View source on GitHub