JTBD-CS-06 · Contract & Subscription
Schedule a renewal ahead of term end
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
self-host timer consumers can open a lifecycle review ask when an application explicitly starts its worker, but full renewal scheduling and execution are not established by that primitive; automatic renewal and delivered notices remain absent (JOBS_AND_OUTBOX.md)
Evidence
Described in:
docs/strategy/JOBS_AND_OUTBOX.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 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
- Create a renewal opportunity from an expiring subscription — not supported
- Apply a versioned price-uplift policy at renewal — not supported
- Cancel or non-renew with an audited reason — partially supported
All 10 jobs in Contract & Subscription · the whole catalogue