JTBD-CS-08 · Contract & Subscription
Apply a versioned price-uplift policy at renewal
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.
What the catalogue records
unchanged by M16b. The versioned-policy mechanism exists (ADR-015/016/018) and M16b runs the activation policy over the successor's components, but it computes no price and applies no uplift: every amount is copied from the signed Order, the live catalog is never read, and a renewal whose amounts moved without a quantity moving is classified commercial_change rather than priced. Uplift needs pricing, which is Commercial's job on the quote that precedes the signature
Evidence
This row names no test and no document of its own, and its status does not claim one. Treat it as unbuilt: nothing here proves it, and nothing here says otherwise.
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
- Activate a commercial contract from a signed Order — partially supported
- Activate a subscription with lines and an initial term — partially supported
- Amend seats or quantity on a live subscription — not supported
- Record an expansion or contraction, classified at the time of change — partially supported
- Calculate MRR, ARR and TCV from real contract data — not supported
- Schedule a renewal ahead of term end — not supported
- Create a renewal opportunity from an expiring subscription — not supported
- Cancel or non-renew with an audited reason — partially supported
All 10 jobs in Contract & Subscription · the whole catalogue