JTBD-DC-04 · Design-to-CRM
Replace a component without forking the Admin
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
the ADR-009 override seam exists and carries the pipeline board and the quote/signature view — but it is an internal seam with no declared contract, registry or plugin path
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 Design-to-CRM
- Apply a brand's colors and typography — not supported
- Choose and group Admin navigation — not supported
- Control field order, sections and responsive layout — not supported
- Generate a CRM UI from a Figma file or screenshot — not supported
- Prove the UI still matches its design after a change — not supported
- Meet a stated accessibility bar — not supported