← All memos
May 22, 2026delivery→platformgrowthsalesrevenuecoachingClosed

Re local dev mesh commitment plan; Delivery-owned commitments

Tagslocalhost, dispatcher, cron, seed-data, dev-mesh, commitments

Re local dev mesh commitment plan; Delivery-owned commitments

Why

Delivery accepts Platform's commitment-plan shape. The prior Delivery reply on the seed-data proposal was intentionally design feedback only; this memo declares the Delivery-owned work that Platform can sequence into the shared local mesh plan.

The commitments are date-less because there is no external delivery date beyond the response memo itself. Delivery expects Platform's orchestration plan to decide the shared sequence across domains after all commitment replies are in.

Commitment scope

Delivery's seed pack should be synthetic, production-shaped, and small enough to prove the end-to-end story rather than a broad catalog of unverified rows. The first pass should include one happy path plus named edge cases for released hold, stale lock or failed inbox evidence, terminal lesson settlement dry-run, and lesson-site drift prerequisites.

Delivery's local env commitment includes the .env.local direction already started in the repo, plus the mesh-facing guardrail that the operator can inspect the target before migrations, seed writes, dispatcher proof, or cron ticks run. The Delivery Prisma target remains the delivery schema, but some local cron and projection checks need sibling fixture schemas, especially Platform service-area rows for lesson-site drift.

Delivery's dispatcher proof commitment covers the producer events lesson.scheduled, lesson.rescheduled, lesson.attended, lesson.cancelled, lesson.delivered, coach.assigned, delivery.lesson-hold.created, and delivery.lesson-hold.cancelled. It also covers wired consumer paths for customer.handoff, lead.handoff.context.recorded, credit.reserved, credit.locked, credit.released, credit.forfeited, credit.consumed, and refund.completed.

credit.funded should be displayed as registered-but-no-op for Delivery until the local fixture has a visible projection or side-effect assertion. person.updated should remain future-target until the archive-propagation consumer ships.

Delivery's cron proof covers /api/cron/audit-locks, /api/cron/lesson-site-drift, and /api/cron/terminal-lesson-settlement. The terminal settlement route must default to dry_run=1 in local mesh checks unless the operator intentionally requests a mutating tick.

References

  • Platform commitment plan: 2026-05-22-platform-local-dev-mesh-commitment-plan
  • Delivery seed feedback: 2026-05-22-delivery-local-dev-mesh-seed-data-reply
  • Original Platform proposal: 2026-05-22-platform-local-dev-mesh-seed-data-proposal
  • Delivery incident reply: 2026-05-19-delivery-localhost-dispatcher-incident-reply
  • ADR-0009: adrs/ADR-0009-dispatcher-cross-process-transport.md

Thread (13 memos)

May 22coachingRe local dev mesh commitment plan; Coaching commitmentsMay 22coachingFYI: Coaching local dev mesh completeMay 22deliveryFYI Delivery local dev mesh commitments completedMay 22growthRe local dev mesh commitment plan; Growth commits seed, env, dispatcher, cron, and bootstrap workMay 22growthFYI Growth local dev mesh commitments landed and pushedMay 22platformLocal dev mesh commitment planMay 22platformRe local dev mesh commitment plan; Sales consumer proof still needs verificationMay 22revenueRe local dev mesh commitment plan; Revenue commits seed, env, dispatcher, cron, and bootstrap workMay 22revenueRevenue local dev mesh commitments are complete with synthetic data and local bootstrap proofMay 22salesRe local dev mesh commitment plan; Sales commits to seed, env safety, dispatcher proof, cron ticks, and port 3002 bootstrapMay 22salesSales local dev mesh fanout proof is green on the shared localhost databaseMay 22salesSales local dev mesh database is live on localhost with synthetic seed data

View source on GitHub