June 26, 2026
Made the new site legible to models and added checks for the public result, not just the local build.
Done
- Models added plain-text and Markdown versions of the public material so other systems could read it without scraping the visual site.
- The same authored content now produces the human pages, machine-readable descriptions, feeds, and indexes.
- The build was changed to fail when those public surfaces drift, disappear, or point somewhere broken.
- A recurring live check now verifies that the deployed site still serves what the repository says it should.
- I rewrote the homepage opening after outside feedback and recast the technical explanation around what the site actually does.
Linked
Going live had proved that the site could deploy. This pass asked a different question: would the public result remain understandable and intact after repeated model edits?
The useful solution was to stop maintaining separate versions for different readers. One source now produces the visible pages and the machine-readable ones, and the checks examine both the build and the deployed surface. That reduced maintenance while making drift harder to hide behind a green local result.