CRM job catalogue
Delivery & Service
handover at M13, execution at M14a, economics at M14b1, and change, deliverables and acceptance at M14b2 — all merged; docs/DELIVERY_HANDOVER.md, docs/DELIVERY_ECONOMICS.md, docs/DELIVERY_CHANGE_ACCEPTANCE.md
12 jobs in this area. 3 validated end to end, 7 partially supported, 2 not supported.
validated end to end An automated test or a checked-in example proves the whole job. This is the only status that counts as evidence.
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.
technically supported The primitives exist but no test proves the job end to end, so it is not claimed as working.
not supported No implementation and no test. It would have to be built. This is the default status in the catalogue — a row moves out of it only when a test proves it.
JTBD-DS-01 · Hand over a won Deal to delivery
validated end to end
commercial-contract.create-delivery-handover (human actor only) turns the activated contract's pending delivery obligations into a planned Delivery Project with work packages and…
tests/delivery-handover-e2e.test.jsJTBD-DS-02 · Create a Commessa / Delivery Project from an Order
partially supported
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…
tests/delivery-execution-e2e.test.jsJTBD-DS-03 · Involve a third-party delivery partner (engagement, role, scope)
partially supported
at most one planned Partner Engagement per project, naming the partner, its role and the work packages it covers, required exactly when work is partner-delivered. It is a…
JTBD-DS-04 · Restrict partner access to assigned work only
not supported
requires RBAC/tenancy — hard-gated by the Production Spine (JTBD-15). M13 records a partner engagement; it grants no access to restrict
JTBD-DS-05 · Manage milestones and deliverables
partially supported
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…
JTBD-DS-06 · Track hours and costs on delivery
validated end to end
M14b1: append-only time and expense evidence on a running work package, costed server-side by a versioned fingerprinted policy at roundHalfUp(ratePerHourCents × minutes / 60). No…
tests/delivery-economics-e2e.test.jsJTBD-DS-07 · Calculate delivery margin (forecast vs actual)
partially supported
M14b1 produces a variance to the latest immutable plan version and a reproducible delivery contribution estimate — the latter only where every commercial input in that currency…
JTBD-DS-08 · Manage a Change Request with impact and approval
validated end to end
M14b2: a governed change request with a stated reason, decided exactly once by a human over a declared state table; approving a non-commercial replan creates an immutable…
tests/delivery-change-acceptance-e2e.test.jstests/delivery-change-acceptance-evidence.test.jstests/delivery-change-acceptance-integration.test.jsJTBD-DS-09 · Collect customer acceptance on deliverables
partially supported
M14b2: Deliverables gated on server-authoritative execution state, and an immutable Acceptance Request that freezes its exact scope with a SHA-256 fingerprint the evidence binds…
JTBD-DS-10 · Activate billing on accepted milestones
not supported
no billing-milestone primitives
JTBD-DS-11 · Activate a Service Contract with Entitlements and SLA
partially supported
M15 (open PR): a contract's pending Service Obligations are activated by a human into an operational Service Coverage with immutable Entitlements, under a versioned fingerprinted…
tests/admin-service.test.jstests/service-operations-e2e.test.jstests/service-operations-upgrade.test.jsdocs/ADMIN_SMOKE.mdJTBD-DS-12 · Manage support cases and escalation
partially supported
M15 (open PR): a Support Case recorded against an entitlement over an explicit five-state transition table, with append-only Case Activity, a first response stamped exactly once,…
What a status here does not mean
These statuses describe this repository at this commit. None of them implies the framework is deployable: there is no authentication, tenancy or RBAC, so it is local-development-only whatever any row says. Every claim and every limitation is on one page.