diff --git a/docs/Website/README.md b/docs/Website/README.md
index c67ad36..d0a850c 100644
--- a/docs/Website/README.md
+++ b/docs/Website/README.md
@@ -41,6 +41,19 @@ python3 -m http.server 8000
Adding a document means adding one line to the `DOCS` array in `docs.js`. The
reader will only load a path that appears there.
+## The two footer notes
+
+Both pages carry two statements below the licence line, and both are meant to
+be read rather than skimmed past.
+
+The first is the flag, below. The second is about AI, and it says the thing
+worth saying: the tool is not the measure. A project is good when the people
+building it understand what was built. That claim is deliberately made next to
+a link to `history/`, because that directory is where it can be checked — the
+bugs are written up in full, including the wrong turns and the measurements
+that disproved them. An explanation you can follow is the evidence; the byline
+is not.
+
## The flag
`Assets/pride.svg` is in the top bar and in the footer, on both pages, and it
diff --git a/docs/Website/docs.html b/docs/Website/docs.html
index 77a0481..676be54 100644
--- a/docs/Website/docs.html
+++ b/docs/Website/docs.html
@@ -55,6 +55,16 @@
Built by, and for, people of every orientation and gender identity.
The flag stays up all year.
+
+ On AI.
+ Parts of SchOS were written with AI assistance, and that is not the measure
+ of anything. A project is good when the people building it understand what
+ was built, and bad when nobody does — whoever, or whatever, typed it. Vibe
+ your way through and you get something no one can fix. Stay in the loop and
+ you get a system you can explain line by line. The bug writeups in
+ history/ are where that gets
+ checked, including the wrong turns.
+
diff --git a/docs/Website/index.html b/docs/Website/index.html
index 0239fe0..b47d8aa 100644
--- a/docs/Website/index.html
+++ b/docs/Website/index.html
@@ -295,6 +295,16 @@
Built by, and for, people of every orientation and gender identity.
The flag stays up all year.
+
+ On AI.
+ Parts of SchOS were written with AI assistance, and that is not the measure
+ of anything. A project is good when the people building it understand what
+ was built, and bad when nobody does — whoever, or whatever, typed it. Vibe
+ your way through and you get something no one can fix. Stay in the loop and
+ you get a system you can explain line by line. The bug writeups in
+ history/ are where that gets
+ checked, including the wrong turns.
+
diff --git a/docs/Website/style.css b/docs/Website/style.css
index 26f96f4..b05b4a0 100644
--- a/docs/Website/style.css
+++ b/docs/Website/style.css
@@ -576,3 +576,18 @@ body.reading footer { margin-top: auto; }
.top nav a.on { color: var(--fg); }
.readerlink { margin-top: 2rem; }
+
+/* A footer note that is a paragraph rather than a credit line. Same width
+ discipline as body text: these are read, not scanned. */
+footer .note {
+ flex-basis: 100%;
+ max-width: 54rem;
+ color: var(--dim);
+ font-size: 0.82rem;
+ line-height: 1.7;
+}
+footer .note b { color: var(--fg); font-weight: 700; }
+footer .note a { color: var(--accent); }
+
+/* The two notes sit below the identity line, not beside it. */
+footer .wrap { row-gap: 1.5rem; }