Accounts reviewed
139
Distinct synthetic accounts with evidence
Operations
Source-system evidence, operating dependencies, and transition-state workload.
Ready/cohort rate
32.8%
Records marked ready for a cohort path
Average complexity
4.6
1-7 transition complexity score
Unknown-usage gaps
25
Evidence where unknown cannot be treated as unused
High-risk integration share
62.5%
Integration records requiring rework
Transition states
6
Distinct T0-T6 states represented
Evidence source mix
| Source | Records | Share |
|---|---|---|
| capability | 43 | 23.9% |
| account | 41 | 22.8% |
| billing | 32 | 17.8% |
| integration | 32 | 17.8% |
| readiness | 32 | 17.8% |
high
Unknown usage blocks confident wave assignment
Records with missing tracking are treated as measurement gaps, not unused capabilities.
25 supporting records
- INT-2026-01-0008integration · 2026-01-01
Traffic exists but cannot be attributed to a known integration surface.
- ACCTREC-2026-01-0024account · 2026-01-02
Low recent activity cannot be interpreted because usage tracking is missing.
- ACCTREC-2026-01-0040account · 2026-01-02
Low recent activity cannot be interpreted because usage tracking is missing.
medium
Billing continuity needs a single-system rule
Accounts with active revenue or billing dependencies need explicit ownership before state changes.
20 supporting records
- BILL-2026-01-0005billing · 2026-01-05
Both platforms may be active, but one billing owner has not been assigned.
- BILL-2026-01-0027billing · 2026-01-06
A third party pays account fees and must be preserved through cutover.
- BILL-2026-01-0011billing · 2026-01-13
A third party pays account fees and must be preserved through cutover.