More values as of today current totals that do not follow the river's date
Commits per family per month, as a table
A map of the work,
in the owner's words.
The topic map at the end of the READMEs, opened up: pick a topic, then a crate, for what it is, how it is used and how it is tested.
Every day,
something takes shape.
Scrub through the year. Follow the implementation and the work that verifies it.
Small pieces.
Whole systems.
Drag to roam, pinch or scroll to zoom. Select any tile to open its neighbourhood — contents, references, and what references it back.
Pillar height ∝ log production lines · bands: family / tests / docs · cap = published on crates.io · translucent = present today; no dated origin · outlined platform = hard fork (includes upstream source)
Current inventory snapshots · manifest references are name matches across the catalogue, not a resolved dependency graph
Every repo
gets a card.
Codecs first — one card per progress-scope repository. All-branch commits this year; stock includes inherited code; completion is not inferred.
Who uses it,
measured.
Downloads, dependents, stars and licenses from the registries themselves, captured weekly so the history outlives their windows.
crates.io downloads per day
Most downloaded crates
NuGet packages
The frontier
is in the details.
Compression comparisons belong to a specific corpus, metric, encoder revision, and set of conditions.
Fewer bits for the same picture.
Drag a box to zoom, scroll or pinch to zoom, double-click to reset.
Testing at scale.
The machines
behind the work.
Rented GPUs and servers from their billing records (cost left out), the home fleet's measured capacity, and what the AI services cost, from the owner's books.
Rented
Home fleet
AI services
Numbers with
a paper trail.
This page regenerates from a deterministic inventory. Each collected fact keeps its source; interpretations keep their rationale and revision history. Unknown quantities stay unknown.
Still collecting
Counting rules and current limits
Python is counted as test code. Rust test-only items, including inline cfg(test) modules, are classified separately. LOC is a stock measure; additions and removals describe activity. Commits, test cases, test executions, sessions, and prompts are distinct counts. Only collected sources contribute. Third-party and generated code are accounted for separately.