REVIEW_NOTES.md
Self-Improving Intelligence: visual guide
REVIEW_NOTES.md
1 # Visual guide review and validation
2
3 **Self-Improving Intelligence — A Visual Guide**
4 **Komorebi P. · Operation Komorebi · Guide v1.0.0 · 8 October 2026**
5
6 ## Scope
7
8 This is a new, 36-page visual companion to the unchanged 60-page first-edition
9 manuscript. It follows the same finite diagnostic example through improvements
10 to its controller, compiler, pruning rule, and acquisition representation. It
11 also explains model uncertainty, preserved evidence, repair scope, certificate
12 invalidation, resource prices, and the limits of recursive continuation.
13
14 All diagrams were drawn programmatically as vector geometry. The PDF contains
15 no raster illustrations. It has 36 bookmarks, eight clickable reading-route
16 links, and page-level source references. The source package includes 36 separate
17 SVG plates and three PNG previews. Fonts are embedded in the PDF; standalone
18 font files are not distributed.
19
20 ## Source review and preservation
21
22 The manuscript and its review notes were read through Files. The original source
23 ZIP was extracted for its reference indexes and exact JSON receipts. Its supplied
24 integrity verifier passed for all 325 archived files. The original manuscript and
25 source ZIP were not edited. The guide's source PDF copy is byte-identical to the
26 original. Selected source JSON files are retained unchanged and pinned by hash.
27
28 Source references point to printed manuscript page numbers. The local finite
29 examples illustrate existing arguments, not new priority claims. The reference
30 work already identifies its standard mathematical foundations. This companion
31 adds no new literature claims and performs no new external literature review.
32
33 ## Mathematical and explanatory checks
34
35 `code/check_guide.py` passed **12 focused groups and 2,978 checks**. The domains
36 and counts appear in `validation/guide_checks.json`. They cover the canonical
37 bit-query policy on all eight cells, its leaf ordering and highlighted cell-five
38 path, repair-aligned partitions, the max/sum storage recurrence, the four possible
39 sensor/model pairs, count-prefix completion at capacities 1 through 8, the
40 three synthesis counterexamples, selected signed-integer identities, paired
41 repair weights, price-specific cost changes, all 16 four-score hindsight paths,
42 and partial sums of diminishing positive gains.
43
44 The same script checks the numerical transcriptions against the unchanged
45 source records for shortcut compilation, streaming, equation admission,
46 quotient size, reacquisition, and certificate replacement. This is a check of
47 **what the source records say**, not a new execution of those source compilers.
48 The complete original 336,867-assertion suite was not rerun.
49
50 The highlighted eight-cell route is explicitly the canonical all-coordinate
51 policy. The actual source compiler's cell-five trace uses an equality query at
52 its last two-case branch. The guide does not misidentify those as the same
53 literal tree. The quotient illustration likewise labels its expression order
54 as schematic rather than claiming the pictured examples occupy those precise
55 positions in the original grammar.
56
57 The certificate diagram retains the separate arithmetic/acquisition and
58 repair/controller branches. A valid capacity expression is not substituted for
59 a repair-weight certificate. The resource plate preserves negative signs and
60 the distinction between semantic validity and a favorable cost assessment.
61
62 ## Actual failures and corrections
63
64 1. The first PDF build stopped at the page-three layout guard: its explanatory
65 note needed 29 points of body height but had only 25.48 available. The note
66 panel was enlarged and moved upward. The body font was not reduced.
67 2. Render inspection exposed missing minus signs in the serif numeric display.
68 The text layout held the correct negative numbers, but the selected display
69 font lacked the minus glyph. The renderer was changed to use the mathematical
70 face for unsupported characters while retaining the requested face elsewhere.
71 3. The first focused preflight subsequently failed on a missing XOR glyph in
72 page-eleven body text. The same fallback was extended to formatted paragraphs.
73 The final PDF is checked for null/replacement characters, and the negative
74 values on page 28 must also extract with their actual minus signs.
75 4. An unused, unembedded default Helvetica resource was removed by explicitly
76 setting the canvas's initial face. All six font resources in the final guide
77 are embedded subsets.
78 5. The bit-query subset legend was added, and the repeated-rejection path was
79 routed outside its boxes. These clarify the illustrated semantics and avoid
80 interpreting line crossings as extra dependencies.
81
82 No local mathematical example or source-number transcription check failed.
83 The layout and glyph failures above were real document failures and are not
84 reclassified as mathematical successes. The final checks passed only after
85 regenerating the PDF.
86
87 ## Visual and mechanical review
88
89 All 36 pages were rendered with Poppler and inspected in contact sheets.
90 Selected full pages were additionally rendered with PyMuPDF and inspected,
91 including the cover, both diagnostic trees, the unknown sensor, the missing
92 capacity feature, the quotient, the dependency graph, signed costs, sequential
93 evidence, and the semantic transport square. The final formatting revision
94 removed only the unused font resource; its Poppler images were compared with
95 the inspected rendering.
96
97 Mechanical checks found no out-of-page words, overlapping word boxes above the
98 stated detection threshold, null/replacement glyphs, or missing source footers.
99 They do not prove every diagram is conceptually correct. The selected full-page
100 and whole-document visual inspections provide a separate presentation check.
101
102 A fresh source copy was rebuilt and checked. Its page-by-page extracted PDF text,
103 PDF bytes, and mathematical check output were compared with the delivered guide.
104 The actual result appears in `validation/fresh_rebuild.json`.
105
106 ## Limits
107
108 The checker and illustrations are authored within the same project. This is not
109 independent peer review, a Lean build, a complete re-proof of the manuscript, or
110 an empirical demonstration of general intelligence. Font substitution and
111 cross-platform byte identity are not certified. PDF/A and tagged accessibility
112 were not certified. SVG text is outlined for portable display; editable wording
113 remains in the Python source.
114
115 The final snapshot checksum inventory verifies the included files, not their
116 truth or independent origin. Verify it before rebuilding outputs whose receipts
117 include fresh execution times.