JTBD-CS-02 · Contract & Subscription

Activate a subscription with lines and an initial term

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 subscription per contract, with a line for every component whose commercial axis is subscription — including recurring components that also carry a service or delivery obligation, so no recurring commitment is lost. Its term inherits the signed Order snapshot when present, or explicitly reasoned operational metadata for a termless Order; the provenance remains visible. Still partial: activation creates commercial records, not billing, proration or cancellation. A future-dated subscription is scheduled; self-host timers can request lifecycle review but do not automatically activate or renew it. Governed amendment execution creates a separate successor agreement without modifying the existing subscription. Evidence: tests/signed-terms-e2e.test.js, tests/contracts-activation-e2e.test.js, tests/lifecycle-amendment-execution-e2e.test.js

Evidence

Proved by these tests, which run on every push:

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

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 Contract & Subscription

All 10 jobs in Contract & Subscription · the whole catalogue