Accounts reviewed
168
Distinct synthetic accounts with evidence
Operations
Source-system evidence, operating dependencies, and transition-state workload.
Ready/cohort rate
35.0%
Records marked ready for a cohort path
Average complexity
4.5
1-7 transition complexity score
Unknown-usage gaps
33
Evidence where unknown cannot be treated as unused
High-risk integration share
60.5%
Integration records requiring rework
Transition states
6
Distinct T0-T6 states represented
Evidence source mix
| Source | Records | Share |
|---|---|---|
| capability | 57 | 23.8% |
| account | 54 | 22.5% |
| billing | 43 | 17.9% |
| integration | 43 | 17.9% |
| readiness | 43 | 17.9% |
high
Unknown usage blocks confident wave assignment
Records with missing tracking are treated as measurement gaps, not unused capabilities.
33 supporting records
- INT-2026-03-0040integration · 2026-03-02
Traffic exists but cannot be attributed to a known integration surface.
- ACCTREC-2026-03-0016account · 2026-03-03
Low recent activity cannot be interpreted because usage tracking is missing.
- CAP-2026-03-0009capability · 2026-03-03
Capability is enabled by default but usage tracking is absent.
medium
Billing continuity needs a single-system rule
Accounts with active revenue or billing dependencies need explicit ownership before state changes.
26 supporting records
- BILL-2026-03-0003billing · 2026-03-01
A third party pays account fees and must be preserved through cutover.
- BILL-2026-03-0004billing · 2026-03-02
A third party pays account fees and must be preserved through cutover.
- BILL-2026-03-0023billing · 2026-03-02
Both platforms may be active, but one billing owner has not been assigned.