Updates

This site is a snapshot with a maintenance plan. The chapters are written to survive; the dated snapshot pages are not, and this log is where the difference gets recorded.

1. 2026-07-26 publication amends: all pages

   First edition

   The site goes up: eight chapters, two dated snapshots, two case studies and the apparatus — register, glossary, this log.

   Where the material comes from. Two research documents assembled in July 2026: a survey of the field as of mid-2026, and a conceptual frame after Osmani and Horthy with an original darkening analysis attached. Both are in specs/ in the repository. The case studies draw on five pipeline repositories on the author’s machine and their retro reports, cited as workspace sources.

   What is deliberately absent. No generated artwork — the figures are inline SVG keyed to the palette. A generator that invents text on drawn signage is a fabrication surface, and a site arguing for verifiable claims should not carry one.

   What will date fastest, in order: the toolbox, then the field report, then chapter 6’s benchmark section. The concept chapters should survive; if they do not, that is the interesting failure and it belongs in this log.

How this site is kept current

The mechanics are deliberately boring, because the failure mode of a living document is that nobody can tell what changed.

• Source ids are immutable. An entry in the register keeps its id forever. Corrections edit the entry's fields or add a new entry; ids are never reused, because they are public anchors.
• This log is append-only. An update names what it amends and does not rewrite history. If a chapter's claim turns out to be wrong, the correction is a new entry that says so, not a silent edit.
• The dated pages carry a snapshot banner driven by one date in the site configuration, so the stamp cannot drift out of sync with itself.
• Every chapter carries a reviewed date in its rail. A chapter whose date is old has not been checked recently, which is a different statement from "is wrong" and a more useful one.
• The build enforces the citations. Adding a claim without a registered source fails the build, so the register cannot quietly fall behind the prose.

What would justify an update

Not every development is a change to this site. The bar, roughly:

• A snapshot page's table becomes false — an organisation moves level, a volume figure is superseded, a tool named here is discontinued.
• A contested source is resolved in either direction, or a vendor-reported figure gets independent measurement. Both change a tier, which is a one-line edit that propagates everywhere.
• Someone publishes a marginal catch rate — what a human gate still catches after the machines pass. Chapter 6 argues that is the measurement the field is missing; if it arrives, that chapter changes.
• A concept chapter's argument is falsified. That is the update worth writing.

A new benchmark score is not, on its own, a reason to touch this site.