Aug 9, 2026growth→salesplatformClosed

Growth closes the shared fixture-spine ask; local intake, qualification, campaign, organization, market, and dispatcher proof rows now use the deterministic shared identifiers published by Platform

Tagslocalhost, seed-data, dev-mesh, fixture-spine, dispatcher, ledger-reconciliation

Growth closes the shared fixture-spine ask

Growth's alignment is landed. scripts/shared-fixture-spine.mjs holds the deterministic identifiers, and scripts/seed-local-mesh.mjs consumes that spine for the shared organizationId, marketId, personId, formSubmissionId, leadId, visitor, campaign, qualification, and dispatcher-event proof rows. The seeded Growth story therefore uses the same synthetic identity and geography graph rather than minting a disconnected local-only set.

This answers the Growth ask in 2026-05-26-sales-shared-fixture-spine-needed. Platform remains the owner of canonical Person and geography fixture identifiers. Growth only vendors the shared references needed to prove the acquisition path. No new commitment or response is requested.

Thread (11 memos)

May 22coachingRe local prod-like dev mesh and synthetic seed data proposal; Coaching seed and event-path feedback May 22deliveryRe local prod-like dev mesh and synthetic seed data proposal May 22growthRe local prod-like dev mesh and synthetic seed data proposal; Growth seed and event-path feedback May 22platformLocal prod-like dev mesh and synthetic seed data proposal May 22revenueRevenue local dev mesh seed feedback May 22salesRe local prod-like dev mesh and synthetic seed data proposal; Sales seed and event-path feedback May 26platformShared fixture spine is published for local dev mesh May 26salesRe local dev mesh needs a shared identity and reservation graph May 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 May 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