Re local dev mesh commitment plan; Sales commits to seed, env safety, dispatcher proof, cron ticks, and port 3002 bootstrap

Sales commitment response

Sales accepts Platform's commitment-plan shape and is declaring its own work in this memo's frontmatter. The commitments are date-less because there is no external deadline beyond the response memo itself. Sales will sequence the implementation with Platform's mesh runner work and the other domain seed packs.

The first pass should favor one complete, inspectable happy path over a broad fixture catalog. Sales' target path is a fake intake that becomes a fake Sales lead, gets worked through qualification and scheduling, enters close orchestration, receives Revenue and Delivery facts, and renders the downstream Coaching booking impact in the Workbench coverage drawer.

Scope details

The Sales seed pack will extend the existing Workbench seed posture. The existing npm run prisma:seed remains the install-time configuration seed. The mesh seed should be separate because it needs coordinated fixture ids across Growth, Platform, Revenue, Delivery, Coaching, and Sales.

The local env safety work is P1 because Sales currently has a sharp edge: prisma.config.ts and prisma/seed.ts load .env.local, then load .env with override enabled. If .env contains production DSNs, a developer can believe local configuration is protecting them while Prisma CLI or seed commands still use the remote database. Sales will either invert that precedence for local commands, require explicit mesh env injection, or add a hard guard that refuses remote DSNs in local setup.

The dispatcher proof commitment covers Sales' wired-now producer and consumer paths. Producers include lead.created, lead.stage.changed, lead.reached, lead.callback.scheduled, lead.attempt.exhausted, role.assigned, role.retired, lead.qualified, and lead.handoff.context.recorded. Consumers include intake.captured, intake.matched, intake.amended, person.updated, customer.handoff, credit.locked, credit.released, and platform.comms.inbound.

Sales will label geography.market.upserted, geography.market.archived, geography.service-area.upserted, and geography.service-area.archived as present in subscriber code but not wired through the current inbox switch unless Sales wires them before the mesh spec lands. Sales will label broader payment, refund, and credit lifecycle events that are in Sales scope but not currently dispatched through the webhook inbox as future-target, not validated.

The cron commitment covers the three vercel.json routes: /api/cron/missed-callbacks, /api/cron/intake-followup, and /api/cron/stage4-reminders. All require Authorization: Bearer <CRON_SECRET> locally. Sales will mark them as explicit manual ticks, not background localhost behavior.

References

• Platform commitment plan: 2026-05-22-platform-local-dev-mesh-commitment-plan
• Sales seed feedback: 2026-05-22-sales-local-dev-mesh-seed-data-feedback
• Sales cron config: sales/vercel.json
• Sales dispatcher inbox: sales/modules/dispatcher-inboxes/dispatcher-inboxes.service.ts
• Sales Prisma env loading: sales/prisma.config.ts and sales/prisma/seed.ts