Answer

Does it cover what happens after a deal is signed?

Partly: verified signature evidence produces an immutable Order (C-09), activation creates a Contract, immutable version, Subscription and pending obligations (C-10), and delivery adds projects, work packages, milestones and append-only cost evidence (C-11, C-12). Terms frozen into the signed quote document retain signed-order provenance; legacy orders without signed terms can use explicitly labelled post-signature operational metadata. Operational dates are never promoted to signed terms. Governed renewal and amendment execution creates a successor agreement from its own signed Order, with immutable lineage and a derived line delta. Historical contracts and subscriptions are not edited. There is no automatic renewal, cancellation execution, billing or customer notification. Deliverables and recorded customer acceptance exist; acceptance is evidence recorded by a user actor, not an authenticated customer signature or permission to bill. Contribution estimates exclude recurring commercial inputs and are not revenue recognition or margin.

What the ledger says, word for word

Each entry below is copied from site/claims.json, where it is bound to the evidence that holds it — a test file, a document, or a named repository fact — and to the limitation that travels with it. The answer above summarises these; these are the claim.

C-09

A signature envelope produces verified events and a hashed signed artifact, and exactly one immutable Order is built from the approved quote version.

LimitA fixture signature provider with a test-only webhook key. No DocuSign, Adobe Sign or Dropbox Sign adapter exists, and the artifact hash is provider-reported rather than independently recomputed.

JTBD-CO-07tests/signature-order-e2e.test.jstests/signature-contract.test.jstests/admin-signature.test.jsdocs/SIGNATURE_ORDER.md

C-10

A signed Order activates into a Commercial Contract, an immutable contract version, a Subscription and explicitly pending delivery and service obligations — every component classified, never guessed.

LimitTerms frozen into the signed quote document retain signed-order provenance; legacy orders without signed terms can use explicitly labelled post-signature operational metadata. Operational dates are never promoted to signed terms. Governed renewal and amendment execution creates a successor agreement from its own signed Order, with immutable lineage and a derived line delta. Historical contracts and subscriptions are not edited. There is no automatic renewal, cancellation execution, billing or customer notification.

JTBD-CS-01, JTBD-CS-02tests/contracts-activation-e2e.test.jstests/contracts-contract.test.jstests/admin-contracts.test.jstests/lifecycle-amendment-execution-e2e.test.jstests/lifecycle-amendment-execution.test.jstests/signed-terms-e2e.test.jsdocs/CONTRACT_ACTIVATION.mddocs/RENEWAL_AMENDMENT.md

C-11

Pending obligations hand over into a Delivery Project with work packages, milestones and an optional partner — atomically, idempotently, and across a package boundary the kernel never learns about.

LimitIt hands work over and runs it through human-driven transitions. Nothing schedules, staffs, computes percent complete or bills. Deliverables and recorded customer acceptance exist as of M14b2, and acceptance there is evidence a user actor recorded — never an authenticated customer, a legal signature or authorization to bill.

JTBD-DS-01tests/delivery-handover-e2e.test.jstests/delivery-execution-e2e.test.jstests/admin-delivery.test.jsdocs/DELIVERY_HANDOVER.md

C-12

Delivery records what it consumed: append-only time and expense evidence, costed server-side by a versioned fingerprinted policy, with a reproducible contribution estimate grouped by currency.

LimitDeliberately not a margin: no revenue recognition, no cost of goods sold, no ARR/MRR/TCV, no annualization, no FX. A project carrying a recurring obligation returns no estimate at all and says why.

JTBD-DS-06, JTBD-DS-07tests/delivery-economics-e2e.test.jsdocs/DELIVERY_ECONOMICS.md

Where this stops

Nothing on this page implies deployment readiness. The framework ships no authentication verifier; authorization is framework-enforced; tenant isolation is one tenant per application instance, not shared-database row tenancy. Read the exact repository posture before deployment. Every claim and every limitation is on one page, and the questions this project refuses to answer are published beside them.