Read a complete amendment history

What the catalogue records

M16b records an immutable contract-succession row per amendment: source and successor contract, version, subscription and Order, the derived classification with its basis, the exact line delta, both terms with their provenance, the term continuity, the signed document hash, the deciding policy version and fingerprint, and who executed it when. Lineage is 1:1:1 and DB-enforced, so the chain is unambiguous. Partial: it is a successor chain, not a field-level amendment log — there is no in-place amendment to log — the chain is linear (one successor per agreement), and it starts at M16b: agreements succeeded before it exist have no lineage row and none is backfilled. Evidence: tests/lifecycle-amendment-execution-e2e.test.js, tests/lifecycle-amendment-execution.test.js, tests/admin-lifecycle.test.js, docs/RENEWAL_AMENDMENT.md

Evidence

Proved by these tests, which run on every push:

Described in:

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
• Apply a versioned price-uplift policy at renewal — not supported

All 10 jobs in Contract & Subscription · the whole catalogue