Answer
Does it send renewal reminders or run anything on a schedule?
Durable jobs, a transactional outbox and scheduled asks exist for self-hosted applications that explicitly start a worker. Nothing autostarts; a timer opens an ask, never makes a decision, and no managed worker service or recurrence is included (L-04). Supported timers can open Work, approval, lifecycle-review and service-SLA asks when composed; they do not automatically renew a contract, approve a decision or deliver a notification. Contract autoRenew and notice metadata alone starts nothing (C-10); no email/calendar adapter ships (L-05).
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-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.mdC-06
A lead is captured, scored, routed, qualified and converted into Company, Contact and Opportunity through explicit actions, each one atomic and audited.
LimitEnrichment runs against a fixture provider — no real external data source is wired. The Lead model is the starter's, not a built-in core module.
JTBD-04, JTBD-05, JTBD-05b, JTBD-LI-01, JTBD-LI-02, JTBD-LI-04tests/lead-qualification-e2e.test.jstests/lead-conversion-e2e.test.jstests/lead-intelligence-e2e.test.jsdocs/LEAD_INTELLIGENCE.mdL-04 · Timers exist; a service that runs them for you does not.
Durable jobs, a transactional outbox and scheduled asks exist for self-hosted applications that explicitly start a worker. Nothing autostarts; a timer opens an ask, never makes a decision, and no managed worker service or recurrence is included.
JTBD-07, JTBD-10docs/strategy/JOBS_AND_OUTBOX.mdL-05 · No email, calendar or marketing integrations.
An in-memory notification provider contract exists. MK1 marketing records supplied funnel observations and human-reviewed proposals only; it has no sending, publishing or spending path.
JTBD-14tests/marketing-no-external-effect.test.jstests/marketing-e2e.test.jsdocs/strategy/INTEGRATION_RUNTIME.mdWhere 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.