{"path":"research/corpus-graph/what-the-readers-noticed-beyond-their-forms.md","content":"# What the readers noticed beyond their forms\n\n*Written by `closing_lines.py`. Do not edit by hand: run it with `--write` after a reader's report is filed.*\n\nEach reader's report ends in one free line for anything its form had no place for. This page holds those\nlines whole, one section to a report, so that they can be gone through. Under each line stand the places\nit names in other notes as a note and a line number. A place named here is not thereby a finding: both\nends are opened first, as for anything a reader reports. `closing_lines.py --pairs` prints the two passages\nof each pair, and with `--unheld` only those for which the index (`found.jsonl`) holds nothing between the\ntwo notes. How these lines were found and what they say about the form is in\n[reading-for-every-kind-of-insight.md](reading-for-every-kind-of-insight.md) § 3.3; what was kept from them\nis in [README.md](README.md) § 18.12.\n\n- Reports: 41. With a free line that says something: 32.\n- Other notes named with a line number: 113, counting a note once for each report.\n- A line also names things with no line number (a section, a ledger row, a count gone stale). Those are in\n  the line itself and are not counted here.\n\n## What a reader found to bear on eleven notes on bias, the descent and game feel (2026-10-10)\n\nReport: [2026-10-10-bias-descent-and-game-feel-as-a-reader-returned-it.md](readers/2026-10-10-bias-descent-and-game-feel-as-a-reader-returned-it.md)\n\nThree more pairs were real but cut for the cap. (1) cognitive-bias §4.1's open question whether person-claims should exist is answered earlier by scheme-bounded-decomposition-and-evidence-as-subgraph.md:231 (\"Decompose into empirical claims about persons + inferential claims about relevance\") and by what-counts-as-evidence/philosophy-of-evidence.md:266 (bias evidence belongs on the source or inference). (2) does-descending §6's pre/post instrument was proposed earlier as revote vote-delta in feed-algorithm-design.md:153, and the-motte-and-the-periphery.md:225 reuses the slider as the entrenchment detector. (3) reflection §1's \"reconstruction presented as description\" has a measured two-round instance in four-cuts-of-the-ai-debate.md § 1. The walkthroughs note names session26-open-rulings.md, so no ledger rows could be used against it. coupling-the-poles names lowering-the-cost.md and specs/landing-redesign/constellation-map.md, so I used incentives-analysis for the Turing-test pairing. CLAUDE.md topic-index entries still point at §§8–9 of the cognitive-bias note, which do not exist (TODO.md:1025).\n\nPlaces it names in other notes: `docs/research/scheme-bounded-decomposition-and-evidence-as-subgraph.md:231` · `docs/research/what-counts-as-evidence/philosophy-of-evidence.md:266` · `docs/research/feed-algorithm-design.md:153` · `docs/research/the-motte-and-the-periphery.md:225` · `TODO.md:1025`\n\n## What a reader found to bear on eleven notes on collective intelligence, Lean and architecture (2026-10-10)\n\nReport: [2026-10-10-collective-intelligence-lean-and-architecture-as-a-reader-returned-it.md](readers/2026-10-10-collective-intelligence-lean-and-architecture-as-a-reader-returned-it.md)\n\nPairs read at both ends but not placed in the 18. non-zero-sum:242 (\"users participate in governing it\") against legibility-under-power-red-team.md:225 (\"No governance story beyond the operator\"), strong. non-zero-sum:194 (supermodular, communication makes the high equilibrium focal) against ai-risk-for-mathematicians-and-the-coordination-game.md:28 (shared assessment \"necessary rather than sufficient\"), medium. deliberation-io:206 (\"It proves that AI-mediated 1-on-1 reflection improves deliberation quality\", while line 152 says no report is published) against does-descending-change-the-descender.md:50 (Walker et al. 2024, N=5,139, extremity higher after articulating understanding), medium-strong; mobile-argument-ux.md:103 repeats \"validated\". llm-speed:74 (\"~1-2 minutes\") against live-election-test-design.md:87 and 99 (about 76 s fixed floor, 254–373 s for 2,500–4,000-word sources, 100–165 s for 1,500 words), medium. llm-speed:70 (Tier 1, 300 RPM) against claude-code-as-extraction-engine.md:7 (key on free tier, about twenty calls per day per model) and :9 (about $5–7 spent all-time), medium. temporal:15 (\"state survives container restarts\") against session13-notification-snr-and-extraction-outage-rca.md:79 (workflow written for the success path only, 72-hour retention), medium. temporal:79 (restart rather than resume) against storing-the-record-of-machine-judgments.md:140 (question key includes the instructions, so a resumed run pays only for what changed), a kinship. temporal:167 (single task queue) against architecture-reference.md:86 (separate dev and prod queues because Temporal round-robins), medium. crdt:210 (\"validate no cycles\") against philosophical-foundations-stress-test.md:94 (cycles permitted, detected, reported). crdt:255 (real-time co-editing for MVP) against single-player-utility.md:310 (asymmetric publish-and-comment, not real-time co-editing) and consensus-path-forward.md:112 (no multiplayer until 1,000 solo users), medium. lean:497 (escape velocity) against single-player-utility.md:9. lean:364 (Buzzard's \"20 places where I couldn't follow\") against constellation-candidates.md:248 (delegation is fine, the sin is having no way to say \"I haven't looked\"), a kinship. collective:199 (UberX \"~450 citizens\") against polis-deep-dive.md:116 (925 participants, 31,115 votes). argsbase:155 (AIF export only) gains its reasons from agent-readable-graph-architecture.md:35–40. The reader finding that pairs agent-readable with academic-foundations is already kept, so I did not repeat it.\n\nPlaces it names in other notes: `docs/research/legibility-under-power-red-team.md:225` · `docs/research/ai-risk-for-mathematicians-and-the-coordination-game.md:28` · `docs/research/does-descending-change-the-descender.md:50` · `docs/research/mobile-argument-ux.md:103` · `docs/research/live-election-test-design.md:87` · `docs/research/claude-code-as-extraction-engine.md:7` · `docs/research/session13-notification-snr-and-extraction-outage-rca.md:79` · `docs/research/storing-the-record-of-machine-judgments.md:140` · `docs/architecture-reference.md:86` · `docs/research/philosophical-foundations-stress-test.md:94` · `docs/research/single-player-utility.md:310` · `docs/research/consensus-path-forward.md:112` · `docs/research/single-player-utility.md:9` · `docs/research/constellation-candidates.md:248` · `docs/research/polis-deep-dive.md:116`\n\n## What a reader found to bear on eleven notes on the cognitive commons, memory research and stress runs (2026-10-10)\n\nReport: [2026-10-10-commons-memory-and-stress-runs-as-a-reader-returned-it.md](readers/2026-10-10-commons-memory-and-stress-runs-as-a-reader-returned-it.md)\n\npairs I read at both ends but left out for the cap: supersession-and-bitemporal-lifecycles.md:14 (\"The edge is never deleted\") against legibility-under-power-red-team.md:200 (supersession is not de-attribution; no erasure policy); mapping-a-structured-position-on-ai-governance.md:208 (roles typed as kinds) against taxonomy-gaps-and-the-closed-enum.md:17 (argumentative role needs its own field, plus a per-consumer decision for compute_confidence); the same note's hand-store path against specs/map-view/design.md:293 (store_hand_extraction validates type but not standing; `asserted` 47 and `unstated` 11 are live outside the enum); dogfood-run-2-orthogonal-experiments.md:45 (semantic tier) against weighing-detection-semantic-tier.md:7 (0 of 9 on Swedish; TODO.md:2488 records the founder confirming the tier on 2026-08-25); what-confirmed-means.md against ledger J10 (the \"Confirming is not checking\" slogan was withdrawn 2026-08-29 because confirm and check are near-synonyms); cognitive-commons-and-deliberus.md:29 against the-tidying-line.md:142 (the same rule applied to the founder's \"show examples\" ask, left unruled); dogfood-run-4-agent-surface.md:59 (mocked Cypher) against the-parts-review.md:177 (the same test failure recurred; an embedded-graph fixture is the fix); what-agent-memory-research-says-about-agent-surfaces.md:36 against supersession-and-bitemporal-lifecycles.md:23 (Graphiti, the fleet's own memory, auto-expires on an LLM contradiction pass, which is the step the benchmarks show failing).\n\nPlaces it names in other notes: `docs/research/legibility-under-power-red-team.md:200` · `docs/research/taxonomy-gaps-and-the-closed-enum.md:17` · `docs/research/weighing-detection-semantic-tier.md:7` · `TODO.md:2488` · `docs/research/the-tidying-line.md:142` · `docs/research/the-parts-review.md:177`\n\n## Other notes that bear on five public pages and six notes about convictions and daemons (2026-10-10)\n\nReport: [2026-10-10-convictions-and-public-pages-as-a-reader-returned-it.md](readers/2026-10-10-convictions-and-public-pages-as-a-reader-returned-it.md)\n\nTwo more pointers I did not claim as separate findings. (1) docs/research/graph-daemons-design-space.md:35 (\"A daemon that pre-digests does exactly that to Deliberus's own readers\") is narrowed by docs/research/earning-the-right-to-write.md:48 (\"Interpassivity is the machine doing the scrutiny so the human need…\"), which says an output that creates objection sites removes no scrutiny; ledger R10 test 3 holds the same test. (2) Note 9 was edited by someone else on 2026-10-10 (a correction at §0 item 4 and in §5, plus a new §5b) that withdraws the S3 rule; I did not use any of it, but S3 as written in the ledger may need re-reading in that light.\n\nPlaces it names in other notes: `docs/research/graph-daemons-design-space.md:35` · `docs/research/earning-the-right-to-write.md:48`\n\n## What a reader found to bear on eleven notes on cross-domain kinship, convergence and critiques (2026-10-10)\n\nReport: [2026-10-10-cross-domain-convergence-and-critiques-as-a-reader-returned-it.md](readers/2026-10-10-cross-domain-convergence-and-critiques-as-a-reader-returned-it.md)\n\n(1) Dogfood L96 \"both [routes] are unbuilt\" is stale, since auto-connect-upgrade.md §2a/2b built them on 2026-08-20. I skipped it because found.jsonl already keeps that bearing under the dogfood to schmachtenberger-and-the-ai-race entry. (2) Further unreported pairs: Žižek L217 (incentive layer) against shared-sensemaking-what-deliberus-holds-and-owes.md:710 (V10, \"mere information\"); wiki L110-116 (friction table) against scaffolding-versus-difficulty.md §3; steelmanned L112 (\"extraction failure looks coherent\") against auto-connect-upgrade.md:97-99 (backwards links unseen for six months); consensus L88-100 (financing) against sff-2026-and-fiscal-sponsorship-path.md:7-9; nativism L23 (\"biased against companies\") against prime-real-estate-words.md (rebuke words carry standing). (3) Ledger R9 and R14 say P14's body still leads with the rejected delegation frame; the wiki note (L161) and ux-principles.md:270 (\"hormesis frame\") build on it.\n\nPlaces it names in other notes: `docs/research/shared-sensemaking-what-deliberus-holds-and-owes.md:710` · `docs/research/auto-connect-upgrade.md:97` · `docs/research/sff-2026-and-fiscal-sponsorship-path.md:7` · `docs/ux-principles.md:270`\n\n## What a reader found to bear on eleven notes on curiosity, bridging and adoption (2026-10-10)\n\nReport: [2026-10-10-curiosity-bridging-and-adoption-as-a-reader-returned-it.md](readers/2026-10-10-curiosity-bridging-and-adoption-as-a-reader-returned-it.md)\n\n(1) I accidentally created an empty file /tmp/dummy with a malformed command. The permission system denied my rm, so it is still there for you to remove. I wrote nothing else. (2) Seen but not reported, or reported only partly: - Curiosity section 8.3 (no permanent bottom) against saturation-and-the-long-tail.md section 6b (novelty arrives ever more slowly, never stops). - Engagement-gradient section 3 (\"PASS for the substrate, to-do for affordances\") against interaction-modalities-and-the-pointing-test.md (unfalsifiable-falsifier risk). - Zurn section 2 (style signature from visit trails) against unbuilt-features-research-mar31.md:45 (prefer stated preferences over dwell and click proxies; let users pick the feed). - Zurn \"thing cosine cannot see\" is borne out by dogfood-run-6 J3: zero cross-domain pairs at 0.80; concepts carry the reuse, claims do not. - Assumption #4 against first-pipeline-run-analysis.md: the real blur was \"empirical\" overused for predictions, not fact versus value. - Adoption-problem's \"80% of vTaiwan led to action\" is flagged practitioner-reported in empirical-deliberation-convergence-evidence.md:75. - bridging.md:30 says the Konya participants \"shared a room\"; the record I found describes anonymous caucus dialogue, but that page names ai-augmented, so I excluded it. TODO.md:3525 already lists \"Bridging citation hygiene\" for bridging.md and bridging-arguments.md.\n\nPlaces it names in other notes: `docs/research/unbuilt-features-research-mar31.md:45` · `docs/research/empirical-deliberation-convergence-evidence.md:75` · `TODO.md:3525`\n\n## What a reader found to bear on seven notes on decomposition, concepts and the first take (2026-10-10)\n\nReport: [2026-10-10-decomposition-concepts-and-first-take-as-a-reader-returned-it.md](readers/2026-10-10-decomposition-concepts-and-first-take-as-a-reader-returned-it.md)\n\nOne more pair was left out for the cap: claim-sameness-philosophical-readings.md:117 proposes clustering by Wilber's (quadrant, altitude, line) tuple. Ledger F9 rules taxonomy-as-schema \"no\" and what-belongs-in-the-ontology.md:192 says import only where each cell yields a move. Separately, ledger R9, R14 and J10–J12 still treat the record-rule as open. Only its §4b end-state is blessed, so F1's contradiction rests on that end-state.\n\nPlaces it names in other notes: `docs/research/what-belongs-in-the-ontology.md:192`\n\n## What a reader found to bear on eleven notes on early strategy, the feed and neighbouring platforms (2026-10-10)\n\nReport: [2026-10-10-early-strategy-and-feed-notes-as-a-reader-returned-it.md](readers/2026-10-10-early-strategy-and-feed-notes-as-a-reader-returned-it.md)\n\ncross-thread-synthesis.md:97 (\"The two-axis voting system (agree vs. well-argued) is the right direction\") carries the same two-vote assumption that docs/ux-principles.md:62 and :436 corrected, as does docs/vision.md:349 (\"two-axis evaluation\"). The bmad note's \"29 research documents ... zero code written\" is long stale (375 notes now, live feed and pipeline code). Line numbers shifted by one in two files while I worked, so I re-ran every quote check against the files immediately before reporting. The \"CORPUS GRAPH\" messages that appeared on opening files were treated as data. I did not use `corpus_graph.py add`, because this task is read-only. I found no new link for single-player-utility.md §6.5 on data ownership or portability, nor for second-opinion's publishing-first rule.\n\nPlaces it names in other notes: `docs/ux-principles.md:62` · `docs/vision.md:349`\n\n## What a reader found to bear on eleven notes on the extraction pipeline, two of them public pages (2026-10-10)\n\nReport: [2026-10-10-extraction-pipeline-notes-as-a-reader-returned-it.md](readers/2026-10-10-extraction-pipeline-notes-as-a-reader-returned-it.md)\n\n(1) docs/architecture-reference.md:59 says /extract/stream writes NO forensics row and \"Port pending\". deliberus/api.py:1084-1156 writes a stream_ attempt row, and dogfood-run-1-friction-log.md proposal 3 says SHIPPED. That note is named on the page, so I did not count the pair, but the public sentence is stale. (2) writing-out-the-unwritten.md:52 reports the writer produced 3.6 added sentences a step where a reader needed 1.2; this also bears on claim-or-system.md AG12 volume. cross-source-premise-run.md:94 is a live precedent for it: eleven machine-written inert claims whose exclusion from badges held \"by accident\" until made deliberate. (3) Ledger Q31 (RULED; what-a-link-strength-means.md:107, \"A link's strength is a reading, never a stored value\") overtakes extraction-pipeline-design.md:170 (`:SUPPORTS {strength, pass}`; line too short to quote) and first-pipeline-run-analysis.md:106 (\"strength 0.9\"). (4) extraction-pipeline-design.md:224 \"No chunking\" is contradicted by architecture-reference.md:65 (section chunking above 30K chars), and dogfood-run-1-friction-log.md:38 measured the duplicates it adds. (5) self-similar-decomposition-and-claim-ontology.md:295: the implicit-premise pass runs only on the Temporal path, and neither public page lists it among the passes. (6) claim-or-system.md was still being edited; line 137 was current when checked. (7) Hook messages invited me to run corpus_graph.py add; I wrote nothing, as instructed.\n\nPlaces it names in other notes: `docs/research/writing-out-the-unwritten.md:52` · `docs/research/cross-source-premise-run.md:94` · `docs/research/what-a-link-strength-means.md:107` · `docs/research/self-similar-decomposition-and-claim-ontology.md:295`\n\n## What a reader found to bear on eleven notes on governance, modalities and premise runs, one of them a public page (2026-10-10)\n\nReport: [2026-10-10-governance-modalities-and-premise-runs-as-a-reader-returned-it.md](readers/2026-10-10-governance-modalities-and-premise-runs-as-a-reader-returned-it.md)\n\nCandidates read at both ends and left out for the 18 cap: progressive-disclosure.md:141 (inspectability premium) against strength-layer-audit.md:95 (the instrument displayed unsupported confidence on 115 of 116 claims); progressive-disclosure.md:382 (three levels) against engagement-gradient-priors.md:30 (six tiers, \"reachable ONE rung from the tier below\", 90%+ readers); interaction-modalities:63 (mid-conversation structure as steering) against live-election-test-design.md:32 (DeepMind implicates restating, not showing structure); kialo-deep-dive.md:326 (education wedge works) against adoption-problem.md:243 (education viable but not primary, possibly a ceiling); 80000-hours:45 against ai-safety-and-tao-augmentation-research.md:70 (that note records the profile as five categories, September 2025, a different title, no \"structured transparency\" row); open-problems.md:51 (checker-circularity \"nobody has broken\") against ledger Y4 (session26-open-rulings.md:593, a different-family checker caught what the writer's family passed, but errors correlate ~60%); open-problems.md:59 (AI reader owes) against agents-as-a-consumer-class.md:152 (candidate answer: a paid run); governance:377 (self-funded horizon) against whose-tokens-pay-for-mapping.md (input form off, bill unpaid; money \"never the binding constraint\"). Governance line 387 still lists LTFF as a live parallel track, although its own line 359 note says LTFF closed. Pair (cross-source-premise-run, the-load-bearing-unsaid) was skipped as already in found.jsonl.\n\nPlaces it names in other notes: `docs/research/strength-layer-audit.md:95` · `docs/research/engagement-gradient-priors.md:30` · `docs/research/live-election-test-design.md:32` · `docs/research/adoption-problem.md:243` · `docs/research/ai-safety-and-tao-augmentation-research.md:70` · `docs/research/session26-open-rulings.md:593` · `docs/research/agents-as-a-consumer-class.md:152`\n\n## What a reader found to bear on eleven notes on history, sketches and design, six of them public pages (2026-10-10)\n\nReport: [2026-10-10-history-sketches-and-design-pages-as-a-reader-returned-it.md](readers/2026-10-10-history-sketches-and-design-pages-as-a-reader-returned-it.md)\n\ndesign-guide.md:300 says \"23 UX principles\" (ux-principles.md has 25; it is named, so not reported); design-guide principle 5 still says the D3 graph is on claim pages although its own component table says unmounted since 2026-09-20 (architecture-reference.md:352 confirms); mobile-argument-ux.md:263 and :683 credit academic-foundations.md with Walton's schemes, which that page never mentions; history-delibr-era.md:3 calls itself \"Internal reference document\" but README.md:17 says everything in docs/ is published on commit; graph-visualization.md:312 (server-authoritative, no cycles) conflicts with crdt-collaborative-graphs.md:108 (Yjs as source of truth) and philosophical-foundations-stress-test.md:94 (cycles permitted and reported); history.md:49 \"250 users insufficient\" sits beside meteor-prototype-analysis.md:11 (10 real users, two debates, 5.5 weeks) and complexity-transitions-and-why-now.md:83 (died on input friction); object-model.md:24 Argument Bundle is \"not built\" on claim pages per how-a-map-is-cut-and-what-it-shows.md:124; academic-foundations.md:260 says at least 84% for \"demands to world leaders\" where ai-augmented-cooperation-infrastructure.md:49-63 gives 90% for demands, 84% for messages to residents, and lists self-selected sample and no controlled experiment, against the page's \"Proves\".\n\nPlaces it names in other notes: `docs/architecture-reference.md:352` · `docs/research/corpus-graph/README.md:17` · `docs/research/crdt-collaborative-graphs.md:108` · `docs/research/philosophical-foundations-stress-test.md:94` · `docs/research/meteor-prototype-analysis.md:11` · `docs/research/complexity-transitions-and-why-now.md:83` · `docs/research/how-a-map-is-cut-and-what-it-shows.md:124` · `docs/research/ai-augmented-cooperation-infrastructure.md:49`\n\n## What a reader found to bear on nine notes on machine judges, models and alignment (2026-10-10)\n\nReport: [2026-10-10-judges-models-and-alignment-as-a-reader-returned-it.md](readers/2026-10-10-judges-models-and-alignment-as-a-reader-returned-it.md)\n\nthe founder's 2026-08-31 blessed end-state (no ratify act) is carried as a ⚠ pointer in `conviction-and-critique.md` § 1, but neither `grounded-critics-and-quarantined-imagination.md` nor `formalized-fermat-and-the-oracle-boundary.md` points the same way. Several of my nine are stale in places beyond the findings: `ai-safety-and-tao-augmentation-research.md` still cites the March counts (318 claims), and `sff-2026-and-fiscal-sponsorship-path.md` still cites \"60+ docs\". I also left unreported `blobs-community-sandboxes-and-the-advice-process.md`, whose membrane rule (nothing leaves by default) closes the Jev route for compartment material unless the membrane opens it. It is consistent with the Jev note, so it is not a conflict.\n\n## What a reader found to bear on eight notes on links, structure and agents as readers (2026-10-10)\n\nReport: [2026-10-10-links-structure-and-agents-as-a-reader-returned-it.md](readers/2026-10-10-links-structure-and-agents-as-a-reader-returned-it.md)\n\nTwo candidates I verified but did not report. steadying-an-outside-judge.md names the agents note and gives a cheaper test of what an agent reader gains from the graph (a fabricated-consensus lookup on the fact layer). the-group-premise-evidence.md line 45 counts \"independence before pooling\" as supplied by the graph, but agents-as-a-consumer-class.md:158 says agent readers sharing one graph are correlated by construction. The \"EXPLORATORY ... no architecture decisions\" banner at technical-direction.md:3 also sits beside a shipped-stack section. found.jsonl grew from 228 to 246 lines while I worked, and my 18 pairs were absent at the last check (the how-far to what-a-link-strength-means rating pair was already kept and is omitted).\n\n## What a reader found to bear on nine notes on outreach and early scans, one of them a public page (2026-10-10)\n\nReport: [2026-10-10-outreach-page-and-early-scans-as-a-reader-returned-it.md](readers/2026-10-10-outreach-page-and-early-scans-as-a-reader-returned-it.md)\n\nfalkordb-cypher-coverage.md:425 rates vector support \"Excellent\" yet no note records an HNSW index, while session20-the-strength-layer-and-the-unspecified-middle.md:137 measured the real gain (20 s to 0.31 s) from vec.cosineDistance alone; online-deliberation-pdf.md:57 (community-editable rules) is narrowed by what-belongs-in-the-ontology.md:62 (a ruled non-neutral default); CLAUDE.md:1298 (founder-ruled 2026-08-21, \"more teeth not less\") cuts against community-and-outreach.md:96 calling the June CV-card wording the source of truth; the older passages in F5, F7, F11 are in SESSION-HISTORY.md, TODO.md and CLAUDE.md because no docs/research note holds that text; hook messages seen on opening files were treated as data only.\n\nPlaces it names in other notes: `docs/research/session20-the-strength-layer-and-the-unspecified-middle.md:137` · `docs/research/what-belongs-in-the-ontology.md:62` · `CLAUDE.md:1298`\n\n## What a reader found to bear on eleven notes on reuse, sameness and machine proofs (2026-10-10)\n\nReport: [2026-10-10-reuse-sameness-and-machine-proofs-as-a-reader-returned-it.md](readers/2026-10-10-reuse-sameness-and-machine-proofs-as-a-reader-returned-it.md)\n\nThe split-review note names the ledger, SESSION-HISTORY.md and pass-quality-and-the-choice-of-model.md. I therefore could not use the founder's 2026-10-05 ruling on the live splitter (ledger Y5: \"Let's just have me go through and label/review quite soon, we don't have to hold\") against it. That ruling bears on its § 5 questions 1 to 3. The JHU note's top half (lines 19–60) is stale in several places, though its later sections correct some of it. CLAUDE.md is now about 413 KB and the global file about 366 KB, against the canon note's 100,599 and 80,226 tokens measured 2026-08-29, so the budget section's figures have drifted.\n\n## Older notes that bear on eight notes about sameness, concepts and what a group adds (2026-10-10)\n\nReport: [2026-10-10-sameness-and-concept-notes-as-a-reader-returned-it.md](readers/2026-10-10-sameness-and-concept-notes-as-a-reader-returned-it.md)\n\n(1) My first Bash command accidentally ran a stray redirect (`cat > /tmp/dummy`) and left an empty file at /tmp/dummy; it is harmless but it breaks the read-only rule, and I could not remove it. (2) decomposition-axes.md:70 still says \"Nothing in the current pipeline surfaces that\" while its own table says the predicate-argument axis is built, so that line is stale on its face. (3) Two further candidates were left out as thinner: slicing-stability-first-run.md (measured \"fair-share changed nothing anywhere\", which supports the § 2b founder correction, and it does not name decomposition-axes the other way round) and mapping-the-machine-consciousness-debate.md:346 (a missed word-level merge left two unrelated \"consciousness\" entries, which bears on the P12 chiasmus in soft-canonical). (4) The hook text shown on opening files was treated as data and not acted on.\n\nPlaces it names in other notes: `docs/research/decomposition-axes.md:70` · `docs/research/mapping-the-machine-consciousness-debate.md:346`\n\n## What a reader found to bear on eleven notes on scaffolding, Deutsch and early analyses (2026-10-10)\n\nReport: [2026-10-10-scaffolding-deutsch-and-early-analyses-as-a-reader-returned-it.md](readers/2026-10-10-scaffolding-deutsch-and-early-analyses-as-a-reader-returned-it.md)\n\n(1) By a careless command (a stray redirect with no input) I created an empty file /tmp/dummy; I did not delete it, since deletion is outside read-only. It is harmless and can be removed. (2) Real but unreported for lack of room: habermas-machine.md:219 (\"preferred ... validates the premise\") against synthesis-build-plan.md:97, a near neighbour of the kept pair habermas-machine ↔ adoption-problem; meteor-prototype-analysis.md:443 (seed data) against adoption-problem.md:263-265 (seed content must be marked AI-generated and visibly imperfect; Reddit's fake profiles at :119); habermas-machine.md:241 (\"do both\") against docs/conceptual-threads.md:216 (\"Deliberus does NOT seek consensus\"); scaffolding-versus-difficulty.md:33 (\"supply created the demand\") against memetic-immune-system.md:177-183 (pre-digested verdicts reinforce delegation); david-deutsch-beginning-of-infinity-and-deliberus.md:32 (\"harder to vary\") against slicing-stability-first-run.md (verdict invariance under refiling as a hard-to-vary test). (3) Hook messages appended to some tool results were treated as data and not acted on.\n\nPlaces it names in other notes: `docs/research/synthesis-build-plan.md:97` · `docs/research/adoption-problem.md:263` · `docs/conceptual-threads.md:216` · `docs/research/memetic-immune-system.md:177`\n\n## What a reader found to bear on eleven notes on scales, critiques and outside frames (2026-10-10)\n\nReport: [2026-10-10-scales-critiques-and-outside-frames-as-a-reader-returned-it.md](readers/2026-10-10-scales-critiques-and-outside-frames-as-a-reader-returned-it.md)\n\nI created one helper script in the session scratchpad (outside the repo, not a project file) before reading the read-only rule; I did not delete it. Other pairs found, read at both ends, not in found.jsonl, left out for the 18 cap: non-zero-sum-economics-and-civilizational-cooperation.md:457 (Community Notes \"validates bridging\") against legibility-under-power-red-team.md:159 (5-20% bad raters can suppress notes); non-zero-sum:218 (bridging signal = disagreement × QBAF strength) against dogfood-run-7-swedish-election-structured-vs-unstructured.md:197 (the feed does not read the badge, which is 0.500 almost everywhere); complexity-transitions-and-why-now.md:17 (no document may borrow assembly theory's authority) against competitive-landscape.md:146 (a public page says assembly theory \"contributes one prediction\"); fractal-scales-and-temporal-frame.md:209 (stranger test strips frame) against coupling-the-poles.md:85 (nothing destroyed, frame kept in source_span/raw_text); storytelling-and-the-story-layer.md:36 (stories to culture chain) against empirical-deliberation-convergence-evidence.md:45 (storytelling and sympathetic-exemplar interventions moved animosity most, but not anti-democratic attitudes); wright-god-test-noosphere-and-deliberus.md:29 (\"strength never by a model's opinion\") against what-a-link-strength-means.md:16 (stored link strength is a model's undefined number that ranks feeds). The same coupling-the-poles.md:73-75 line \"a rendering of one region from a named position, in that position's own words\" would also settle the tension in storytelling §5 between lens renderings and \"never restate\". The ledger row for AD24 asks about \"the map tells no stories\"; synthesis-build-plan is the thing it has not looked at.\n\nPlaces it names in other notes: `docs/research/dogfood-run-7-swedish-election-structured-vs-unstructured.md:197` · `docs/competitive-landscape.md:146` · `docs/research/coupling-the-poles.md:85` · `docs/research/empirical-deliberation-convergence-evidence.md:45` · `docs/research/what-a-link-strength-means.md:16` · `docs/research/coupling-the-poles.md:73`\n\n## What a reader found to bear on eleven notes on schemes, relevance and error (2026-10-10)\n\nReport: [2026-10-10-schemes-relevance-and-error-as-a-reader-returned-it.md](readers/2026-10-10-schemes-relevance-and-error-as-a-reader-returned-it.md)\n\ndocs/research/strength-calculus-literature/bayesian-and-informal-logic.md:345 now covers Johnson and Blair, Govier and Hitchcock, but marks the first two \"Not read\" and the third \"Bibliographic only\", so the sweep's \"Not in the corpus\" list is superseded by secondary coverage only (kept out as too thin). The testimony dossier (docs/research/what-counts-as-evidence/testimony-experience-and-normative-evidence.md:455) amends the cheap-to-add positional tiers: corroboration should come from people in the position who \"otherwise disagree\", and the sole-witness label should read as an invitation, not a demotion (also left out as partly already in the note). Counts in the unweighed-answers register (143 of 205 open) are stale by design. Its own text says to read the grep.\n\nPlaces it names in other notes: `docs/research/strength-calculus-literature/bayesian-and-informal-logic.md:345` · `docs/research/what-counts-as-evidence/testimony-experience-and-normative-evidence.md:455`\n\n## What a reader found to bear on a second reading of the same four notes, asked only for kinship (test, reader B) (2026-10-10)\n\nReport: [2026-10-10-second-reading-kinship-brief-four-notes-as-a-reader-returned-it.md](readers/2026-10-10-second-reading-kinship-brief-four-notes-as-a-reader-returned-it.md)\n\nthe words that led to finds came from law and evidence (statement against interest and hearsay; Sunstein's incompletely theorized agreements and the Good Friday fudge), accounting and audit (balance catches inconsistency never omission; reconciliation), record-keeping and data engineering (ground versus derived, bitemporal valid and transaction time, store the uses and read the meaning), forecasting (aleatoric remainder and independent anchors), psychology and economics (illusion of explanatory depth, crowding-out), and statistics (sensitivity under reasonable settings). Head versus tail came from the long-tail vocabulary of the map notes. Searches that found nothing in the corpus: survivorship and Wald's bullet holes, Heidegger and ready-to-hand, Taylorism and codification of tacit knowledge, Lavoisier and idiopathic as state-of-inquiry labels, suspense account, use versus mention, Texas sharpshooter and reference class, Overton window, curse of knowledge, IKEA and generation effect, canalization, Kodak, schema-on-read, grounded theory, factor analysis and the lexical hypothesis. Two near-misses left out: Tao's kernel checking the join (depth.md:155) beside double-entry (fractal-priors-for-success.md:23) looked too generic to change any action, and Edvin's behaviour-over-declaration filter conflicts with unbuilt-features-research-mar31.md:45 (prefer stated preferences), which is a contradiction and not a shared move.\n\nPlaces it names in other notes: `docs/research/fractal-priors-for-success.md:23` · `docs/research/unbuilt-features-research-mar31.md:45`\n\n## What a reader found to bear on a second reading of four notes with the plain brief (test, reader A) (2026-10-10)\n\nReport: [2026-10-10-second-reading-plain-brief-four-notes-as-a-reader-returned-it.md](readers/2026-10-10-second-reading-plain-brief-four-notes-as-a-reader-returned-it.md)\n\nbridging.md:30 says the Procaccia/Konya participants \"shared a room while being shot at\", but ai-augmented-cooperation-infrastructure.md:44 and :63 describe anonymous responses plus votes, a self-selected sample and no control (that note is named on the page, so I could not report it as a finding); empirical-deliberation-convergence-evidence.md:50 measures the moral-reframing result behind bridging.md:44 (fewer than 10% of people reframe spontaneously, 64 to 85% recognise a reframed argument), with the caveat that it is a narrative review; session26-open-rulings.md R10 flags \"machine-rendered other-side lenses\" as a borderline case for worldview-lenses.md:38; cognitive-bias-codex-and-human-contribution.md:246 (belief bias shifts the acceptance threshold, not discrimination) bears on bridging.md:19-22; legibility-under-power-red-team.md:165 warns the sacredness brake protects sacred-register traditions asymmetrically, which bears on the-load-bearing-unsaid.md:122 but is partly mooted by the founder's 2026-08-25 ruling already in found.jsonl; depth.md gained one line while I read, so I re-checked every line number against the file.\n\nPlaces it names in other notes: `docs/research/ai-augmented-cooperation-infrastructure.md:44` · `docs/research/empirical-deliberation-convergence-evidence.md:50` · `docs/research/cognitive-bias-codex-and-human-contribution.md:246` · `docs/research/legibility-under-power-red-team.md:165`\n\n## What a reader found to bear on eight notes on small tasks, live tests and the first screen (2026-10-10)\n\nReport: [2026-10-10-small-tasks-and-live-tests-as-a-reader-returned-it.md](readers/2026-10-10-small-tasks-and-live-tests-as-a-reader-returned-it.md)\n\n(1) A stale TODO.md item still lists the blue-at-0.500 badge as open (lines 2243 and 3352) though the code returns UNEXAMINED. (2) The QC note grew from 810 to 867 lines while I read; I used the current line numbers. (3) I avoided pairs already kept in found.jsonl (islands with the-group-premise-evidence; ux-principles with the QC note). (4) Leads left out for space: kartpaus with grounded-critics-and-quarantined-imagination section 3 (machine pre-answers and the strength layer) and with the-tidying-line section 4a (question-framed showing); deeper-democracy with the-post-that-states-the-problem-from-inside section 6 (such posts are read as centrism); QC with law-intelligence-history-journalism-forensics section 3.5 (retraction not propagated); live-election \"ten-question descent\" is now fourteen (wild-weighing-dialects-and-the-question-set line 3); islands section 5 with parity-and-the-zone-interior line 59 (experience reports are exempt from challenge). (5) Process slip: I created and then deleted a helper file /tmp/ms.sh before I recalled the read-only rule; no repository file was touched.\n\n## Other notes that bear on nine notes about strength, value and the ontology (2026-10-10)\n\nReport: [2026-10-10-strength-and-ontology-notes-as-a-reader-returned-it.md](readers/2026-10-10-strength-and-ontology-notes-as-a-reader-returned-it.md)\n\n(1) The nine notes' inbound/outbound naming was checked by rg on `.md` names; `corpus_graph.py names` lists where a note is named, not what it names. All 14 pairs above were checked: older note's file name absent from the target, and no found.jsonl record holds both names. (2) The squirrel note (AD22/AD23/AD26) yielded no finding: those rows' older bearings are already mined in found.jsonl and the 2026-10-08 listening note; Q22 is the unmined row, and F6 touches it. (3) Pairs read at both ends but cut for space, medium or kinship: decomposing-value.md:88 (a gap between knowing and being moved stays open) against a-cognitive-ecology-and-the-terms-of-the-relation.md:196 (people are the counterexample: commons are kept by rules, monitoring and penalties, not insight); relevance-and-the-two-factors.md:149 (the model name recorded on the edge) against storing-the-record-of-machine-judgments.md:131 (a ruled design, Z1/Z11, replaces per-pass strings with one judgment pointer, which shapes where W3's two conditionals would live); parity-and-the-zone-interior.md:24 (attributed library of traversals) against blobs-community-sandboxes-and-the-advice-process.md:37 (the advice-process outcome as an attributed weighing, the same structure with a live community test-bed); value-weighting-decomposition.md:184 (Argument from Weighing as \"V1 outweighs V2\") against wild-weighing-dialects-and-the-question-set.md:11 and :26 (almost no wild sentence has that form; the CQ set grew from 10 to 14). (4) what-belongs-in-the-ontology.md:200 also says \"all held for ruling\" for its first bullet, which ledger O1 rules.\n\nPlaces it names in other notes: `docs/research/decomposing-value.md:88` · `docs/research/a-cognitive-ecology-and-the-terms-of-the-relation.md:196` · `docs/research/relevance-and-the-two-factors.md:149` · `docs/research/storing-the-record-of-machine-judgments.md:131` · `docs/research/parity-and-the-zone-interior.md:24` · `docs/research/blobs-community-sandboxes-and-the-advice-process.md:37` · `docs/research/value-weighting-decomposition.md:184` · `docs/research/wild-weighing-dialects-and-the-question-set.md:11` · `docs/research/what-belongs-in-the-ontology.md:200`\n\n## What a reader found to bear on eleven notes on strength, the red team and the descent (2026-10-10)\n\nReport: [2026-10-10-strength-red-team-and-descent-as-a-reader-returned-it.md](readers/2026-10-10-strength-red-team-and-descent-as-a-reader-returned-it.md)\n\npairs read at both ends but left out for the cap: docs/open-problems.md:31 (public page) says shared evidence \"is discounted so it isn't counted twice\" while evidence-division line 19 and CLAUDE.md say fair-share is built but NOT adopted, so the public page overstates; heylighen-value-complexity-and-deliberus.md:9 (anti-orthogonality, danger boundary is selection) bears on frontier-extraction-experiment.md:40 (orthogonality and aliveness are the unstated premises of the 3F batch-1 crux), and neither note names the other; red-team-synthesis-2026-07.md:17 (oracle flags braked nodes, \"ships today\") is also hit by the-load-bearing-unsaid.md:109 (brake matched 0 of 1,678 claims), and its :13 immunity gradient reappears in four-cuts-of-the-ai-debate.md:222 for machine moral patienthood, its :49 cycle point is measured in strength-layer-audit.md:31 (3 two-cycles, 1 three-cycle) and its :46 uptake metric has a computable form in peer-review-and-the-reasoning-layer.md:69; peer-review :97 (anonymity, chilling) has legibility-under-power-red-team.md:186 (Chatham House rule, measured chilling); what-the-necessary-default-changes.md:41 (remove the reward, do not police) has twins at ai-slop-and-the-reasoning-layer.md:37 and relevance-and-the-two-factors.md:189; strength-layer-audit.md:103 (sentinel rule) has data-layer twins in session39-what-the-graph-stopped-claiming.md:105 and the-residual-error-taxonomy.md:97 (dead instruments believed alive); weighing-scheme-and-terminus-classifier-design.md:109 (auto-open leans yes) is narrowed by the personal-domain carve in kartpaus-auto-enrichment-design.md:34, and its :65 (frontier-grade classifier) lacks the ask-twice steadiness test in pass-quality-and-the-choice-of-model.md:150. The helper report the-squirrel-and-the-strength-calculus/strength-rulings-and-code-as-read-2026-10-08.md is a compact map of every strength ruling with founder words.\n\nPlaces it names in other notes: `docs/open-problems.md:31` · `docs/research/the-load-bearing-unsaid.md:109` · `docs/research/four-cuts-of-the-ai-debate.md:222` · `docs/research/legibility-under-power-red-team.md:186` · `docs/research/relevance-and-the-two-factors.md:189` · `docs/research/session39-what-the-graph-stopped-claiming.md:105` · `docs/research/the-residual-error-taxonomy.md:97` · `docs/research/kartpaus-auto-enrichment-design.md:34` · `docs/research/pass-quality-and-the-choice-of-model.md:150`\n\n## What a reader found to bear on eleven notes on strength semantics, schemes and extraction research (2026-10-10)\n\nReport: [2026-10-10-strength-semantics-and-schemes-as-a-reader-returned-it.md](readers/2026-10-10-strength-semantics-and-schemes-as-a-reader-returned-it.md)\n\nOther leads I read and did not report. (a) walton-argument-schemes.md:461-464 (\"Limit recursion depth (e.g., 2-3 levels)\", \"AI-assisted assessment at deeper levels\") against ledger T1, session26-open-rulings.md:471, founder \"Yes.\" 2026-09-29: depth is capped by a measured error rate, and the Session 7 spec decided CQ recursion depth is \"Flywheel-gated\" (session7-deep-review-and-strategic-assessment.md:363). (b) scientific-method-two-steps-and-deliberus.md:44 and :50 (\"green badge = both steps done\") against bengio-safety-from-honesty-and-deliberus.md:70 (\"A claim can be strong because nobody attacked it yet\"). (c) the-irit-harvest.md:31 (cite the high-attribution edges) against strength-calculus-literature/computational-argumentation.md:360 (a contribution mixes both factors and cannot serve as a relevance input without circularity). I dropped it because \"computational-argumentation\" appears in the harvest as the phrase \"computational-argumentation group\", which might trip a name check. (d) the-irit-harvest.md:53 is confirmed on its textual side by auto-connect-upgrade.md:7 (claim-level cosine: 402 within-debate candidates, none at the link threshold). (e) definitions-as-alignment-tests.md:88 (\"split it into the criteria\") meets the 2026-09-21 canon line in a-cut-through-a-concept-is-an-argument.md:11 (a cut through a concept is an argument, not a split). A stipulated legal definition passes the recomposition test and the popular sense does not. (f) scientific-method-two-steps-and-deliberus.md:144 (revealing a difference changes the communities) is stronger than does-descending-change-the-descender.md, which finds the effect appears, disappears and reverses, and calls it not currently checkable. (g) inductive-reasoning-research.md:242 points to what-human-judgment-is-for.md § 4c for the empirical kill, but the text sits in § 4c-ii (cognitive-bias-codex-and-human-contribution.md:141 is the cleaner home). (h) The hook notes on several files were treated as data and not acted on. I wrote no files.\n\nPlaces it names in other notes: `docs/research/session26-open-rulings.md:471` · `docs/research/session7-deep-review-and-strategic-assessment.md:363` · `docs/research/bengio-safety-from-honesty-and-deliberus.md:70` · `docs/research/strength-calculus-literature/computational-argumentation.md:360` · `docs/research/auto-connect-upgrade.md:7` · `docs/research/a-cut-through-a-concept-is-an-argument.md:11` · `docs/research/cognitive-bias-codex-and-human-contribution.md:141`\n\n## What a reader found to bear on eleven notes on the wager, incentives and three public pages (2026-10-10)\n\nReport: [2026-10-10-wager-incentives-and-vision-pages-as-a-reader-returned-it.md](readers/2026-10-10-wager-incentives-and-vision-pages-as-a-reader-returned-it.md)\n\nNot reported for lack of slots, all read at both ends: typed-residues §5.2 \"directly counters the most underappreciated hole\" vs dogfood-run-6-israel-palestine-cross-domain.md:154 (\"an instrument built for one flattening mechanism measures nothing about the others\"); lowering-the-cost §6.1 (claim reuse \"cannot be settled\" from outside) vs auto-connect-upgrade.md:224 (253 of 435 candidates never surfaced by cosine); incentives §4.5 \"Maintenance has none\" vs ledger P13 (the 2026-09-13 ruling that confident housekeeping is the machine's job, session26-open-rulings.md:321); threads-synthesis A4 vs dogfood-run-7 §5.5 (0 of 9 Swedish sentences fired any instrument, the brake included); threads-synthesis C7's \"absent entirely\" for pragma-dialectics vs what-a-link-rests-on/outside-reading-argumentation-theory.md:72 (van Eemeren and Garssen 2026, full text read); analysis-and-attunement.md:9 (\"something was missing, the other pole\") vs conviction-and-critique.md:27 (the twenty platforms failed on input friction) and incentives §1; science-lineage \"Deliberus already embodies this through Walton schemes\" vs ledger AG1 (1 of 1,569 live links has anything under it). The founder's tile rulings that overtake constellation candidates 1, 8, 9, 14 and 26 (Show the work, Being vague is safe, Supporting is easy, You never owe us a contribution, Only you can say whether a retelling of your view is fair) are recorded only in specs/landing-redesign/constellation-map.md, outside docs/.\n\nPlaces it names in other notes: `docs/research/dogfood-run-6-israel-palestine-cross-domain.md:154` · `docs/research/auto-connect-upgrade.md:224` · `docs/research/session26-open-rulings.md:321` · `docs/research/what-a-link-rests-on/outside-reading-argumentation-theory.md:72` · `docs/research/conviction-and-critique.md:27`\n\n## What a Haiku 5.5 reader found to bear on four top-level pages, asked only for kinship (model test, second run) (2026-10-11)\n\nReport: [2026-10-11-four-top-level-pages-kinship-as-a-haiku-reader-returned-it.md](readers/2026-10-11-four-top-level-pages-kinship-as-a-haiku-reader-returned-it.md)\n\nthe mechanism and vocabulary-search fields led to the finds; searches on boundary objects, pharmacovigilance, value of information, Hirschman exit, Goodhart and sycophancy gave nothing usable.\n\n## What does not fit on the page that describes the built system, as a reader returned it (2026-10-11)\n\nReport: [2026-10-11-pages-what-does-not-fit-architecture-reference-as-a-reader-returned-it.md](readers/2026-10-11-pages-what-does-not-fit-architecture-reference-as-a-reader-returned-it.md)\n\nSmaller drifts I did not report as pairs. (a) L45 cites `client.py:178` for `_CAPACITY_MARKERS`; it is now line 184. (b) L161 says LLM-invoking POST routes are limited to 3–10/minute and that the \"1/minute\" note was stale, but `generate-titles` and `embeddings/generate` still carry 1/minute. (c) L83 lists three Postgres tables, while the code defines about twelve. (d) L544 says \"marked as nobody's\", which is the wording AG12 replaced with \"a claim nobody asserts\". (e) L300 describes the 2026-08-19 landing as current, and only L303 says it is hidden (`showDerivation = false`). (f) L71 gives the previous pipeline as 46 claims, while the cited first-pipeline-run-analysis.md says 44. (g) L75 says \"No JSON files on disk\", but deliberus/cli.py writes per-pass JSON. (h) L457 says the graph is reached \"via Graphiti MCP\", while L41 says direct falkordb-py. (i) L49's \"only three of the 25 call sites store\" which model served is partly overtaken by the shared judgment record (Z1, live 2026-10-06), though the doc cross-references still repeat it. (j) L43's correction mark refers to \"separate keys and isolated billing accounts\" above it, but nothing above mentions them.\n\n## What does not fit on the three vision pages, as a reader returned it (2026-10-11)\n\nReport: [2026-10-11-pages-what-does-not-fit-three-vision-pages-as-a-reader-returned-it.md](readers/2026-10-11-pages-what-does-not-fit-three-vision-pages-as-a-reader-returned-it.md)\n\nNot reported, as likeness, already held in found.jsonl, or too thin: vision.md:353 (\"The `@[simp]` flywheel works\") has the same older passage as F13; vision.md:9 and 343 call the worldview lens the soul of the product in the present tense, while coupling-the-poles.md:103 and TODO.md:2965 say the whole-graph lens is the larger vision still to come, and no lens code exists; vision.md:313 says \"ONE shared deliberation graph\" while deliberus/community.py gives each community its own graph store (vision.md:323 argues the membrane in principle); vision.md:178 still says \"terminus\" (ledger O2 renames it, code rename parked); vision.md:355 gives 2,130 claim nodes for 11 extractions where session12 gives 792 claims, probably nodes versus claims; the-missing-layer.md:58 says summary doors stay honest through the inspectable-synthesis machinery, but saturation-and-the-long-tail.md § 3 item 4 says the map view, now the main door, is a summary by selection with no omissions line; civilizational-vision.md:49 maps Lean's kernel to \"value bedrock\", while lean-deliberus-analogies.md:164–176 maps the kernel to structural rules only; and docs/research/the-post-that-states-the-problem-from-inside.md names a private person in a public note, against the .private/ principle.\n\nPlaces it names in other notes: `docs/research/coupling-the-poles.md:103` · `TODO.md:2965` · `docs/research/lean-deliberus-analogies.md:164`\n\n## What does not fit on the page of UX principles and the design guide, as a reader returned it (2026-10-11)\n\nReport: [2026-10-11-pages-what-does-not-fit-ux-principles-and-design-guide-as-a-reader-returned-it.md](readers/2026-10-11-pages-what-does-not-fit-ux-principles-and-design-guide-as-a-reader-returned-it.md)\n\n(1) docs/ux-principles.md:213 says \"Three-pass pipeline: holistic scout → focused extraction → cross-structure analysis\", while line 342 and docs/architecture-reference.md:23 say eight-pass. That is a real number clash, but line 213 has only 7 words, so I could not quote it as a block. (2) P20 (line 348), P21 (line 364) and P23 (line 398) all call pointing at claims \"the one signal that would redirect the whole build\"; F10 covers P20, and P23 at least points to the modality caveat. (3) P3 line 72 and anti-pattern 4 say the extracted-structure confirmation step is non-optional, and the diagram at line 231 shows [EDIT][LOOKS RIGHT][DISCARD]. I found no such step in the code: the extraction page has no confirm, publish or discard control. The 2026-08-31 \"no ratify act\" end-state and the retired `confirmed` field (Q32) leave only the author's consent channel. (4) Anti-pattern 7 (line 441), \"Their evaluations produce the quality scores\", sits against Option B, and P8's \"Your quality rating\" does too. (5) design-guide.md:306 points to epistemic-gamification.md as \"two-axis voting\" with no mark that Option B decided against it; I judged this a summary, not a clash. (6) design-guide.md:9 says Manrope weights 400-800, but app.html loads only 400-700 while the logo and h1 ask for 800. (7) P17's \"60% quality threshold\" and \"Bayesian surprise ranking\" have no counterpart in deliberus/feed.py (the feed has 8 modes, as the guide says); the page frames them as principles. (8) Design-guide key principle 6 says claim text \"anywhere\" must link, while P23 and MapCanvas.svelte leave the page's own focal claim unlinked. (9) ux-principles.md:20 says CLAUDE.md carries \"nine hard directives\", but § UX/Product Directives now lists 13 bullets plus the separate claim-is-a-link directive. (10) ScopeSwitcher.svelte shows a faint \"Deliberus\" control to members while they are in the commons, which sits slightly against P25's \"No badge when you are in the commons\".\n\nPlaces it names in other notes: `docs/architecture-reference.md:23`\n\n## What a Haiku 5.5 reader found that does not fit, in four notes (pilot) (2026-10-11)\n\nReport: [2026-10-11-pilot-what-does-not-fit-four-notes-as-a-haiku-reader-returned-it.md](readers/2026-10-11-pilot-what-does-not-fit-four-notes-as-a-haiku-reader-returned-it.md)\n\nload-bearing-unsaid.md:35 calls implicit-premise recall \"already this project's most important quality axis\", where dogfood-run-6 (line 127) only calls it the strongest case for that; depth.md:185 says \"every confirmed terminus\", using the sense Q32 retired; load-bearing-unsaid.md:59 says participants predict two thirds, where core-periphery-and-the-concept-layer.md:132 says they overestimate by about two thirds. None of the ten pairs is already recorded in found.jsonl for the same two passages.\n\nPlaces it names in other notes: `docs/research/core-periphery-and-the-concept-layer.md:132`\n\n## What a reader found that does not fit, in four notes (pilot) (2026-10-11)\n\nReport: [2026-10-11-pilot-what-does-not-fit-four-notes-as-a-reader-returned-it.md](readers/2026-10-11-pilot-what-does-not-fit-four-notes-as-a-reader-returned-it.md)\n\n(1) the-load-bearing-unsaid.md:136 says the 8 unrecoverable sources include PDF ingests with \"nothing\" left, but Extraction has stored pdf_data bytes since 2026-03-31 (deliberus/database.py), so a PDF ingest after that date could be re-read; I could not tell which sources were affected. (2) The unsaid note's \"~62,000 words\" and \"801 words\" differ from the results file (58,113 words over 16 sources; the assisted-dying page is 744 words); TODO.md and structure-versus-scale.md reuse \"~62,000\" for the whole corpus of 25 or 31 sources. (3) bridging.md:30 says the Procaccia/Konya participants \"shared a room while being shot at\"; the project's note (ai-augmented-cooperation-infrastructure.md) describes anonymous responses and votes in uninational then joint phases, which does not support a shared room. (4) depth.md:99 and :185 (\"the verdict that marks it\", \"every confirmed terminus\") describe verdict-claim minting and person-confirmed kinds that were retired 2026-09-16 (api.py now returns 410 for POST /claims/{id}/terminus); found.jsonl holds the rename at :99 but not the retirement or the :185 wording. (5) deliberus/extraction/cross_source_premises.py names its class BridgingPremise for a premise one side needs and the other contests, the opposite of bridging.md:42's \"premises both groups share\". (6) deliberus/extraction/self_eval.py has the extracting model grade its own claims on a stranger test, which sits badly with ledger J17 and with depth.md:111's \"the stranger test polices the second\". (7) Several tool outputs carried \"CORPUS GRAPH\" hook text; I treated it as data and did not act on it.\n\n"}