From cbbf734dd1f5f35f5058c2dc7cc5fac51757802e Mon Sep 17 00:00:00 2001
From: Sam Keen
Date: Sat, 10 Oct 2026 10:33:28 -0700
Subject: [PATCH] Fine-tune the docs landing page, and say who wrote the test
tasks
Landing page:
- "Why I ran these" is two paragraphs, followed by a note on the use of AI.
- "Three kinds of question, no prose" becomes "The premise: what Jev is",
and points to TypeSafe's introduction for the detail.
- Each live experiment has a thumbnail beside its hypothesis. model-router
has no UI, so its thumbnail is a capture of the results page's route
explorer, in a light and a dark version that follow the theme toggle.
- "Protocol" becomes "More about my process": how an experiment runs, the
AGENTS.md rules the agent works to, and an example on each of the five
design rules. The anchor is now #process.
- "Read before trusting" becomes "A note on the current level of rigor",
cut to one paragraph and four points. The anchor is now #rigor.
- Each card's timing note links to its results page's latency note, which
has the setup the shorter rigor section no longer repeats.
The pages called the samples "hand-written". model-router's README records
that Claude wrote and labelled its 24 tasks, so its results page and written
report now say that. godot-jev's page says its lines were written for a
recording, which is what its caveats already said; the repo doesn't record
who wrote them.
Co-Authored-By: Claude Opus 5.5
---
docs/README.md | 4 +-
docs/godot-jev/index.html | 5 +-
docs/index.html | 230 ++++++++++++++++++------
docs/model-router/app.js | 4 +-
docs/model-router/index.html | 4 +-
docs/model-router/screenshot-dark.png | Bin 0 -> 58625 bytes
docs/model-router/screenshot-light.png | Bin 0 -> 53596 bytes
model-router/eval/results-2026-10-08.md | 7 +-
8 files changed, 191 insertions(+), 63 deletions(-)
create mode 100644 docs/model-router/screenshot-dark.png
create mode 100644 docs/model-router/screenshot-light.png
diff --git a/docs/README.md b/docs/README.md
index b6985af..ebbb345 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -9,9 +9,9 @@ folder `/docs`.
| Path | What it is |
| --- | --- |
-| `index.html` | Landing page: why the experiments were run, what System One models are, the four experiments, the protocol, the notebook log, the limits |
+| `index.html` | Landing page: why the experiments were run, the premise (what Jev is), the four experiments, the process, the notebook log, a note on the level of rigor |
| `assets/` | Shared by every page: styles (`site.css`) and the theme toggle (`site.js`). Shared by the results pages: `results.css`, and `results.js` (tooltips, chart helpers, the side contents) |
-| `model-router/` | The 2026-10-08 model-router run: `index.html`, `app.js`, and generated `data.js` |
+| `model-router/` | The 2026-10-08 model-router run: `index.html`, `app.js`, generated `data.js`, and two captures of the page's route explorer (`screenshot-light.png`, `screenshot-dark.png`) that the landing page shows as a thumbnail |
| `godot-jev/` | The 2026-10-08 three-model godot-jev run: `index.html`, `page.css`, `app.js`, a screenshot of the game, and generated `data.js` |
| `tools/build-model-router-data.mjs` | Builds `model-router/data.js` |
| `tools/build-godot-jev-data.gd` | Builds `godot-jev/data.js` |
diff --git a/docs/godot-jev/index.html b/docs/godot-jev/index.html
index fb19090..9be6c74 100644
--- a/docs/godot-jev/index.html
+++ b/docs/godot-jev/index.html
@@ -73,8 +73,9 @@
Three Jevs parse 16 lines of player slang.
model, with the moves possible right now as the options of one Choice. I gave three Jevs, one hosted
and two running on a laptop, the same 16 lines in the same game states, three times each. All three got
the player to the crown without a wrong move. They differ in how sure they were, how often the game had
- to ask what the player meant, and how long a turn took on this setup. This is a gut check on a small,
- hand-written set of lines, not a benchmark: what it does and doesn't show.
+ to ask what the player meant, and how long a turn took on this setup. This is a gut check on a small
+ set of lines written for a recording, not a benchmark:
+ what it does and doesn't show.