Part 7. The detailed design of the harness

This folder holds the detailed design of the experiment: one chapter per mechanism of the harness, each describing, for a given line of code, what it does, why it is there, what it writes, who reads what it writes, and what happens when it fails. The specification that governs the set is 5. Experiment/11. Detailed Design/specifications/C0-detailed-design-specification.md (its section 4 fixes the fourteen sections every chapter carries, section 5 the diagrams, section 6 the reference form, section 7 the maintenance contract, section 9 the production plan and the acceptance test). The standard a chapter is written to is the reviewed sample, chapter 06, which still sits at 5. Experiment/11. Detailed Design/records/sample-chapter-execution-of-a-cell.md and moves into this folder in the step the specification’s section 9.5 reserves for the operator. This file stands in for the reading guide 00-reading-guide.md until that guide is written; it lists the chapters with their status and carries the dependency table skeleton of the specification’s section 7.1.

Written 2026-09-12 by Claude Fable 5.1 under task F4 of the plan-first orchestration job. The four chapters produced in this pass were written in the production order the specification’s section 9.1 gives, 09, then 03, then 01, then 10, so that the operator can correct the standard on the cleanest extractions before the expensive chapters are written. Every line number in them was read from the source at commit 6e2ee2c2b. Two further commits landed during the session (1416c4130, the publication of run set 212, and 2d705b5b7, a batch specification) and changed only run-set, metrics, monitoring and report files; every file the four chapters own has the same Git blob hash at commit 2d705b5b7 as at 6e2ee2c2b, and the harness scripts among them have the same hash as at b69ae5977, the commit the flow model was verified against.

1. The chapters and their status

A chapter is written when it has been produced to the standard and verified by search against the source; drafted when only the local model’s first draft exists under operations/detailed-design/drafts/ (a lead, not a fact, per that folder’s README); reserved when the mechanism does not yet exist in the harness.

2. What each written chapter ends with

Each written chapter ends with four things the task required beyond the specification’s section 14: a numbered list of what the local model’s draft got wrong, so the model’s error rate is on record (chapter 09 lists thirteen errors, chapter 03 fourteen, chapter 01 twelve, chapter 10 eleven); the chapter’s weakest claim; what was not checked; and the token line, the context consumed by the session at the moment writing began, measured as the difference of the remaining-token counter. The counter stood at 236,446 tokens consumed when chapter 09 was written, 455,732 for chapter 03, 628,458 for chapter 01 and 817,201 for chapter 10; the chapters add their own length on top, and the job ledger carries the cost.

The acceptance test of the specification’s section 9.3 has not been run on any of the four: no reviewer has answered its five questions in writing, and the two mechanical checks that precede the reviewer cannot yet run, because the currency check does not exist and the write-site search over the owning files (write_text, open( in a writing mode, json.dump, copytree, copy2, shutil) was done by reading each file rather than by a script. The record tables of section 7 in each chapter were built from that reading.

3. The dependency table skeleton

The columns are those of the specification’s section 7.1: the code path, the line range the chapter reads into (empty for a whole file), the Git blob hash of the file when the chapter was last verified (git rev-parse <commit>:<path>), the commit, the chapter, the chapter sections that describe the range, the diagram identifiers that draw elements from it, and the test files that exercise it. Diagram identifiers follow the convention <chapter>-<section><letter>: 09-5a is the first diagram of chapter 09’s section 5, 09-5b the second, 09-6 the sequence of section 6, 09-7 the lineage of section 7. The blob hashes below were computed at commit 2d705b5b7 and are identical at 6e2ee2c2b for every path listed; verified_commit names the commit the chapter’s line numbers were read at. The sample chapter’s row is carried from the specification. DEPENDENCIES.csv is this table written as comma-separated values with the same eight columns.

Every file under the owned folders that no row names is a new file with no chapter; the currency check of the specification’s section 7.2 lists them when it exists. The files of chapters 02, 04, 05, 07, 08, 11, 12 and 13 are absent from this table on purpose: their rows are written when their chapters are.

4. What this pass did not do, stated so that it is not mistaken for done

The public research site was not updated. Its source folder 0. The Website/ is guarded for this pass, and the site’s standing obligation (a plan document changing design or policy is a material change) is a debt this index records: when the design folder is accepted, the site’s page for the plan needs a row for it and the changelog an entry. The plan’s own README.md was not edited for the same reason; step 5 of the specification’s section 9.5 gives it a row for this folder by the operator’s hand. The currency check script, the dependency file as comma-separated values, the reading guide, the glossary and the currency report were not written. No harness script was run; no batch, closeout or model call was started; nothing under the guarded subtrees was changed.