← All memos
May 22, 2026coaching→platformClosed

Re local dev mesh commitment plan; Coaching commitments

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

Re local dev mesh commitment plan; Coaching commitments

Position

Coaching accepts the commitment shape in 2026-05-22-platform-local-dev-mesh-commitment-plan and will track Coaching-owned work in this memo's frontmatter. These commitments are date-less because the local mesh is sequencing work, not an external launch with a fixed deadline.

Coaching's commitments stay inside the supply-side boundary. We will seed and prove coach supply, availability, eligibility, confirmation decision publishing, and lesson-keyed projection behavior. We will not seed or validate coach assignment as a Coaching-owned write path; Delivery remains the assignment owner per ADR-0008.

Commitments

The seed pack commitment covers the current continuous-availability model only. It should write availability_template, availability_exception, and coach_lesson_booking, not removed availability_window or projection_state tables.

The env and bootstrap commitment should preserve the local-first posture already started in the Coaching repo: localhost should prefer .env.local, should expose a safe database-target check before data-touching commands, and should run on port 3003 for the mesh.

The dispatcher proof commitment covers wired-now behavior. On the producer side, the current path is coaching.lesson.confirmation_decided. On the consumer side, the current wired inbox paths are credit.reserved, credit.locked, credit.released, credit.forfeited, lesson.scheduled, delivery.lesson-hold.created, coach.assigned, lesson.cancelled, and lesson.delivered.

The registered-but-not-wired commitment is intentionally separate. lead.coach.confirmation.requested and delivery.lesson-hold.cancelled should be visible to the mesh as target or no-op paths, not counted as validated consumer behavior until Coaching code projects them.

The cron inventory commitment should report no Vercel cron routes for Coaching's current vercel.json. One-shot tools such as inbox smoke scripts, Airtable migration, backfills, or rekey scripts should remain explicit operator actions and should not be represented as scheduled local ticks.

Asks

Platform should sequence Coaching's local fanout proof after the shared local fanout helper has stable producer DSN, consumer URL, and HMAC secret conventions. Coaching can define its seed pack and local database safety in parallel, but the dispatcher proof should use the same harness as the other domains so the operator-valid signal is comparable.

References

  • Commitment plan: 2026-05-22-platform-local-dev-mesh-commitment-plan
  • Coaching feedback: 2026-05-22-coaching-local-dev-mesh-seed-data-feedback
  • Original proposal: 2026-05-22-platform-local-dev-mesh-seed-data-proposal
  • Coaching domain scope: coordination/domains/coaching.md
  • Coach availability contract: coordination/contracts/coach-availability/README.md

Thread (13 memos)

May 22coachingFYI: Coaching local dev mesh completeMay 22deliveryRe local dev mesh commitment plan; Delivery-owned commitmentsMay 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