CRM job catalogue
Communications
no milestone assigned
5 jobs in this area. 1 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-CM-01 · Sync email with CRM records
not supported
no email provider; needs the Integration Runtime
JTBD-CM-02 · Sync calendar events
not supported
no calendar provider
JTBD-CM-03 · Log meetings and calls
not supported
Work v1 adds a free-text note on a subject timeline, and that is all: there is no meeting, call, participant, duration, direction or outcome model, no calendar and no telephony.…
JTBD-CM-04 · Schedule and track a follow-up
partially supported
Work provides one reusable Task and Activity model. Self-host timer consumers can open scheduled Work asks through an explicitly started worker; dueAt alone starts nothing. Still…
tests/spine-v3c-timer-consumers-postgresql.test.jstests/work-operations-e2e.test.jstests/work-operations-evidence.test.jstests/work-provenance-and-actor.test.jstests/work-source-key-stability.test.jsJTBD-CM-05 · Honor unsubscribe and communication preferences
not supported
no preference or suppression model (DATA_GOVERNANCE.md)
docs/strategy/DATA_GOVERNANCE.mdWhat a status here does not mean
These statuses describe this repository at this commit. None of them implies the framework is deployable: no authentication ships, so a deployment must supply the verifier before anyone but you reaches it, whatever any row says. Every claim and every limitation is on one page.