JTBD-LI-06 · Lead Intelligence & Routing
Manually reassign with permission and reason
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.
What the catalogue records
the assignment record carries source/previousAssignmentId/reason as future data, but no override action exists and none may claim manager permissions before the Production Spine (JTBD-15)
Evidence
This row names no test and no document of its own, and its status does not claim one. Treat it as unbuilt: nothing here proves it, and nothing here says otherwise.
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 Lead Intelligence & Routing
- Enrich a Lead from external sources with snapshot + provenance — validated end to end
- Calculate an explainable lead score — validated end to end
- Prioritize Leads by score — partially supported
- Route a Lead automatically under a published policy — validated end to end
- Use sales capacity and availability in routing — partially supported
- Version and publish a scoring/routing policy — validated end to end
- Roll back a policy to an earlier version — partially supported
- Reproduce a historical routing decision exactly — partially supported
All 9 jobs in Lead Intelligence & Routing · the whole catalogue