JTBD-10 · CRM JTBD validation matrix

Manage contracts and renewals

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

contract activation, human renewal intent and governed successor execution exist, retaining signed-term provenance and immutable lineage. Timer consumers can open lifecycle-review asks when an application explicitly starts its worker. They do not automatically renew, cancel, bill or notify; historical contracts are not edited.

Evidence

Proved by these tests, which run on every push:

tests/contracts-activation-e2e.test.jstests/lifecycle-amendment-execution-e2e.test.jstests/workflow.test.js

Described in:

docs/CONTRACT_ACTIVATION.mddocs/RENEWAL_AMENDMENT.md

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 ships no authentication, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.

Other jobs in CRM JTBD validation matrix

Manage a custom CRM business object end to end — validated end to end
Associate a generated CRM record with another generated CRM record — validated end to end
Request commercial approval on a deal — validated end to end
Manage a deal through pipeline stages — validated end to end
Capture a lead — validated end to end
Qualify (or disqualify) a lead — validated end to end
Convert a qualified lead into Company, Contact and Opportunity — validated end to end
Manage a custom object with an approval rule — partially supported

All 17 jobs in CRM JTBD validation matrix · the whole catalogue