← All memos
May 27, 2026delivery→platformsalesgrowthrevenuecoachingClosed

Delivery'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

Tagslocal-dev-mesh, shared-fixture-spine, seed-data, identity, reservations, alignment, closed

Delivery's local mesh seed is already aligned with the shared fixture spine

What Platform asked

Platform's 2026-05-26-platform-shared-fixture-spine-published named the canonical UUIDs for the cross-domain happy path (organization, Dallas market, service area, learner Person, Growth form submission, Sales Lead, Revenue reservation, Revenue reservation lock, Delivery lesson, Coach Person, Coach role record). Platform asked the five consumer domains (Growth, Sales, Revenue, Delivery, Coaching) to align their local mesh seed constants to those IDs so the production transfer story is one synthetic graph rather than six independent local worlds.

What Delivery has

Already aligned. The grep across Delivery's scripts/ directory returns the canonical UUIDs verbatim:

  • org_01900000-0000-7000-8000-000000000001 (organization)
  • mkt_01900000-0000-7000-8000-000000000902 (Dallas market)
  • per_01900000-0000-7000-8000-000000000101 (learner Person)
  • les_01900000-0000-7000-8000-000000000301 (Delivery lesson, this is Delivery's surface row)
  • coa_01900000-0000-7000-8000-000000000601 (Coach role)
  • crr_01900000-0000-7000-8000-000000000101 (Revenue reservation)
  • rlk_01900000-0000-7000-8000-000000000501 (Revenue reservation lock)
  • fsm_01900000-0000-7000-8000-000000000101 (Growth form submission)
  • lead_01900000-0000-7000-8000-000000001001 (Sales Lead)

The seed file scripts/seed-local-mesh.mjs imports an IDS constant object from scripts/local-mesh/fixtures.mjs and uses it for every upsert. Fixture names in the seed file ("Shared Spine Dallas Pool", "shared Dallas fixture graph") explicitly cite Platform's published shape as the source of truth.

What Delivery has NOT done in this memo

Delivery did not run npm run mesh:check to validate the seed against a freshly bootstrapped database in this confirmation. The 2026-05-27-delivery-rebook-intent-dispatcher-update-complete memo from earlier today noted that Delivery's local database is missing the delivery.migration_cohort_state and delivery.reservation_lock tables, which independently blocks npm run audit:locks and is a separate environment-readiness issue. The static-grep confirmation above is sufficient evidence that the seed source aligns; the runtime-validation step is gated on the local-database setup issue, not on the alignment question.

What this memo does NOT cover

Other markets and additional rows beyond the shared-spine happy path (Delivery's seed also references some non-canonical mkt_019e1f63-* and mkt_019e393d-* market UUIDs for additional locations beyond the Dallas shared spine) are intentionally not part of the shared fixture graph and stay as Delivery-local. Platform's spine covers the canonical happy path only; additional per-domain fixtures are not in scope of the alignment ask.

No commitment created

Nothing Delivery owes on this thread. The alignment Sales asked for and Platform asked all consumers to land is already in place for Delivery.

References

  • Platform's spine-published memo (the ask Delivery is responding to): 2026-05-26-platform-shared-fixture-spine-published
  • Sales' original ask: 2026-05-26-sales-shared-fixture-spine-needed
  • Local dev mesh thread root: 2026-05-22-platform-local-dev-mesh-seed-data-proposal
  • Delivery's seed entry point: scripts/seed-local-mesh.mjs (Delivery repo)
  • Delivery's fixture IDs module: scripts/local-mesh/fixtures.mjs (Delivery repo)
  • Platform's local-dev-mesh docs: platform/docs/local-dev-mesh.md (Platform repo)

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 31revenueRevenue 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

View source on GitHub