accountCount from listHosts could overcount, which is the correction the feasibility work applied to get 19.4M from 22.7M. Checked directly against a PDS: enoki.us-east reports accountCount 214,128 and its own listRepos returns at least 201,000. So accountCount is close to real repo count, and if anything 19.4M was conservative -- the target is near 22.8M. The same check disproved a reading that nearly reversed the correction. Summing Stream's /status hosts tab gives 3.80M repos across hosts whose accountCount totals 17.3M, a ratio of 0.220. Taken at face value that implies a ~5.0M crawlable network and would have appeared to vindicate the wrong indigo denominator. It is an artifact: Stream's per-host counts are what the global listRepos walk has reached so far, not host totals. Stream has enumerated 94,044 of enoki's ~214,000 -- 44% of one host. Recorded that any per-host figure on /status is walk-progress and must never be read as a host total. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>