The part that actually fails in practice
An Atlassian accountId, a ClickUp user id, a Trello member id and an ACF employee record are four different keys, and the match is never complete. Every project-tool integration meets this wall; most of them handle it by dropping the rows.
The rule (A-47): an unmatched person is never scored zero. Their lane-2 weight is set to zero and the remaining weights are renormalised, so the absence of a match costs them nothing. Scoring someone zero because an integration could not find them is the single most damaging bug this feature could ship — and it is the default behaviour of almost every tool that does this.
- JIRAacc_j93quocanh.nguyen23 work items · 4 Jul 2026 → 22 Sep 2026
no employee record — leaver, contractor, or a shared service account
- CLICKUPcu_9102TS Automation Bot118 work items · 1 Jun 2026 → 23 Sep 2026
looks like a service account, not a person — map to none
- CLICKUPcu_8844duc.pv19 work items · 6 Jul 2026 → 19 Sep 2026
probably Pham Van Duc (E-1044) — one click to confirm, and his lane-2 weight comes back
- Pham Van DucE-1044lane 2 → 0%, other lanes renormalised to 100%. Coverage 13%.team view
- Ly Minh KhoaE-3006lane 2 → 0%, other lanes renormalised to 100%. Coverage 27%.team view
Note what renormalising does to coverage: it falls, because a lane that was scorable is gone. The scorecard gets less defensible, not more — which is the honest consequence and the reason the mapping above is worth someone's ten minutes.