Redacted excerpt; full evidence withheld.

$ cd <guest-path> && ls -la && cat README.md | head -c 6000; id -u; python3 --version
exit: 0
hundred 1-pixel slivers are noise, not information. Anything too thin to see is folded into one desaturated wedge in its parent's hue, carried out to the rim. Doing this only at the top level leaves the outer rings — which own most of the disc's area — almost entirely black.
- **Rings are dropped when they stop carrying data.** An outer ring covering less than ~35% of the circle costs more area than it earns, so it's removed and the remaining rings get thicker.

The treemap is the standard [squarified](https://www.win.tue.nl/~vanwijk/stm.pdf) algorithm (Bruls, Huizing & van Wijk), which favours near-square rectangles so small entries stay clickable.

## Accuracy

Getting disk numbers right on macOS takes more care than walking the tree:

- **Blocks, not bytes.** The default is `blocks × 512` — what deleting something would actually give back. Sparse files and APFS clones report far more apparent bytes than they occupy, which is why Finder and `du` so often disagree. <kbd>a</kbd> shows the other number.
[excerpt truncated]