What has changed since

This site is dated on purpose. When the field moves, the movement is recorded here and the registry entry it affects is corrected — rather than a chapter being quietly rewritten.

How a change gets made

Three steps, in this order, and the order is the point:

Correct the registry. A new figure, a revised claim, a company that stopped operating the way it said it did — that is an edit to _data/landscape.yml or _data/sources.yml, with a new as_of date and its own source. A build validator refuses the change if the date is missing, the tier is unknown, or the source does not resolve.
Record the revision here, naming what it affects. Entries are appended, never edited, so the trail of what this site used to claim stays readable.
Touch a chapter only if the argument changed. Most developments do not change the argument. If a station has to be rewritten, that is itself worth saying out loud in the entry — it means something structural moved, not just a number.

The log

Baseline established

2026-07-24 · affects the whole registry

The state of the field as of July 2026, fixed as the baseline every later entry will be measured against: 28 sources, 16 landscape entries, and a validator that refuses any figure without an as-of date and a resolving source.

Three things in this baseline are unusually likely to move, and are worth watching first: the autonomy level of any operation currently listed at L4, because the interesting question is whether any of them removes its merge gate; the review-cost figures, which are model-priced and therefore volatile; and the productivity evidence, which is currently marked contested and could become settled in either direction.