JTBD-CM-04 · Communications
Schedule and track a follow-up
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.
What the catalogue records
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 partial: no recurrence, notification delivery, automatic assignment or managed worker service. See tests/work-operations-e2e.test.js, tests/work-operations-evidence.test.js, tests/work-provenance-and-actor.test.js, tests/work-source-key-stability.test.js and tests/spine-v3c-timer-consumers-postgresql.test.js.
Evidence
Proved by these tests, which run on every push:
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.jsWhat this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework ships no authentication, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Communications
- Sync email with CRM records — not supported
- Sync calendar events — not supported
- Log meetings and calls — not supported
- Honor unsubscribe and communication preferences — not supported