CRM job catalogue
Lead Intelligence & Routing
Milestone 9 — implemented for the local slice, ADR-015
9 jobs in this area. 4 validated end to end, 4 partially supported, 1 not supported.
validated end to end An automated test or a checked-in example proves the whole job. This is the only status that counts as evidence.
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.
technically supported The primitives exist but no test proves the job end to end, so it is not claimed as working.
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.
JTBD-LI-01 · Enrich a Lead from external sources with snapshot + provenance
validated end to end
with a deterministic fixture provider behind the real provider contract — a real paid external provider is explicitly NOT validated (needs human-approved credentials)
JTBD-LI-02 · Calculate an explainable lead score
validated end to end
versioned model → ScoreRun + per-rule contributions; reproducible for identical inputs; bounds clamped
JTBD-LI-03 · Prioritize Leads by score
partially supported
the managed score exists on every scored lead; no sorted/prioritized list surface exists yet
JTBD-LI-04 · Route a Lead automatically under a published policy
validated end to end
versioned policy → RoutingRun (policy + target-set fingerprints) + per-target route-evaluation evidence + Assignment history; deterministic tie-break; fallback queue;…
JTBD-LI-05 · Use sales capacity and availability in routing
partially supported
declared capacity against ACTIVE workload is enforced (full target excluded; slot released when a lead converts/disqualifies — tested); real availability/calendar data is NOT…
JTBD-LI-06 · Manually reassign with permission and reason
not supported
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-LI-07 · Version and publish a scoring/routing policy
validated end to end
narrow wording: publication = code-first registration at startup; each version's fingerprint is persisted in definition_versions; an edited registered version stops the app; no…
JTBD-LI-08 · Roll back a policy to an earlier version
partially supported
the mechanism is proven (a new version derived from an earlier definition registers cleanly; history immutable) but no end-to-end starter flow routes with a rolled-back version yet
JTBD-LI-09 · Reproduce a historical routing decision exactly
partially supported
runs persist model/policy identity + declared fingerprints, target-set fingerprint, per-target evaluation evidence (in/out, reason, load, capacity, priority) and fingerprints of…
What a status here does not mean
These statuses describe this repository at this commit. None of them implies the framework is deployable: there is no authentication, tenancy or RBAC, so it is local-development-only whatever any row says. Every claim and every limitation is on one page.