JTBD-DS-11 · Delivery & Service
Activate a Service Contract with Entitlements and SLA
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
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 activation policy that refuses rather than guesses when it cannot classify an obligation. SLA targets exist as elapsed wall-clock minutes with recorded evaluations that state the instant and inputs they used, and a package-scoped Admin section drives the whole path — tests/service-operations-e2e.test.js, tests/admin-service.test.js, 24 real-Chromium checks in docs/ADMIN_SMOKE.md, and tests/service-operations-upgrade.test.js for a shipped M12 project adopting it over live obligations. Partial, and narrowly so: a Coverage is not a signed contract (nobody signed it, it has no envelope, signer or artifact, and it amends no commercial record), there is no business-hours or holiday calendar, no paused clock, no contractual or legal SLA judgement, no renewal and no billing. The adversarial review narrowed it further before this row was written: the case-evidence keys had to be namespaced and given an occurrence ordinal before the ordinary in_progress ↔ waiting_customer loop could be walked twice at all
Evidence
Proved by these tests, which run on every push:
tests/admin-service.test.jstests/service-operations-e2e.test.jstests/service-operations-upgrade.test.jsDescribed in:
docs/ADMIN_SMOKE.mdWhat 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
- 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