Day 1 · Exploration · collected 2026-08-31

The day that mapped the territory

Nineteen prompt slices and twenty-four model names, including nemotron, opus 5 and two spellings of the same GLM build. This was the day that mapped the territory rather than measuring it.

236
files collected
24
model names
19
prompt slices
39
A-episodes returned
Presenter mode shows one section per screen. Arrow keys move, A toggles autoplay, Esc exits.
1
Ranking

How the field ranked on this day

Run-1 tier, T1 best
Day 1 had no ground truth to grade against, so tier is the only ranking the day supports. T1 = best of run, T2 = complete but generic, T3 = broke the output contract. Bar length shows which tier each model reached.
opus 5T1sonnetT1kimiT1glm 5.3*T2metaT2chatgptT2mimoT2minimax m3T2tencent yunbaoT2deepseekT2–T3geminiT2–T3mistralT2–T3qwenT2–T3solar proT3
top value groupbottom value groupbetween
The four models the log grouped as T2–T3 are drawn at the midpoint and labelled as a group. minimax (free) is absent: a quota error returned no output, so it has no tier. * The free web chat build of GLM 5.3 Flash is the quantized one; the API-harness deployment of the same model name is a different build, and the two do not score alike.
2
The prompt

Nineteen slices sharing one output discipline

Day 1 ran the whole lettered family. Every prompt shared one discipline, “a single bare JSON object or array and nothing else”, an explicit truthfulness field, and a hard rule that inventing a source or a chip name is the worst possible output.

Goal of this animation

Show what the Day 1 exemplar prompt asked for: three draft episodes in one JSON array, each with rejected options and a self-named weakest point.

A-v5 promptmodelfree web chatexactly three episodes in one bare JSON array[]ep 1routing congestionon a 28nm blockep 2a timing failure readfrom the report’s shapeep 3an SDC derivationat a block boundarycandidates_consideredan option rejected with its concrete costan option rejected with its concrete costan option rejected with its concrete costweakest_pointthe detail most likely wronginvented name = worst outputtruthful skip scores higher
Step 5 of 5

An invented name scores worst

An invented name is the worst possible output. A truthful skip scores higher. The rejected options and the weakest point mattered more than the story.

Left and right arrow keys step back and forward once the player has focus. Link to a step with #xp-day1-step=N.
PROMPT-A-EPISODES · A-v531 prompts in the family; this is the exemplar
You are helping build a research dataset about how senior ASIC physical-design engineers actually reason during design closure. I need DRAFT case studies ("episodes") that a real 14-year physical-design veteran will later review, correct, or reject.

**Output format: a SINGLE bare JSON array and NOTHING else.**

Produce exactly 3 episodes, one per scenario:/n  1. A routing-congestion crisis on a 28nm block
  2. A timing-closure failure where the violation report's SHAPE drove the diagnosis
  3. A timing-budget / SDC-derivation decision at a block boundary

...`candidates_considered` (array of โ‰ฅ3 `{action, rejected_because}` โ€” rejections matter most and must cite a concrete cost) ... `weakest_point` (the single detail most likely wrong).

**Hard rules:** No invented chip, company, or person names. No sources you cannot name. Boring-and-consistent beats dramatic-and-wrong. A truthful skip scores higher than a fabricated episode.
The other eighteen slices: B-v1/v2 browser cells · C-v1 sources · D1-v3 genre map · D2 POWER4 extraction · E-v2 calculations · F-v1 diagnosis library · G-v1 SDC patterns · H-v1 proving pitfalls · I-v1 review checklists · J episode red-team · K-v1 node deltas · L/M/N/O paper recall · P-v1 POWER4 rerun · Q-v1 Q&A guide · S-v1 calc depth · T-v1 test vectors

The slices present on this day:

A-v1/v2 episodesB-v1/v2 browserC-v1 sourcesD1-v3 genre mapD2 POWER4 extractE-v2 calculationsF-v1 diagnosisG-v1 SDC patternsH-v1 pitfallsI-v1 checklistsJ red-teamK-v1 node deltasL Alpha recallM Pentium 4 recallN POWER4 phys recallO Niagara recallP-v1 rerunQ-v1 Q&AS-v1 calc depthT-v1 vectors
3
What graded it

Three run logs followed by a corpus-wide digest

Station
Fable 5
Wrote and graded the three collection run logs. Run 1 (A-v1/B-v1, 15 models) and run 2 (A-v2/B-v2/C-v1, 15 outputs) and run 3 (D-v1 Task 1, 14 outputs) each carry a per-model tier table and a “v-next changes” section.
Web Model Tasks/Day 1/LOG-RUN1,2,3-2026-08-31.md
Station
Opus 5
Later re-graded the merged corpus: 233 files, 2.34 MB, 1,550 JSON items across 18 slices, with nineteen no-JSON files salvaged rather than discarded.
digest/DIGEST-REPORT.md
Method
Mechanical, where ground truth exists
Arithmetic was recomputed; the S and T slices were recomputed vector by vector. Prose was not scored.
digest/recall-scorecard.md §2b
4
How each model performed

Run 1 covered A-v1 and B-v1 across 15 models

LOG-RUN1 tier table, 2026-08-31
ModelA episodesB cellsTierNote
opus 536T1Best of run. Realistic macro-channel/NDR detail; weakest_point correctly flags its own implausible 214k→340 DRC drop
sonnet312T1Self-flags the optimistic spread-improves-timing claim; largest B block
kimi35T1Only model whose congestion fix COSTS timing (WNS −0.05→−0.06), the realistic direction
glm 5.338T2Complete, generic
meta310T2Complete, generic
chatgpt3n/aT2Truthful constructed-example tag on ep3
mimo / minimax m33 eachn/aT2Over-delivered candidate count (fine)
deepseek / gemini / mistral / qwen3 eachn/aT2–T3Bland composites, thin rejections
solar pro5 blocksn/aT3Ignored the output format
tencent yunbao3partialT2Content fine, format deviation: wrapped in a {"prompt_a": ...} object
minimax (free)n/an/an/aQuota error rather than an output. Retry after reset
Totals: 39 A-episodes, all tagged composite-of-common-practice or constructed-example and zero recalled-public-case. Truthful, but no jackpot. ~41 B-cells with URLs, unverified at the time of the log.
LOG-RUN2 (A-v2 / B-v2 / C-v1) and LOG-RUN3 (D-v1) tier lists
RunT1T2T3n/a
Run 2: A/B/C, 15 outputsopus (A+B+C, the tracker lead); chatgpt (two IBM papers); sonnet (A+B+C); kimi (A+B); glm 5.3 (A+B)mimo, minimax-3 (content fine, wrong shape), yuanbao, qwen, solar pro, gemini, metadeepseek, mistral (bland again; two bland runs = deprioritize)minimax 2.7 (quota error, 2nd time)
Run 3: D-v1 Task 1, 14 outputs13 models produced genre maps: 129 entries, 96 unique titles, 82 singletonsmimo: empty genre_map (format followed, nothing delivered)deep-research-report: never received the attachment, produced a 12 KB meta-reportn/a
5
What it found

What the widest net returned

Best performer
opus 5
Took T1 in both runs, and its weakest_point field predicted the reviewer’s own attack on the implausible 214k→340 DRC drop.
Weakest performer
solar pro
Returned five blocks instead of three episodes and ignored the bare-array rule, the day’s only outright T3.
The honesty machinery worked as designed
opus 5, sonnet and kimi all took T1 and each named its own weakest number. opus 5 flagged its implausible 214k→340 DRC drop, the first thing a reviewer attacks, and sonnet flagged its optimistic spread-improves-timing claim. The pattern held across six graded slices.
Prompt C worked on its first run
Three models attempted it. chatgpt named two IBM Journal of R&D papers, POWER4 closure at 2002 with confidence 0.94 and z10 at 2008. opus named the OpenROAD, OpenLane and LibreLane GitHub issue trackers as public failure-and-recovery archives. sonnet named the Bhasker and Chadha STA book at confidence 0.6. The trackers became the ten Day-8 red-team blocks.
Format rules broke whenever more than one prompt went into one chat
The rule held for single-prompt chats. With several prompts in one chat, chatgpt folded its source answers into the episode array as a fifth entry, minimax-3 emitted dictionary blocks instead of arrays, and kimi appended an empty block. Run 3 fixed it by process, sending one prompt per fresh chat. Harder prompt language had not helped.
minimax 2.7 hit a quota error twice and was graded n/a
It failed on run 1 and again on run 2, so it was recorded n/a both times and never zero. The same distinction between a model that did not answer and one that answered badly recurs on Day 5 (solar, PROSE-NOT-JSON), Day 6 (meta and solar, unparseable) and Day 7 (0 of 15 schema).
6
Source files

Where the evidence lives

๐Ÿ”’ All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data โ€” use synthetic or anonymised inputs only.