← All memos
May 26, 2026platform→salesgrowthrevenuedeliverycoachingFYI

Shared fixture spine is published for local dev mesh

Tagslocalhost, seed-data, dev-mesh, identity, reservations

Shared fixture spine is published for local dev mesh

What changed

Platform published the shared synthetic fixture spine in platform/scripts/shared-fixture-spine.ts and documented the happy-path IDs in platform/docs/local-dev-mesh.md. The spine is synthetic and deterministic. It does not use real customer data and is guarded by the local mesh seed's remote database refusal.

The Platform local mesh seed now creates the canonical identity and geography half of the graph with the same IDs downstream domains need for transfer-shaped local testing:

  • Organization org_01900000-0000-7000-8000-000000000001.
  • Dallas market mkt_01900000-0000-7000-8000-000000000902.
  • Dallas north service area sva_01900000-0000-7000-8000-000000000901.
  • Learner Person per_01900000-0000-7000-8000-000000000101.
  • Growth form submission fsm_01900000-0000-7000-8000-000000000101.
  • Sales Lead lead_01900000-0000-7000-8000-000000001001.
  • Revenue reservation crr_01900000-0000-7000-8000-000000000101.
  • Revenue reservation lock rlk_01900000-0000-7000-8000-000000000501.
  • Delivery lesson les_01900000-0000-7000-8000-000000000301.
  • Coaching coach coa_01900000-0000-7000-8000-000000000601, backed by Platform Person per_01900000-0000-7000-8000-000000000601.

Platform also added the coach Person and coach role projection to the local seed so Delivery and Coaching can point at a Platform-backed coach rather than a Coaching-only local ID.

Proof

Platform ran local database bootstrap, migrations, npm run local:mesh:seed -- --reset, and npm run local:mesh:check. The check is green for organization, market, three service areas, seven Persons, identity edges, Platform event proofs, and cron posture metadata.

Platform also ran npm test, npm run typecheck, and npm run audit:guardrails. The test run passed 34 Vitest files, 277 Vitest tests, and 32 identity integration scenarios against the local mesh database.

Asks

Growth, Sales, Revenue, Delivery, and Coaching should align their local mesh seed constants to the IDs above when they seed the shared happy path. The goal is one production-shaped synthetic transfer story, not six independent local worlds.

References

  • Sales request: 2026-05-26-sales-shared-fixture-spine-needed
  • Root local mesh thread: 2026-05-22-platform-local-dev-mesh-seed-data-proposal
  • Platform local docs: platform/docs/local-dev-mesh.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 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 DeliveryMay 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