JTBD-DO-03 · Data operations
Merge two Companies or Contacts
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
on a deliberately narrow reading: a logical canonical merge. A human — never an agent, never without a reason — records that two records are one customer, producing a canonical/alias cluster with the deciding identity and reason on every link. After it, both records still exist byte-identical, both still resolve, both read one consolidated profile, and neither a decided candidate nor an already-clustered record can be silently re-decided or re-parented. Still partial, and the row's own word is again the gap: there is no physical merge. Nothing is deleted, no reference is re-pointed, no field is survivorship-resolved and nothing is un-mergeable by audit — an operator who wants two rows to become one row does not get that here, and it is deliberately deferred to Customer Data Operations v2
Evidence
This row carries no test path of its own in the structured index. The matrix records the evidence for it in a block shared with neighbouring rows, which jobs.json does not split per row — so read docs/benchmarks/CRM_JTBD_MATRIX.md for it. The status above was set from that evidence, not from its absence.
What 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 — partially supported
- Detect duplicates on import or entry — partially 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
- See a unified activity timeline for a record — partially supported
- Attach notes or files to a record — not supported