From fbf57d543508855f55b7607e537d900deb3f0091 Mon Sep 17 00:00:00 2001 From: Ebin Date: Thu, 27 Aug 2026 20:39:56 +0530 Subject: [PATCH] Say the explainer is hosted, because it now is The Pages deploy ran on the merge and succeeded: https://ebt55.github.io/incidentgate/ returns 200 and serves 52,627 bytes, byte-identical to the committed explainer/index.html, so the gated file reached the URL rather than a rebuild or the headless fragment. The README said the page "will be hosted", was "not live yet", and that the URL "404s until that lands". All three were true when written this morning and are false now. A placeholder that outlives its condition is the same defect as any other record that no longer matches what produced it, and this one sat in the file whose staleness started the rewrite. Replaced with the present tense, and the deploy gate named where a reader will look for it: the page cannot drift from the artifacts without failing the deploy, which is the reason it is served from a workflow rather than uploaded. Co-Authored-By: Claude Fable 5 --- README.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index a249ac6..5b9a472 100644 --- a/README.md +++ b/README.md @@ -150,16 +150,17 @@ the environment traps. ## The explainer page - - -A generated walkthrough of these results will be hosted at -**** — ***not live yet***. Until then, -`python explainer/build.py` writes `explainer/index.html` to open from disk. Every -quantitative claim on that page is derived from committed artifacts by +A generated walkthrough of these results is hosted at +****. `python explainer/build.py` writes the +same page to `explainer/index.html` to open from disk. + +Every quantitative claim on that page is derived from committed artifacts by [`explainer/build.py`](explainer/build.py); its only hand-carried text is a block -of exact quotations, each pinned by a test against its source document. +of exact quotations, each pinned by a test against its source document. The deploy +refuses to publish a page that has drifted from the artifacts it claims to derive +from — [`.github/workflows/pages.yml`](.github/workflows/pages.yml) gates on +`build.py --check`, so a stale page fails the deploy rather than reaching the URL +most likely to be read and quoted. ## What else is measured