JTBD-DS-05 · Delivery & Service
Manage milestones and deliverables
partially supported. Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.
What the catalogue records
a canonical, ordered milestone plan is created with the project and linked to its work packages, and M14a lets a human start and complete one under a running project. M14b2 adds Deliverables as real objects: planned against a work package and optionally a milestone, completed only from a work package the server says is finished, and immutable once complete. Still nothing schedules or bills a milestone, it is never a contractual milestone, and no file or binary is stored
Evidence
This row carries no test path of its own in the structured index. The matrix records the evidence for it in a block shared with neighbouring rows, which jobs.json does not split per row — so read docs/benchmarks/CRM_JTBD_MATRIX.md for it. The status above was set from that evidence, not from its absence.
What this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Delivery & Service
- Hand over a won Deal to delivery — validated end to end
- Create a Commessa / Delivery Project from an Order — partially supported
- Involve a third-party delivery partner (engagement, role, scope) — partially supported
- Restrict partner access to assigned work only — not supported
- Track hours and costs on delivery — validated end to end
- Calculate delivery margin (forecast vs actual) — partially supported
- Manage a Change Request with impact and approval — validated end to end
- Collect customer acceptance on deliverables — partially supported