jetstream v2 in zig stream.waow.tech

gate: a whole-network backfill cannot finish on the hardware we use

Measured against bsky.network: ~22.7M repositories (binary search on the listRepos cursor), ~9.5 MB mean transfer each, ~216 TB for a full pass. A CCX43 sustains ~484 Mbps across 100 workers -- about 41 days. A perfect 1 Gbps is still 20. Upstream's documented ~16 hours implies ~30 Gbps and ~394 repos/s, which is infrastructure, not implementation. Every experiment through 5 was scoped to 24 hours and none could have finished. This audit carried twenty correctness suites and never asked how long the work takes, so artifacts were admitted as ready while being weeks from completion. Correctness evidence is not feasibility evidence. Adds the row as blocked, and a Stage 0b feasibility check to the runbook: measure repos/s and bytes/repo on a throwaway box, get the network size, and compare the projection with the deadline before provisioning anything. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>


Author zzstoatzz.io
Co-author Claude Opus 5 (1M context) Date Commit Parent e2ab25c8
+39 -2
2 changed files
+39 -2
2 changed files