Pre-launch. Not deployable to production. This page states what the tests prove and what is missing — nothing else.

CRM job catalogue

CRM JTBD validation matrix

17 jobs in this area. 8 validated end to end, 4 partially supported, 5 not supported.

validated end to end An automated test or a checked-in example proves the whole job. This is the only status that counts as evidence.

partially supported Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.

technically supported The primitives exist but no test proves the job end to end, so it is not claimed as working.

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.

JTBD-01 · Manage a custom CRM business object end to end

validated end to end

create the object type, then list/create/view/edit its records through the Admin.

tests/admin-core.test.jstests/admin-modules.test.jstests/generated-api-e2e.test.jstests/module-factory-e2e.test.jsdocs/ADMIN.mddocs/ADMIN_SMOKE.md

JTBD-01b · Associate a generated CRM record with another generated CRM record

validated end to end

(Milestone 5), for generated-to-generated many-to-one references only.

tests/admin-modules.test.jstests/module-factory.test.jstests/reference-fields-e2e.test.jstests/reference-resolver.test.jsdocs/MODULE_FACTORY.md

JTBD-02 · Request commercial approval on a deal

validated end to end

(Milestone 0), for the built-in renewal object.

tests/api.test.jstests/workflow.test.js

JTBD-03 · Manage a deal through pipeline stages

validated end to end

(Milestone 8) for code-first pipelines on the built-in Opportunity module. The legacy fixed stage enum remains what the renewal-approval policy runs on (unchanged evidence:…

tests/admin-pipeline.test.jstests/opportunity-pipeline-e2e.test.jstests/pipeline-contract.test.jstests/workflow.test.jsdocs/ADMIN_SMOKE.md

JTBD-04 · Capture a lead

validated end to end

(Milestone 6), for the starter's Lead model.

tests/lead-qualification-e2e.test.jsdocs/ADMIN_SMOKE.md

JTBD-05 · Qualify (or disqualify) a lead

validated end to end

(Milestone 6), for the starter's qualify/disqualify actions.

tests/action-contract.test.jstests/action-runtime-semantics.test.jstests/admin-actions.test.jstests/lead-qualification-e2e.test.jsdocs/ADMIN_SMOKE.md

JTBD-05b · Convert a qualified lead into Company, Contact and Opportunity

validated end to end

(Milestone 7), for the starter's convert action.

tests/action-contract.test.jstests/admin-actions.test.jstests/lead-conversion-e2e.test.jsdocs/ADMIN_SMOKE.md

JTBD-06 · Manage a custom object with an approval rule

partially supported

generated CRUD is validated (JTBD-01), but the factory does not yet generate workflows/approvals for custom objects.

JTBD-07 · Schedule next actions / follow-ups

partially supported

narrowly: the first follow-up Task is created as part of Lead qualification (Milestone 6). There is still no reusable task engine, no scheduling/delayed-workflow primitive, no…

tests/lead-qualification-e2e.test.js

JTBD-08 · Hand off a won deal

validated end to end

superseded by JTBD-DS-01, which is the current row for this job and carries its evidence. This row is kept because "hand off a won deal" is the phrasing a reader or an agent…

tests/contracts-activation-e2e.test.jstests/delivery-execution-e2e.test.jstests/delivery-handover-e2e.test.js

JTBD-09 · Onboard a customer

not supported

no checklist/onboarding primitives.

JTBD-10 · Manage contracts and renewals

partially supported

a contract can now be activated from a signed Order with an explicit term (M12), and the renewal-approval workflow slice is validated. Renewal itself is not supported: auto-renew…

tests/contracts-activation-e2e.test.jstests/workflow.test.jsdocs/CONTRACT_ACTIVATION.md

JTBD-11 · Identify churn risk

not supported

no health-scoring/activity primitives.

JTBD-12 · Identify upsell

not supported

no usage/entitlement primitives.

JTBD-13 · Report pipeline

partially supported

data is queryable via API/SDK and the dashboard shows counts; no reporting/aggregation surface for generated modules.

JTBD-14 · Integrate email / calendar / marketing

not supported

only an in-memory notification provider contract exists; no email/calendar/marketing adapters.

JTBD-15 · Enforce team / tenant permissions

not supported

no authentication, tenancy or RBAC. The server is local-development-only. This is a hard prerequisite before any remote exposure.

What a status here does not mean

These statuses describe this repository at this commit. None of them implies the framework is deployable: there is no authentication, tenancy or RBAC, so it is local-development-only whatever any row says. Every claim and every limitation is on one page.

All 149 catalogued jobs · /jobs.json · the claims ledger