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

CRM job catalogue

Agent experience

AX0–AX5, cross-cutting

10 jobs in this area. 2 validated end to end, 4 partially supported, 4 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-AX-01 · Discover installed packages, capabilities and policies

validated end to end

crm app inspect [--json] (AX1) answers it in one deterministic document: the installed package graph with its five distinct version axes, the resolved capability graph including…

tests/app-inspect.test.js

JTBD-AX-02 · Extend the CRM for a goal without patching the kernel

validated end to end

the package contract: a customer-authored package attaches, works and detaches with every kernel file fingerprinted unchanged (JTBD-PK-01/PK-02). A record that must gain a field…

JTBD-AX-03 · Turn a business objective into a reviewable solution plan

partially supported

AX2: solutionPlanContract: 1 with a revision and a canonical fingerprint, six decision types mapped to the repository's own hierarchy, six evidence categories with resolving…

tests/solution-plan.test.js

JTBD-AX-04 · Build the solution as checked-in, customer-owned source

partially supported

true for modules, actions, policies, packages and Admin views that exist today; the analytics and campaign parts of a typical funnel goal cannot be built at all

JTBD-AX-05 · Verify the solution against defined acceptance

partially supported

Quality Gates, crm package validate, the test suites, the clean-clone run and the JTBD matrix are real and enforced; there is no automated goal-to-acceptance runner (AX3)

JTBD-AX-06 · Report unavailable capabilities honestly

partially supported

the JTBD matrix and package metadata make the honest answer available; nothing enforces that an agent uses it, which is why the Skill states it as a rule

JTBD-AX-07 · Analyse a funnel and identify a drop from a goal

not supported

needs Analytics Studio and a funnel primitive

JTBD-AX-08 · Propose an optimization campaign from an insight

not supported

MK1; no Campaign Proposal object exists

JTBD-AX-09 · Deploy, observe and fix a solution in production

not supported

AX4; hard-gated by the Production Spine and Cloud

JTBD-AX-10 · Close the loop: measure, learn, propose the next version

not supported

AX5; needs Marketing, Analytics, Data Governance and Durable Automation

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