JTBD-DO-08 · Data operations
See a unified activity timeline for a record
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 v1 (ADR-030) adds an append-only Activity timeline per subject, with a closed four-entry vocabulary, rendered oldest-first in the Admin — tests/work-operations-e2e.test.js, tests/admin-work.test.js. It is not a unified customer timeline: it covers only what Work itself recorded, Service's support-case-activity stays domain-specific, Delivery history is not aggregated, marketing and communications do not exist at all, and no email, call, meeting or audit row appears on it. Confirmed partially supported by human decision on that wording; no other row is promoted by inheritance from it
Evidence
Proved by these tests, which run on every push:
tests/admin-work.test.jstests/work-operations-e2e.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 is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Data operations
- Import records from CSV — not supported
- Detect duplicates on import or entry — not supported
- Merge two Companies or Contacts — not supported
- Export records — not supported
- Bulk update a set of records — not supported
- Save and share a filtered view — not supported
- Search across modules — not supported
- Attach notes or files to a record — not supported