The entangled core, precisely
Every system is partitioned by how many binding mechanisms apply: a pinning dependency, a WCF surface, or a shared core database. The partition is computed by rule from the current dataset, so it stays correct on every assessment run (counts can differ slightly from the whitepaper narrative, which was derived by hand). The binding runs through ten points; cutting those releases whole populations at once.
kernel The kernel: 67 systems bound by two or more mechanisms
The entangled core properly so called. These systems cannot be modernised one ticket at a time; they move as groups, sequenced by the programme stages.
loosely attached The loosely attached ring: 59 systems held by a single thread
Each of these touches exactly one binding mechanism, and each thread has a known cut. Most fall out of the core automatically when stage 2 cuts the binding points.
loose Already loose: 87 systems
No binding mechanisms apply. Modern leaf systems here are in effect already split out; legacy leaf systems split out by retirement rather than migration.