The argument
Find the High-Density Wack
Wack Density measures how many assumptions, exceptions, ownership gaps, and evidence dependencies converge around one component or process.
The field pattern
A payment-support subnet contains a legacy appliance, a vendor tunnel, a shared administrator account, an expired exception, a manual log export, and a diagram last updated before the migration. Each item has a separate explanation. The concentration is the risk signal.
Why it matters
Density helps prioritize. A single odd configuration with a clear owner and test may be manageable. A location where scope assumptions, access paths, vendor dependencies, and evidence gaps overlap is more likely to produce cascading uncertainty.
High-density areas also distort sampling and assessment planning. More variants and exceptions demand a more deliberate understanding of the population before anyone can choose representative evidence.
Questions that expose the Wack
- Where do the most exceptions and manual steps converge?
- Which component appears in the most control narratives?
- Where do ownership and evidence both become ambiguous?
- Which area creates the most follow-up questions per answer?