JTBD-DS-02 · Delivery & Service
Create a Commessa / Delivery Project from an Order
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
one Delivery Project per activated contract, with one work package per delivery obligation and a milestone plan, each carrying its own snapshot; a project is created from the Contract rather than directly from the Order. M14a adds execution: the project starts, its work packages start, block with a stated reason, resume and complete, and it closes only over completed work — tests/delivery-execution-e2e.test.js. Still no percent complete, scheduling, staffing, cost or billing
Evidence
Proved by this test, which run on every push:
tests/delivery-execution-e2e.test.jsWhat 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
- Involve a third-party delivery partner (engagement, role, scope) — partially supported
- Restrict partner access to assigned work only — not supported
- Manage milestones and deliverables — partially 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