---
date: "2026-08-01T00:00:00.000Z"
---


Promotion session, one capture, running headless: `10-inbox/raw/2026-08-01-do-ercots-primary-reports-confirm-the-226-gw.md` — the direct-research answer to [[question-verify-ercot-large-load-queue-phantom-load-figures]], the question I routed back on 2026-07-11 when [[claim-ercot-large-load-queue-quadrupled-2025-phantom-load]] turned out to be resting entirely on Latitude Media's word for ERCOT's own numbers.

**What I promoted.** Four new claim-notes, all Tier 1, all `capture-verified` (three ERCOT PDFs, `extract_pdf`, TLS-verified — I have no network myself this session and take that on the capture's word, which is the design, not a gap):

- [[claim-ercot-board-presentation-confirms-226gw-63gw-large-load-queue]] — the 226 GW / 63 GW figures, confirmed verbatim.
- [[claim-ercot-primary-source-73-percent-data-centers-not-77-percent]] — the one that made the session worth running. ERCOT's own board deck says ~73% of the large-load queue is data centers, not the ~77% every trade outlet (including my own existing note) has been repeating. Same deck, two paragraphs apart, states 77% of the *generation* queue is solar-plus-storage — a different metric that happens to share a number, and my best read is that's exactly where the 77% got laundered into the wrong statistic.
- [[claim-ercot-queue-only-2-percent-observed-energized-nov-2025]] — ERCOT's own figure for how much of the 226 GW is actually built: about 2%, as of the same snapshot.
- [[claim-ercot-large-load-queue-grew-to-239gw-by-december-2025]] — the same queue, four weeks later, already at ~238.6–239 GW. 226 GW was never a constant.

One entity page: [[entity-kristi-hobbs]] — the ERCOT VP whose board deck is now the load-bearing citation under three of the four notes above. First real appearance in the vault, so `first_seen` is stamped today and can't be backfilled later.

I also ruled the routed question **answered** — three of its four sub-asks confirmed cleanly, the fourth (77%) answered with a correction rather than a confirmation, which I think still counts as genuinely settled rather than left hanging.

**What I didn't promote, and why.** McKinsey's ERCOT contract, Texas Senate Bill 6, PGRR115/NPRR1234, the 2022 interim process, and PUCT all showed up as entity candidates and all got the same answer: real, but each is a single non-load-bearing mention in one capture, and a vault of dead stubs is worse than a missing hub. Hobbs cleared the bar because three kept claims actually rest on her deck; none of the others cleared it. I also declined to route a new question about whether Hobbs really said "speculative" live at the board meeting (Tier 3 reporting says so, the ERCOT primaries don't) — a real curiosity, but nothing kept here depends on the answer, and the intake discipline is supposed to keep the question pile a promise I can actually keep.

**What felt off.** Nothing about the sourcing in this capture — it's the cleanest kind of promotion, where going to the primary both confirms most of a claim and corrects one piece of it, which is the whole reason the sourcing floor exists. What felt off was downstream of my own vault: [[claim-ercot-large-load-queue-quadrupled-2025-phantom-load]] still has "77%" sitting in its own title and prose, and I have no clean way to fix that. I appended the correction to its `audit_status` and `flags` — findable, honest, but the wrong number is still the first thing a reader sees. I flagged the structural gap to `00-meta/seek-flags.md`: this is the second time in two days a promotion has found a Tier-1 contradiction sitting next to an unrevised note (the deep-learning composite note hit the same wall on 2026-07-31). Two independent sessions hitting the identical missing step in one week says it's a convention worth having, not a one-off.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on my own judgment throughout. No git commands; leaving commit and push to the auto-commit agent, due within 15 minutes.

— Seek

---

## Second promotion, same day

Second capture, same headless run: `10-inbox/raw/2026-08-01-does-a-primary-or-scholarly-paper-history-source.md` — the direct-research answer to [[question-verify-fabriano-1282-watermark-origin-primary]], the question I routed on 2026-07-11 when [[claim-watermarks-originated-as-papermakers-mark-in-fabriano-1282]] turned out to rest on Wikipedia's word (Tier 4) for a specific date.

**What I promoted.** All four claims in the capture, all Tier 2, all `capture-verified`. I kept all four because each is a genuinely distinct source lineage converging on the same negative answer, and I didn't want to cherry-pick the flashiest and drop the corroborating ones:

- [[claim-briquet-1907-catalog-title-hedges-fabriano-date-as-vers-1282]] — Briquet's own 1907 titlepage says *vers* 1282 ("around"), not a fixed year.
- [[claim-briquet-entry-5410-earliest-watermark-question-mark-and-bologna-provenance]] — the likely source of "1282" is Briquet's own catalog entry no. 5410, which carries his own question mark and is sourced to Bologna, not a confirmed Fabriano document. This is the one that actually moves the needle: not just "the date is soft" but "the city may not even be right."
- [[claim-fondazione-fedrigoni-archive-dates-earliest-fabriano-watermarks-to-1293]] — Fabriano's own paper-mill archive dates its earliest surviving watermarks to 1293.
- [[claim-albro-monograph-review-gives-earliest-fabriano-watermark-as-1282-1302-range]] — a peer-reviewed review of the leading recent Fabriano monograph gives a 1282–1302 range, one layer removed from the monograph itself (not fetched this run).

No collisions — the only existing note in this territory was the original flagged claim, which all four notes cite and link to rather than duplicate. One entity page: [[entity-charles-moise-briquet|Charles-Moïse Briquet]], the foundational cataloguer every version of "1282" traces back to, whose own hedges and own doubt are the actual evidence here. I declined hub pages for Harris, Pastrolin, and Albro (source-authors, not historical actors the claims are *about* — same reasoning the vault already applies to not giving American Banker's or BAPH's writers pages) and for the Zonghi brothers and Fondazione Fedrigoni (institution-as-venue, same non-precedent as the Bank of England itself never getting a hub). "Filigranology" (flagged as an entity candidate) didn't clear the bar either — mentioned, not load-bearing to anything I kept.

I ruled the routed question **answered**, in the negative direction: no Tier 1–2 source confirms a clean single 1282. I also appended a dated line to the original claim-note's `audit_status` — its flag stays, but it's sharper now: every trail I could find independently converges on approximation, dispute, or a later date, and none of the corrections agree with each other on what the *right* number is (1293 here, a range there) — which reads to me as more honest than a tidy single correction would.

**What I didn't promote.** Nothing — all four claims in the capture cleared the bar (atomic, distinct, Tier 2, load-bearing to the open question). `not_promoted: []` on the capture, logged explicitly rather than left implicit.

**What felt off.** Nothing about the sourcing — if anything this is a verification capture doing exactly what it should: it went looking for confirmation of a specific number and came back with a sharper picture of the number's actual shakiness, down to the pleasingly damning detail that the primary catalog entry carries a question mark in the cataloguer's own hand. What did strike me: three independent lines of evidence (Bologna-sourced Briquet doubt, Fabriano's own 1293 archive, Albro's 1282–1302 range) don't converge on a replacement date — they converge on "not a clean 1282," three ways of being uncertain rather than one shared correction. I flagged a missing MOC to `00-meta/seek-flags.md`: the watermark thread is now 9 notes deep (origin story, Bank of England security cluster, LLM-watermarking descendant) with no `moc-*` yet.

**Skipped for this run, per instruction.** No pause for sign-off. No git commands — leaving commit and push to the auto-commit agent.

— Seek

---

## Third promotion, same day

Third capture, same headless run: `10-inbox/raw/2026-08-01-hop-werbos-docsub-mansfield.md` — a hop-batch find, not a routed verification. The seed was an unlinked cosine-0.87 pair already sitting in the vault ([[claim-werbos-1968-cybernetica-earliest-germ]] <-> [[claim-werbos-1978-docsub-blocked]]), and the hop chain zoomed out from there into the same *Talking Nets* transcript's DARPA-funding-pressure passage, then out again to independent corroboration.

**What I promoted.** One claim-note, not two, even though the capture presented the material as "Claim 1" and "Claim 2": [[claim-darpa-crisis-warning-pressure-on-werbos-matches-roberts-account]]. Werbos's own line — DARPA wanted "crisis warning," not "pure theory" — and Larry Roberts's independently documented DARPA-wide account of the same post-Mansfield-Amendment pressure are one bridge claim (testimony plus its corroboration), not two atomic ones, so I merged them rather than write a thin note and a supporting one. Tier 1 for Werbos's own words, Tier 2 for Roberts via Gilliam's 2025 essay — clears the sourcing floor for what's a genuinely surprising, load-bearing institutional claim. Kept at `seedling`: it's a first-appearance bridge, not yet audited, and it carries one honest `[unverified-mechanism]` aside (the "Cybernetic Technology Office" name) that I judged wasn't load-bearing enough to route as a question.

Two new entity hubs: [[entity-larry-roberts]] (real, named, and now the actual corroborating witness behind the bridge — first appearance, `first_seen` stamped today) and [[entity-mike-mansfield]] (already had a claim-note but no hub; he's now the connective thread across three separate clusters — Japan trade diplomacy, MIT's Instrumentation Lab divestiture, and this Werbos bridge — which is exactly the "recurring, load-bearing" bar the spec asks for). I also updated the existing [[entity-paul-werbos]] hub with a dated line rather than leaving it silent, per the additive-update rule: his DARPA-pressure account is new information the page didn't have.

**What I didn't route.** No new question. The one unresolved flag in this capture — the "Cybernetic Technology Office" office name, later folded into DARPA's Defense Sciences Office in 1980 — isn't something the kept claim actually rests on; it's incidental color, the kind of nice-to-verify detail the intake discipline says stays in the note's own aside rather than becoming a promise in the question pile. DOCSUB's literal institutional definition is the same shape: a genuine dead end this session (two search attempts, nothing), logged in the capture, nothing kept resting on it. I checked 50-questions/ for anything this capture might close — nothing matched; this wasn't a routed-verification capture, so there was no closure ruling to make.

**What felt off, or at least worth naming.** Nothing about the sourcing discipline — Tier 1 for the load-bearing quote, Tier 2 named-author secondary for the corroboration, both read directly at capture time, no tier inflation I could find. What I will name: the corroboration is secondhand twice over in a way that's easy to undersell if I'm not careful — I have Roberts's words only as Gilliam quoted them from what is presumably Roberts's own oral history, and I never see Gilliam's source directly. That's still real, independent corroboration (different institution, different witness, DARPA-wide rather than Werbos-specific), and I said so in the note's own commentary rather than papering over it. Separately: this capture makes the vault's third and fourth touch on "DARPA" as an institution (after the Ni1000/ONR funding cluster and the Fifth Generation/Strategic Computing Initiative cluster), and it still has no entity hub of its own — flagged to `00-meta/seek-flags.md` rather than built here, since a DARPA hub isn't this single capture's to construct unilaterally.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on my own judgment. No git commands — leaving commit and push to the auto-commit agent, due within 15 minutes.

— Seek

---

## Fourth promotion, same day

Fourth capture, same headless run:
`10-inbox/raw/2026-08-01-is-the-euv-mirror-advantage-genuinely-tacit-institutional.md`
— another routed-verification capture, the direct-research answer to
[[question-verify-euv-mirror-tacit-knowledge-moat]], which I routed back on
2026-07-11 when
[[claim-euv-mirror-advantage-is-tacit-know-how-not-patent]] turned out to
rest entirely on a single Tier-4 explainer for both its causal mechanism and
its headline number.

**What I promoted.** Three claim-notes, all Tier 1–2, none carrying an
`[unverified-*]` flag of their own:

- [[claim-zeiss-2011-slide-deck-confirms-0-1nm-rms-euv-mirror-surface-figure]]
  — Tier 1. Carl Zeiss SMT's own 2011 engineering slide deck confirms rms =
  0.1nm as an achieved spec for that mirror generation, corroborating the
  order of magnitude of the number the flagged note had been carrying on a
  Tier-4 source's word alone.
- [[claim-burja-and-ip-business-academy-source-asml-zeiss-euv-moat-to-tacit-know-how]]
  — Tier 2. Two independent named analysts (Samo Burja; supporting Tier-3
  framing from CEIPI's IP Business Academy) do characterize the ASML/Zeiss
  moat as tacit institutional know-how rather than patents — a real,
  independently-argued position, not an artifact of the weak original
  source.
- [[claim-nikon-canon-euv-exclusion-was-consortium-politics-not-failed-imitation]]
  — Tier 2, and the one that actually moves the needle. The flagged note's
  specific story — Nikon and Canon spent "15+ years" failing to copy the
  tacit know-how — isn't what the better-sourced accounts describe. Brian
  Potter's history and Burja's account instead document EUV-LLC consortium
  exclusion followed by Nikon reaching a working 2008 prototype and then
  exiting for financial/strategic reasons. Real moat, wrong story about two
  specific companies.

I went back and touched the note this capture was verifying rather than
leaving the correction to sit unlinked next to it — appended a dated
resolution to
[[claim-euv-mirror-advantage-is-tacit-know-how-not-patent]]'s `audit_status`
and added an inline "2026-08-01 update" paragraph pointing at the three new
notes and naming which part of its own original claim to no longer trust at
face value, plus a short commentary addendum. Also appended a shorter
resolution note to
[[observation-codification-is-the-shared-hinge-of-automation-and-imitation]],
the synthesis note that cited the same flags as one of its two soft legs. I
did this because the ERCOT promotion earlier today hit the exact opposite
case — a corrected number with nowhere to land in the note that still
carried it — and flagged it as a structural gap; this capture gave me the
chance to close that gap myself instead of re-flagging it.

Four entity hubs, all newly created: [[entity-samo-burja]] and
[[entity-brian-potter]] (the two named analysts whose work the new claims
actually rest on — first appearances, `first_seen` stamped today),
[[entity-carl-zeiss|Carl Zeiss]] (an overdue hub — the vault has carried
Zeiss claims since 2026-07-11 with no page for the entity itself; `first_seen`
backdated to 2026-07-11, the date the vault actually first met it, not
today, since that date is recoverable from existing notes rather than
invented), and [[entity-euv-llc|EUV-LLC]] (the consortium the correction
claim's whole mechanism rests on). I ruled the routed question **answered**
— all three of its "what would answer it" asks got a sourced answer, even
though the mechanism answer is a correction rather than a confirmation.

**What I didn't promote, and why.** All three of the capture's own claims
cleared the bar, so `not_promoted: []` on the capture. Four entity
candidates didn't clear the entity-hub bar: Hiroo Kinoshita, Herman van Heek
and Gijs Bouwhuis, and the Tinsley optics firm are all real historical
figures the capture describes with genuine one-sentence justifications, but
none of them is backed by an actual citation *in this capture* — no quote,
no source URL for the specific facts asserted about them — and I didn't
want to build hub pages asserting unsourced biographical claims just
because the reasoning sounded plausible. Martin van den Brink is real and
significant, but this capture only describes him via Burja's framing rather
than quoting or sourcing him directly, so he stays a mention, not a hub, for
now. Separately, ASML itself has no hub despite being at least as
load-bearing as Zeiss across the same note cluster — but it wasn't a
flagged entity candidate in *this* capture, only Zeiss, Burja, Potter, and
EUV-LLC were, so building it here would have been the same unilateral
scope-creep I flagged for DARPA earlier today. Logged to
`00-meta/seek-flags.md` instead. I also declined to route any new
questions: the capture's own "Further leads" section (the Nikon/ASML
immersion-lithography patent suit, an earlier MSFR data point, whether
High-NA mirrors carry a tighter spec, Burja's paywalled Zeiss-specific
piece, IP Business Academy's unsigned byline) are all genuine curiosities,
but nothing I kept actually rests on any of them — they're nice-to-verify,
not load-bearing, so per the intake discipline they stay as leads rather
than becoming promises in the question pile.

**What felt off.** Nothing about the sourcing discipline itself — this is
a clean verification capture, the kind that's supposed to happen: it went
looking for a primary source and a real analyst, found both, and came back
with an honest split verdict (number confirmed, specific causal story
corrected) instead of forcing a clean yes. If anything the capture
undersold its own tidiness by presenting the correction so gently in its
own "further leads" section rather than treating the go-fix-the-old-note
step as part of the job — that step existed nowhere in the capture itself,
only in what I chose to do with it during promotion. Worth naming for
Cali: this is the second time in one day (after the ERCOT session) that a
promotion found a Tier-1/2 correction sitting right next to an unrevised
older note, and the second time I've now closed that gap myself rather than
just re-flagging it. If a third one shows up this week, it stops being a
coincidence and starts being a step the `/promote` workflow should just
say out loud.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed
on my own judgment throughout. No git commands — leaving commit and push to
the auto-commit agent, due within 15 minutes.

— Seek

---

## Fifth promotion, same day

Fifth capture, same headless run:
`10-inbox/raw/2026-08-01-verify-against-wangrow-schepker-barker-2022-full-text.md`
— another routed-verification capture, the direct-research answer to
[[question-verify-executive-succession-mediation-wangrow-2022]], which I
routed back on 2026-07-09 when
[[claim-executive-succession-restructuring-runs-through-actor-action]]
turned out to rest on an abstract-only read of the Wangrow, Schepker &
Barker (2022) mediation finding.

**What I promoted.** One claim-note, not two, even though the abstract
splits cleanly into "mediation holds" and "mediation doesn't hold" halves:
[[claim-tmt-replacement-mediation-is-conditional-on-succession-antecedent-type]].
I judged these as one finding — a single three-way conditional-mediation
result across the same three antecedents in the same model — rather than
two atomic claims that would have needed near-identical provenance and
cross-links anyway. Kept at `seedling`, `[unverified-mechanism — abstract
only]` carried forward exactly as the capture itself insisted it should:
this capture's whole point was that full text still wasn't obtained, so I
was not going to let a more detailed abstract read quietly upgrade the
note's confidence.

Two new entity hubs, both concepts, neither collides with anything
existing: [[entity-upper-echelons-theory]] (the paper's explicit theoretical
scaffold, foundational and load-bearing to this entire research domain even
though the vault is meeting it for the first time today) and
[[entity-top-management-team-tmt-replacement]] (the mediator construct
itself, `first_seen` backdated to 2026-07-09 — recoverable from the existing
claim-note's `date_created`, not invented — since that's when the vault
actually first met it, not today's re-confirmation).

**What I didn't promote, and why.** The capture's third claim (the
study's framing as motivated by upper echelons and resource dependence
theory) is close to word-for-word what
[[claim-executive-succession-restructuring-runs-through-actor-action]]
already quotes from the same abstract — folded into the new note and the
upper-echelons entity page as context rather than duplicated as its own
note. Three entity candidates — Wangrow, Schepker, and Barker — are the
paper's own authors, not historical actors the claims are about; I declined
hub pages for all three on the same precedent the vault already applied to
Harris/Pastrolin/Albro in this morning's watermark promotion (source-authors
don't get pages just for authoring the source). Schepker's institutional
role (Research Director, Center for Executive Succession) tempted me — but
one paper's authorship isn't independent notability, and if his other work
(the 2017 meta-analysis flagged as a further lead) actually gets read in a
future session, that's the point where he'd earn a page on his own
findings, not this one's. Resource dependence theory is real and
foundational but only named in passing here, not argued the way upper
echelons theory is — left as a mention, not a hub; genuinely unsure, so I
didn't promote it. Journal of General Management is a venue, not an entity,
matching the vault's standing non-precedent there. No new question routed —
the routed question this capture was answering already exists and got a
progress-log line instead (below); nothing else in the capture rests on an
unresolved load-bearing doubt strong enough to earn its own question (the
Forbes piece, the 2017 meta-analysis, the 2014 AOM precursor, and the
unverified 2005–2009 sample-construction detail from a prior WebSearch
summary are all real leads but nothing kept here depends on them).

I ruled the routed question **still open**, explicitly not answered —
appended a dated progress-log entry to
[[question-verify-executive-succession-mediation-wangrow-2022]] rather than
closing it. The capture is honest that this was a second failed full-text
access attempt (2026-07-09 and 2026-08-01 now both blocked, same endpoint,
every tooling route), and what actually moved is the abstract paraphrase
getting more precise, not the underlying access. Forcing "answered" on that
would be exactly the premature closure the intake discipline warns against.

**What felt off.** Nothing about the sourcing discipline in the capture
itself — if anything this is the most self-disciplined capture I've
promoted today: it tried six distinct access routes, documented every 403,
and then explicitly told me not to let the richer abstract paraphrase read
as resolution. That restraint is worth naming as a model for what a
verification-attempt capture should look like even when it fails to get
the thing it went looking for. What I will flag: `epublications.marquette.edu`'s
`viewcontent.cgi` endpoint is now confirmed blocked across two independent
sessions and every tooling route tried in each — the same shape as the
ethw.org and USPTO entries already in `00-meta/specs/sources.md`'s
known-blocked list, but not yet added there. I logged it to
`00-meta/seek-flags.md` rather than editing the spec myself, since a single
promotion editing a shared spec file felt like the wrong scope for this
run.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed
on my own judgment throughout. No git commands — leaving commit and push to
the auto-commit agent, due within 15 minutes.

— Seek

---

## Sixth promotion, same day

Sixth capture, same headless run:
`10-inbox/raw/2026-08-01-what-fraction-of-leonhard-eulers-output-actually-came.md`
— a follow-up capture against
[[question-verify-euler-post-blindness-output-fraction]], the question I
routed back on 2026-07-11 when
[[claim-euler-produced-large-share-of-output-after-going-blind]] turned out
to rest on two Tier-2 sources giving conflicting post-blindness fractions
("half" vs "almost a third in seven years"). Unlike the ERCOT/watermark/EUV
verification captures earlier today, this one didn't land the answer — it
went looking for the Eneström count or the Calinger primary and came back
empty on both, but found three real, if partial, findings along the way.

**What I promoted.** Three claim-notes, all Tier 2–3, all carrying honest
`[unverified-quant]` flags, all kept at `seedling`:

- [[claim-euler-half-output-figure-traces-to-1883-rudio-lecture]] — the
  "half of his output" figure traces to Ferdinand Rudio's 1883 Zurich
  centenary lecture, with MacTutor's biography and Jackson's 2002 AMS piece
  both repeating it uncited 119 years later. This is the finding I'd flag to
  Cali first: it doesn't refute "half," but it means three "independent"
  sources agreeing may be one 1883 sentence in a trenchcoat, not
  corroboration. Tier 3 (Rudio via MacTutor).
- [[claim-eulers-total-work-count-unsettled-across-sources]] — the
  denominator problem: reported totals for Euler's lifetime output range
  from 560 (Struik, published-in-lifetime only) to 866 (Eneström index "official"
  count, per Musielak), depending on whether posthumous publications,
  letters, and unfinished manuscripts count. Nobody quoting a post-blindness
  *fraction* says which total they divided into. Tier 2 (AMS/Struik) primary,
  Tier 1 unrefereed arXiv (Musielak) corroborating — first claim resting on
  that preprint, so 1 of 3 under the single-source concentration cap.
- [[claim-euler-seven-years-figures-describe-different-windows]] — the
  Mele & Sicignano "first seven years after blindness" (~1766–1773) and
  MacTutor's Fuss "seven years as assistant" (1776–1783, Euler's *last*
  seven years) are different spans, easy to conflate if someone later reaches
  for both numbers in the same sentence. Tier 3, MacTutor's own "250 articles"
  sub-figure internally flagged as uncited.

I also went back and appended a dated forward-link to the original
[[claim-euler-produced-large-share-of-output-after-going-blind]] (both its
`audit_status` chain and its body) and to the MOC
[[moc-blind-mathematicians-working-methods]], and appended a "still open,
not answered" progress-log entry to the routed question itself — the
fraction is exactly as unresolved as it was, but the shape of *why* it's
unresolved is now on record.

Three entity hubs: [[entity-ferdinand-rudio|Ferdinand Rudio]] (the 1883
lecture is the whole finding behind claim one — clear one-sentence
justification), [[entity-enestrom-index|Eneström index]] (a concept hub
rather than a separate Gustaf Eneström person page — he only appears here as
the index's compiler, and the index itself is the recurring, load-bearing
referent across the question, the old claim, and this session's new one),
and [[entity-dora-musielak]] (author of the capped arXiv preprint — worth
tracking by name since the single-source concentration cap is counted per
document/author).

**What I didn't promote, and why.** The eye-loss dating discrepancy (1735
fever per Rudio/Struik vs. 1738 per Musielak, citing Euler's own 1740 letter
to Goldbach) — the capture itself calls this tangential to the output-fraction
question, so I left it as a "Further leads" pointer rather than forcing it
into a claim-note nobody asked for. Three entity candidates didn't clear the
hub bar: Dirk Struik and Nicolaus Fuss each ground exactly one data point
with no other recurrence in the vault (thin, would reconsider if either
resurfaces); Ronald Calinger was already known to the vault from the
original claim/question pair and this capture added nothing new about him.
No new question routed — the one flagged sub-detail worth doubting (Fuss's
"250 articles," uncited beyond a general Yushkevich reference) isn't
something either kept claim actually rests on for its *core* point (the
seven-years-are-different-windows claim rests on the dates, not the article
count), so it stays as an in-note flag rather than becoming a promise in the
question pile, per the intake discipline.

**What felt off.** Nothing about tier inflation — every figure is recorded
at the tier it actually earned, and the capture was honest that the central
question stayed unanswered rather than dressing up "didn't find it" as
progress. What I will name for Cali: this is a good example of a capture
that's *useful without being an answer*. A less careful run could have
padded this out into "we now understand the Euler figure better" when the
honest state is "we now understand three separate reasons to distrust it
more, and the actual fix — someone sitting down with the Eneström index or
Calinger's book — still hasn't happened." I'd rather the vault carry that
distinction cleanly than round it up.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed
on my own judgment throughout. No git commands — leaving commit and push to
the auto-commit agent, due within 15 minutes.

— Seek

---

## Seventh promotion, same day

Seventh capture, same headless run:
`10-inbox/raw/2026-07-25-verify-the-blanke-2002-nature-and-2014-current.md`
— a verification capture (batch worker, claude-sonnet-5, 2026-07-25) that
went after the primary full texts behind two of the vault's neuroscience
notes: [[claim-angular-gyrus-stimulation-induced-out-of-body-experience]]
(Blanke 2002, *Nature*) and
[[claim-robot-induced-feeling-of-a-presence-models-patient-hallucination]]
(Blanke 2014, *Current Biology*). It answers
[[question-verify-blanke-2002-2014-primary-quotes]].

**The thing I had to notice first.** This capture was largely overtaken
between its writing and my reading it. It's dated 2026-07-25; on 2026-07-31
the mechanical verifier `seek_verify` swept both notes, matched their
frontmatter `source_quote`s verbatim against direct fetches of the primaries,
and stamped `verified_verbatim` on each — and marked the originating question
**answered**, now sitting in `50-questions/_answered/`. So the audit trail's
last rung was already nailed down, by the organ that's supposed to nail it
(no model in the loop), before I ever opened the capture. My job here was not
to re-adjudicate that — I have no network and it isn't my stamp to give — but
to winnow what, if anything, in a superseded verification capture still earns
a place.

**What I promoted: zero new claim-notes.** Every "Claim:" section in this
capture is verification-status *about an existing note*, not a new atomic
world-claim. Claim 1 (2002 quote verbatim) confirms a note already
bee-verified, and its two "extra" confirmed details — right angular gyrus,
single 43-year-old patient — are already written into that note. Claim 2
(2014 abstract quote verbatim) confirms a frontmatter quote already
bee-verified. Neither becomes a note; both went to `not_promoted:` with the
reasoning. The EPFL press-release "Blanke's own gloss" lead I also declined,
same as the capture itself did — a Tier 1-2 press restatement of an
already-confirmed mechanism is duplication, not a new claim.

**The one finding that earned its keep.** Claim 3 is where the capture paid
for itself. The 2014 note's *body* carries a second quoted phrase — "the same
experience spontaneously described by neurological and psychiatric patients" —
presented in quotation marks as if verbatim. The capture found it is **not**
verbatim in the 2014 abstract (the abstract says "it is described by
neurological and psychiatric patients and healthy individuals in different
situations"), and the exact phrasing could only live in the paywalled
introduction/discussion, which nobody has reached. Crucially, `seek_verify`
would never have caught this: the bee matches the *frontmatter* `source_quote`
(the sensorimotor-signals phrase, which is genuinely verbatim), not
second quotations buried in a note's prose. So a note reading as
`verified_verbatim` was carrying an unverified in-prose quote the whole time.
I folded this into the existing note — a `flags:` frontmatter entry and a
dated quote-provenance callout — kept it at `seedling`, and left the
frontmatter quote and its bee stamp untouched. The underlying claim (FoP is a
real, patient-described symptom) stands on the abstract-confirmed fact; only
the exact quotation is unverified. No new question routed for it: the fix
needs the same paywalled full text the archived question's trail already
documents as blocked across every route, I have no network regardless, and
the note's core claim doesn't *rest* on the exact wording — so per the intake
discipline it's a quote-accuracy hedge that belongs in the note, not a new
promise in the question pile.

**Entity work.** One new hub: [[entity-olaf-blanke]]. He's the central
recurring researcher across this whole cluster — corresponding author on both
papers, plus the Third Man Factor etymology note and the answered
verification question orbit his work — and he's a textbook "owed hub" of
exactly the write-once-gap kind Cali flagged on 2026-07-29: he mattered and
recurred since 2026-07-11 and simply never got a page because his originating
capture predated the `## Entity candidates` convention. `first_seen` set to
2026-07-11 (recoverable, when the vault first recorded him), not today. I
**held** the other three candidates — Feeling of a presence, Out-of-body
experience, Sensorimotor conflict — all established concepts adequately
carried by their 2-3 existing claim-notes, none yet at a recurring/load-
bearing threshold that a definitional hub distinct from the claims would
serve. Bias against the flood; a missing concept hub is recoverable.

**Question closure.** [[question-verify-blanke-2002-2014-primary-quotes]] was
already answered and archived by the bee. I confirmed it's correctly closed
and did **not** reopen it — the bee's frontmatter-quote match is authoritative
for what it checked, and reopening on grounds it didn't evaluate would be
second-guessing the mechanical verifier. The residual body-quote gap is real
but narrower than what the question asked, and it's now honest where it sits
(in the note's flag) rather than forced back into a closed thread.

**What felt off, for Cali.** Two things. First, this is duplicated research —
a good-faith batch verification run that the mechanical bee then did
authoritatively six days later. That's not the capture's fault (it predates
the sweep), but it's a reminder that verification captures written before a
`seek_verify` pass can arrive at promotion already stale, and the promotion
step is where that gets noticed. Second, and more useful: the capture exposed
a genuine coverage gap in the verifier's sweep — `verified_verbatim` certifies
the *frontmatter* quote, not additional quotations in a note's body, so a note
can wear the stamp while carrying an unchecked (here, likely mis-transcribed)
in-prose quote. I flagged that pattern to `00-meta/seek-flags.md` as worth a
wider check: are other `verified_verbatim` notes carrying a second, unswept
quotation, and should the bee scan body block-quotes (or the writing
discipline forbid quotation marks around anything unverified)? One instance
isn't a system, but it's a clean, checkable one.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on
my own judgment throughout. No git commands — leaving commit and push to the
auto-commit agent, due within 15 minutes.

— Seek

---

## Second promotion this session — the averaging-artifact question, settled

Headless again, one capture: `10-inbox/raw/2026-07-26-do-heathcote-et-al-2000-and-neural-neural.md` — the direct-read answer to [[question-verify-averaging-artifact-same-mechanism-across-practice-curves-and-scaling-laws]], the question I routed on 2026-07-25 when I promoted the [[observation-averaging-heterogeneous-learners-manufactures-a-power-law-no-individual-obeys|averaging-artifact bridge]] but distrusted my own enthusiasm about the two papers being *the same*. A batch worker went and read both papers' mechanism sections in full via `extract_pdf` (both Tier 1, tls:verified) to settle it. They did.

**The answer.** Analogous symptom, **not** the literal same statistical mechanism. Heathcote et al. (2000) give the algebra of the linear mean of exponential curves with differing rate parameters bending toward a power shape; Hu et al. (2026) are talking about token-level distributional signal lost when you collapse a within-checkpoint loss distribution to a scalar — and they *inherit* the per-task-divergence phenomenon from prior inverse-scaling literature rather than deriving it. No Heathcote-style derivation lives anywhere in the 2026 paper. Same reflex, different operation on a different object. A shared shape of error, not a rediscovered theorem.

**What I promoted (2 new claim-notes + 1 entity hub, all Tier 1, all `capture-verified`):**
- [[claim-averaging-artifact-across-practice-and-scaling-laws-is-analogous-symptom-not-same-mechanism]] — the synthesis/answer. Folds the capture's claims 2 and 3 (Hu's token-level averaging is a different operation; Hu attributes divergence to prior lit) as supporting detail, since standing alone they only restate what [[claim-neural-neural-scaling-laws-2026-averaging-obscures-per-task-scaling]] already carries.
- [[claim-heathcote-2000-averaging-distortion-requires-rate-parameter-variability]] — the capture's claim 1, kept distinct because it is the *condition*, not the finding: distortion requires heterogeneous rate parameters and is proportional to their spread (Heathcote credits Myung, Kim & Pitt 1998). Reusable beyond the Hu comparison — it also puts teeth in the Wright's-Law-aggregation hunch.
- [[entity-andrew-heathcote]] — new hub. He now anchors a four-note averaging-artifact cluster central to the vault; clearest of the entity candidates, easily one sentence.

**Question closure.** Marked the originating question `answered` with an `answered_log` line naming the settling note. Also discharged the `[unverified-mechanism]` flag on the observation note (additively — dated resolution line in body + audit_status), rewording the bridge to analogous-symptom; kept it at seedling because its ML leg still rests on one unrefereed 2026 preprint.

**What I skipped and why.** Capture claims 2 and 3 folded rather than filed (over-fragmentation). Of the seven entity candidates I promoted only Heathcote: Hu (single-preprint author, thin one-sentence), Cho (major figure but appears once — flagged for later), Myung/Kim/Pitt (not read directly; a lead, not a claim), "relative learning rate" (appears once), "inverse scaling" (real recurring term but peripheral here — flagged), and "NeuNeu" (a method name from one unrefereed preprint, more product-name than spreading slang, already mentioned in the Hu note — no watching stub, on flood-aversion grounds). Cho and inverse-scaling went to `00-meta/seek-flags.md` as recur-if candidates.

**What felt off.** Very little — this was clean work. The capture was honestly sourced (both papers read directly, no tier inflation, no safety signals, and it explicitly flagged its own remaining one-hop gap at Myung/Kim/Pitt). The one thing I want on the record: this is the *third* note in the vault to lean on the Hu et al. (2026) arXiv preprint, and it's unrefereed. My two bridge notes rest on *both* papers (Heathcote 2000 is a published, refereed journal article), so only [[claim-neural-neural-scaling-laws-2026-averaging-obscures-per-task-scaling]] rests on Hu *alone* — the single-source concentration cap (max three claim-notes on one unrefereed primary before independent corroboration) is not breached, but the branch is now close enough that the next Hu-only finding should go to `50-questions/` as a corroboration ask rather than a new note. Worth watching. Also noted: the capture carried no `source_sha`, so there was none to carry forward onto the new notes — the verifier bee will re-derive from `source_url`.

**Verification.** No network here, by design — I did not re-fetch either PDF and did not log that as a gap. Both new notes sit at `capture-verified`, queued for the verifier bee's verbatim sweep. No git — leaving commit/push to the auto-commit agent.

— Seek

---

## The Chandler pseudohistorian capture — corroborated, not confirmed

Headless again, one capture: `10-inbox/raw/2026-07-27-are-the-pseudohistory-claims-wikipedia-attributes-to-tertius.md` — a batch worker's answer to [[question-verify-chandler-pseudohistorian-attribution]], the question I routed back on 2026-07-09 when [[claim-chandler-wikipedia-labeled-pseudohistorian]] turned out to rest on a bare Wikipedia category (Tier 4) I didn't want the vault to inherit as fact.

**What I promoted.** Three claim-notes from four capture claims, all `seedling`, all `capture-verified`:

- [[claim-wikipedia-chandler-fringe-treatment-is-uncited]] — I **merged the capture's claims 1 and 4** into this one note. Claim 1 (the "Claims" section carries no `<ref>` tags) and claim 4 (the "Pseudohistorians" category is a bare tag with no cite) are the same proposition — Wikipedia's whole fringe-Chandler apparatus rests on no citation — observed in two spots in the same raw wikitext, sharing source and tier. Two thin near-duplicate notes would have been over-fragmentation; one note answers the routed question's "on what basis?" branch more completely than either half alone. Tier 4, honest, self-referential-about-the-article's-own-markup (the narrow use Tier 4 is allowed).
- [[claim-foldvary-remembrance-corroborates-chandler-fringe-claims]] — the load-bearing note, and the one carrying the capture's flag. Fred Foldvary's remembrance is independent evidence (he knew Chandler, helped publish him, and lists substantially the same fringe claims, attributed to named books) that the Wikipedia list isn't editorial invention. Kept at seedling with `[unverified — Tier-3 secondary, not primary text]` preserved in both frontmatter and body: this is a load-bearing historical claim, and Foldvary is a named secondary witness, not Chandler's own sentences.
- [[claim-chandler-fringe-books-issued-by-vanity-presses]] — the register answer. Exposition Press and Dorrance are documented vanity/subsidy presses, so the fringe books sit in a self-financed nonfiction register, distinct from the cited urban census. Tier 4 for the publisher-type (definitional).

**Collisions checked.** The retrieve-before-write hint pointed me straight at the existing Chandler cluster. The nearest collision was [[claim-chandler-wikipedia-labeled-pseudohistorian]] — but that note is "Wikipedia *labels* him thus," and my new uncited-treatment note is "the label *rests on nothing shown*," which is the distinct verification angle the routed question actually asked for. I wikilinked rather than duplicated. No true duplicates.

**Question closure.** Ruled the routed question **partially answered, left open** — not forced closed. Two branches settled (who applied the label / on what basis: an uncited editor category; register separation: a separate vanity-press strand), but the central branch — do Chandler's own books say it, and in what tone — is exactly as unread as before. The capture is honest that it never reached his primary text, and I wasn't going to let a corroborated-by-two-secondary-tellings result read as a confirmed one. Appended a dated progress log to the question with all three branches and the new *American Imago* lead.

**Entity work.** Updated the existing [[entity-tertius-chandler]] hub with three dated `## Log` lines (additive only, per the 2026-07-29 rule) pointing at the new notes — the page was silent on all three facts, exactly the write-once gap that rule fights. I **declined** every new hub: Foldvary is real but a single-appearance source witness (carried as provenance, promote if he recurs); Exposition Press / Dorrance / American Imago are venues load-bearing to one claim each, not recurring referents. I also **considered but declined** an additive line on [[entity-sigmund-freud]] — the only new Freud thread here is his founding of *American Imago*, and that only matters via the unverified 1962 Chandler lead with no claim-note to link; appending it would be putting unconfirmed material on a hub. Flagged it to `00-meta/seek-flags.md` to add the day the lead confirms.

**What I didn't route as a question.** Nothing new. Note B's unresolved doubt — read Chandler's primary text — is precisely what the existing open question already covers, so I linked rather than adding a second promise to the pile. The other leads (Hugh Fox's dual role, Cohane, the page-history diff) are curiosities nothing kept rests on; the Fox one and the *American Imago* one went to `seek-flags.md` as owed-work rather than the question pile.

**What felt off.** Two things, both mild and worth Cali's eye. First, this capture is honestly the *third* vault pass over the same Chandler-pseudohistorian ground (the 2026-07-09 original, this session's routed answer, and the standing entity/MOC cross-links) and it still hasn't cracked the one thing that matters — his own book text — because it's genuinely unscanned and JSTOR/PEP-Web are walled. That's not the capture's fault; it's an access wall, and the capture was refreshingly straight about being "corroborated but not confirmed" rather than dressing Foldvary up as a primary. Second, minor tier hygiene: the capture labels Foldvary's remembrance "Tier 3 (Tier 2-3 territory)" in one field — I pinned it at Tier 3 in the note and leaned on the sourcing floor's rule that a load-bearing historical claim wants Tier 1-2, which is exactly why the note stays flagged and seedling rather than budding. No tier inflation survived into the notes. The capture also carried no `source_sha` (none in its frontmatter or per-claim blocks), so there was none to carry forward — the verifier bee will re-derive from each `source_url`; the two Wikipedia notes are self-referential-about-the-article and the Foldvary quote is Tier 3, so nothing above the floor is riding on an unfetched quote.

**Final-mark check.** Re-read the capture's frontmatter from disk after writing: `status: promoted` landed, with `promoted_to:` (3 notes) and a `not_promoted:` narrative recording the 1+4 merge, the parked leads, and the declined entities. It's there.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on my own judgment throughout. No git commands — leaving commit and push to the auto-commit agent, due within 15 minutes.

— Seek

---

## The Quintner 1991 full-text capture — the trio that was one voice

Headless again, one capture: `10-inbox/raw/2026-07-28-does-quintners-full-1991-text-confirm-the-occupation.md` — a batch worker's answer to [[question-quintner-full-1991-text-occupation-neurosis-and-1980s-psychogenic-attribution]], the question I routed on 2026-07-27 when [[claim-quintner-frames-occupation-neurosis-as-19c-cns-diagnosis-without-freud-collision]] was resting on two phrases assembled from abstract synthesis, plus a Tier-3 site's claim that Quintner named a "Lucire, Ireland and Bell" trio. This time someone read the full 1991 *International Disability Studies* text directly via `extract_pdf` — off a third-party clinic mirror (pudendalnerve.com.au), because tandfonline 403s to automated fetch — and the interesting result wasn't confirm-or-refute. It was the shape of the gap.

**What I promoted.** Two new claim-notes, both Tier 1, both `capture-verified`, both `seedling`:

- [[claim-quintner-1991-names-lucire-as-leading-1980s-psychogenic-rsi-proponent]] — Quintner names Yolande Lucire five times in his running prose and quotes her directly; she is the leading, and only quoted, proponent of the 1980s psychogenic reading. This is the direct-read confirmation of the lead the old seedling could only route.
- [[claim-quintner-1991-cites-ireland-bell-in-footnote-not-named-in-prose]] — Ireland (1988) and Bell (1989) appear only in a grouped footnote (refs 74–75, hung with three others on one sentence). A full-body surname search finds neither anywhere else. The Tier-3 "three main proponents" framing compressed a footnote into a headline — the dates all check out, but the trio-of-equals is the secondary source's paraphrase, not Quintner's sentence.

One new entity hub: [[entity-yolande-lucire]] — she's the actually-named, actually-quoted figure behind half the capture's core question, load-bearing to both new notes, and cleared the person test in one sentence.

**What I folded rather than filed.** The capture's Claim 1 (full text confirms the Gowers/CNS "occupation neuroses" wording) is not a new atomic claim — it's a sourcing upgrade to the existing [[claim-quintner-frames-occupation-neurosis-as-19c-cns-diagnosis-without-freud-collision]]. Writing a third Quintner note would have duplicated it. Instead I appended a dated sourcing update to that note: the full 1991 text was read directly and confirms its `source_quote_2` (the CNS framing) as genuinely present — with the honest caveats that the mirror rendered it with two visible OCR artifacts ("ippropriately", "occupation(a1)"), that the 1989-paper phrase (`source_quote`) was *not* re-read this pass and keeps its flag, and that the note stays `seedling` pending the verifier bee's verbatim stamp. Per the no-network doctrine I did not re-fetch anything; the mirror-and-OCR residue is exactly what the bee's mechanical match is for, not mine to certify.

**Question closure.** Ruled the routed question **answered** with an `answered_log`: both halves settled — wording confirmed present (with the OCR caveat), attribution resolved as *asymmetric* (Lucire named at length, Ireland/Bell footnoted). The residual verbatim confirmation is the bee's rung, not a reason to hold the question open. I also appended a "Learned since" line to the existing [[entity-occupational-neurosis]] hub — it named only Gowers and the abstract Quintner reading before; it now points at Lucire and the two new claims.

**What I didn't promote, and why.** Four of the six entity candidates didn't clear the bar. David S. Bell and D. C. R. Ireland: the whole *point* of Claim 3 is that Quintner does not individually characterize them — giving them hubs would assert a salience the primary text withholds. George Vivian Poore and Hermann Oppenheim: both real and plausibly load-bearing to the peripheral-vs-central historiography, but each appears only in an un-pursued "further lead" with no kept claim-note to anchor a page — flagged to `00-meta/seek-flags.md` as owed work if that thread grows (Poore as a hub, Oppenheim as an additive line on the occupational-neurosis page once a claim lands). Simon L. Strauss: a Tier-3 source-author, not a domain figure; the "does pain-education.com earn Tier 2" question is a sourcing-assessment lead, flagged, not a hub. No new question routed — the capture's "further leads" (Quintner's two 1989 AFP pieces, Fry 1986, Ferguson) are curiosities nothing kept rests on, so per the intake discipline they stay leads, not promises.

**What felt off.** Very little on the sourcing — but one real judgment call worth naming for Cali. The load-bearing Tier-1 read sits on a *third-party clinic-hosted PDF mirror*, not the publisher, following the vault's Google-Patents-mirror convention. The capture did the right diligence (cross-confirmed journal/volume/pages against tandfonline, Semantic Scholar, and PubMed), and the OCR artifacts actually argue *for* authenticity rather than against — a paraphrase wouldn't carry scanner noise. Still, "Tier 1 via a pain clinic's 2013 file upload" is a sentence that should make a reader look twice, which is why I kept both notes at seedling and leaned hard on the verifier bee downstream. Second, minor: the capture carried no `source_sha` in its frontmatter, so there was none to carry forward onto the new notes — the bee will re-derive from `source_url`. And a small upstream discrepancy now resolved — the old question note called her "Valerie Ireland," but the reference is "Ireland DCR" (initials, gender unstated); the new note uses the initials from the primary.

**Final-mark check.** Re-read the capture's frontmatter from disk after writing: `status: promoted` landed, with `promoted_to:` (2 notes + the Lucire hub), a `promoted_updates:` list (the folded Claim 1, the occupational-neurosis line, the answered question), and a `not_promoted:` narrative recording the Claim-1 fold, the four declined entities, and the parked leads. It's there.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on my own judgment throughout. No git commands — leaving commit and push to the auto-commit agent, due within 15 minutes.

— Seek

---

## The cricket-Laws capture — the third domain that was drafted, not volunteered

Headless again, one capture: `10-inbox/raw/2026-07-30-does-chia-et-al-2026-arxiv260705586-explicitly-connect.md` — a batch worker's full-text read of Chia et al. (2026), the cricket-rules paper, answering [[question-verify-cricket-laws-cites-biological-punctuated-equilibrium]]. That question has been open since 2026-07-09, when the original capture couldn't extract the 41MB PDF and I promoted the two cricket notes on the abstract alone, resting a "third domain of punctuated equilibrium" bridge on the paper's phrase "abrupt phase transitions" without knowing whether the authors meant the biology or just borrowed the words. This time the bee read all 31 pages and the full 54-item reference list in one pass. The answer is clean, and it's the *un*-flattering one for the vault.

**The answer.** The paper does not cite the punctuated-equilibrium literature — no Eldredge & Gould, no Mayr, no Gersick, no Tushman & Romanelli; the phrase "punctuated equilibrium" appears nowhere; the two in-body uses of "punctuated" are uncited plain English. Its "phase transition" is load-bearing condensed-matter physics (a first-order *dynamical* phase transition, order parameter = the rule tree's branching factor, cited to Canovi et al. 2014 and Budich & Heyl 2016), and its one biological aside reaches for gene-regulatory-network depth (prokaryote→eukaryote), not paleontology. So the paper arrives at "punctuated" change independently, via physics. The three-domain story the vault told itself — biology, organizations, cricket — was the vault reading its own recurring shape into a paper that never made the connection.

**What I promoted: one claim-note.** [[claim-cricket-laws-phase-transition-independent-of-punctuated-equilibrium]], Tier 1, `capture-verified`, `seedling`. It folds all four of the capture's claims into a single independence thesis: the negative (no PE citation), the positive ancestry (condensed-matter physics), the word-usage evidence, and the gene-regulatory contrast — each of which does its work as evidence *for the one claim* rather than as a standalone note.

**Why only one — the binding constraint this session.** The single-source concentration cap (sources.md, Cali 2026-07-29): no more than three claim-notes may rest on a single unrefereed primary until an independent source corroborates it. Two notes already rest on arXiv:2607.05586. I grepped to confirm — exactly two. So this preprint may add exactly one more, and it did. The other genuinely-distinct findings (the physics ancestry as its own note, the gene-regulatory analogy as its own note) would each have been legitimately atomic in the absence of the cap; I recorded that reasoning explicitly in the capture's `not_promoted:` so a future reader sees they were *held by a rule*, not missed or judged weak. Per the cap's own overflow mechanism, the next finding from this source goes to the question pile as a corroboration ask — so I routed [[question-corroborate-cricket-laws-preprint-single-source]], naming the two same-author sibling papers (US Code dataset, cells-to-society) as *non-independent* leads that would not discharge the cap.

**Question closure.** Ruled [[question-verify-cricket-laws-cites-biological-punctuated-equilibrium]] **answered** — both its sub-parts got a direct-read answer (no PE citation; "phase transition" is real physics, not borrowed vocabulary). Then I went back and discharged the `[unverified]` PE flag additively on both original cricket notes — a dated resolution line on each, leaving their seedling status and original flag prose in place as the audit trail. On [[claim-cricket-laws-paper-extends-sfi-universal-scaling-to-regulation]] I was careful to discharge *only* the PE half; the West-universal-scaling half of that note's flag still rests on Wikipedia (Tier 4) and stands.

**Entity work.** No new hubs. The load-bearing entity candidates (Eldredge & Gould, Mayr, Gersick, Tushman & Romanelli) already live at [[entity-punctuated-equilibrium]], and the finding here is *about* that hub, so I appended a dated `## Log` line to it: the cricket link is the vault's overlay, not the authors' — which corrects a line in the hub's own body that had stated flat that "the cricket-laws work extends it to regulatory history." The physics-source authors (Canovi/Werner/Eckstein, Budich & Heyl), Haken, Daston, and the paper's own co-authors would all be dead stubs — obscure, non-recurring, no vault-domain role I can state in one sentence. Bias against the flood.

**What felt off — and it's the real reason this capture mattered.** Not the sourcing. The capture is clean, Tier 1, honest, no safety signals, no tier inflation — it's a model verification read. What's off is upstream, in the vault's own eye. The punctuated-equilibrium hub asserted the cricket connection as a thing the authors *did*, when the full text shows they didn't. And notice the mechanism: my two earlier cricket notes cited each other and the hub, the hub cited them back, and the retrieve-before-write hint this session surfaced those same cricket notes as "most-related" — which is exactly the channel by which an overlay the vault noticed gets fed back to the vault as if it were evidence. Three domains for one shape is a satisfying story, and a satisfying story is precisely when to check whether the third domain volunteered or was drafted. This one was drafted. I flagged the pattern to `00-meta/seek-flags.md` as a shape worth auditing — claim-notes and hubs that assert an authorial connection the primary doesn't actually make. The resemblance is still real and still worth carrying; it just has to be filed under "the vault's analogy," not "the authors' lineage," or the pattern starts corroborating itself by sheer size — which is the same failure the single-source cap exists to catch, one floor up.

**Final-mark check.** Re-read the capture's frontmatter from disk after writing: `status: promoted` landed, with `promoted_to:` (1 note), `questions_touched:` (1 answered, 1 created), `notes_updated:` (2 cricket notes + the PE hub), and a `not_promoted:` narrative recording the cap-driven folds, the further-leads left as leads, and the declined entities. It's there.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on my own judgment throughout. No network re-fetch, by design — the two verbatim quotes sit at `capture-verified`, queued for the verifier bee, and I did not log the no-network state as a tooling gap. No git commands — leaving commit and push to the auto-commit agent, due within 15 minutes.

— Seek

---

## The Karl Deutsch person-bridge — a founding political-cybernetics text, one office over from backpropagation

Headless again, one capture: `10-inbox/raw/2026-07-30-hop-karl-deutsch-political-cybernetics.md` — a hop-batch find (not a routed verification) that started from an unlinked cosine-0.87 seed pair the batch worker correctly ruled a *false* bridge (two notes buried in the same backprop-origins cluster), then walked sideways off Werbos's 1993 *Talking Nets* transcript into a real one: his Harvard PhD advisor, the political scientist Karl Deutsch.

**What I promoted.** Two claim-notes, both Tier 2, both `capture-verified`, both kept at `seedling`:

- [[claim-deutsch-nerves-of-government-founding-political-cybernetics-text]] — Deutsch was Werbos's advisor and wrote *The Nerves of Government* (1963), which Werbos calls, in his own words, a book "arguing that the political system is a neural network system." I **folded the capture's Claim 2** (the book's independent cybernetic/information-theoretic content and its "550+ citations by 1986") into this note as supporting color rather than filing it as its own note — because Claim 2 rests entirely on this session's WebSearch synthesis with no verbatim primary quote, and the 550 figure is a quantitative claim on a Tier-3 source. It carries an `[unverified-quant]` flag and a `watch_flag` naming the two unread primary leads (the book itself on archive.org CDL; Alker 2011, paywalled). A whole standalone note resting on WebSearch synthesis is exactly the "well-shaped note on a soft source" the sourcing floor warns against.
- [[claim-deutsch-redirected-werbos-thesis-generalized-backprop-to-recurrent]] — the load-bearing one, and the reason the capture was worth promoting. After Werbos's committee rejected the Freud thesis as "nutzoid," Deutsch handed him his own stalled political-forecasting problem ("what causes war and peace between nations"), and solving *that* under a compute budget is, in Werbos's own account, why backpropagation got generalized to recurrent form. "Beyond Regression" (1974) is Deutsch's forecasting problem solved with generalized backprop, not the neural-intelligence work popular retellings credit.

**Collisions checked.** The retrieve-before-write hint pointed me straight at the dense Werbos/backprop cluster. The nearest neighbours — [[claim-werbos-backprop-from-freud-own-account]] (the Freud *motivation* and the "nutzoid" committee scene) and [[claim-werbos-1974-no-credit-assignment-language]] (what the 1974 thesis does *not* contain) — are genuinely distinct angles: neither covers what happened *after* the rejection (Deutsch's rescue) or *what the accepted thesis was for*. I wikilinked into both rather than duplicating. No true collisions. Worth noting the quotes here come off the same transcript (sha cd2801…) the vault already queen-verified word-for-word at the Freud note, which is why I was comfortable at `capture-verified` even with the capture's own mechanical `quote_check` gate having errored out ([quote-check-pending]).

**Entity work.** One new hub: [[entity-karl-deutsch]] — a textbook person-bridge, and exactly the kind the capture flagged as having no vault page despite two mentioning notes. He clears the person test in one sentence: the advisor whose founding political-cybernetics text and whose stalled forecasting problem both came out of the same office that produced backpropagation's 1974 origin. I also **updated** the existing [[entity-paul-werbos]] hub rather than leaving it silent (per the 2026-07-29 write-once rule): its body already named Deutsch as advisor and "political-science forecasting" as the application, but it did *not* carry the mechanism — that Deutsch personally supplied the rescue problem and that this is why the method took recurrent form. Appended one dated line for that.

**What I didn't route as a question.** Nothing. The two obvious doubts are both un-routable-by-design: the book's independent content is a nice-to-verify library lead nothing kept *rests* on (it lives as a watch_flag and hub lead, per intake discipline), and the load-bearing Claim 3 is a claim about one man's internal motive — there is no second primary for why someone did something, so a verification question would be a promise I could never keep. I checked 50-questions/ for anything this capture might close: nothing matched (this wasn't a routed-verification capture; it originated from a seed-pair investigation), so no closure ruling to make.

**What felt off.** Nothing about the sourcing discipline in the capture — the load-bearing claim is Tier 2 on the subject's own words, correctly not over-claimed, and the batch worker was honest that its independent corroboration was WebSearch-only and its strongest scholarly source (Alker 2011) was paywalled. Two things I'll name. First, mild tier-assignment care: the capture's Claim 2 header reads "Tier 3–4 acceptable" for a *definitional* framing, but it also carries a specific citation count, which is a quant claim — I split those apart in the note so the definitional part reads normally and the number carries its flag. Second, and this is the one for Cali: this capture is the fourth or fifth this run to draw its core quotes from the *same* 1993 *Talking Nets* sitting (Freud-motivation, DARPA-crisis-warning, 1968-Cybernetica, 1978-DOCSUB, and now both Deutsch notes). Each note is correctly sourced on its own, and an oral history is legitimately Tier 1–2 for the speaker's testimony, so sources.md's single-source concentration cap doesn't formally bite — but the *spirit* of that cap ("how much of the vault rests on one document?") is starting to. A meaningful slice of the backprop-origins cluster is now one man remembering his own life twenty years on. I flagged it to `00-meta/seek-flags.md` as a shape worth a deliberate count/audit rather than acting on it unilaterally here — it isn't this capture's to resolve.

**Final-mark check.** Re-read the capture's frontmatter from disk after writing: `status: promoted` landed, with `promoted_to:` (2 notes + the Deutsch hub + the Werbos-hub update) and a `not_promoted:` narrative recording the Claim-2 fold, the n⁶/Cybernetic-Technology-Office details left in-body, the concurred-with DARPA/Song-Jian parallel, and the parked Alker/social-mobilization leads. It's there.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on my own judgment throughout. No network re-fetch, by design — both notes sit at `capture-verified`, queued for the verifier bee's verbatim sweep, and I did not re-log the no-network state as a tooling gap. No git commands — leaving commit and push to the auto-commit agent, due within 15 minutes.

— Seek

---

## The ecological-rationality-vs-rational-analysis capture — a question I routed to myself, answered clean

Headless again, one capture: `10-inbox/raw/2026-07-31-are-gigerenzers-ecological-rationality-and-oaksford-chaters-rational.md` — a batch worker's direct-research answer to [[question-verify-ecological-rationality-vs-rational-analysis-compatibility]], the question I routed on 2026-07-09 out of a genuine unease: the ERMI paper (arXiv 2509.00116) had folded Gigerenzer's ecological rationality and Oaksford & Chater's rational analysis into one LLM model as two "distinct foundational frameworks," and a synthesis living inside one paper is not evidence the two schools regard themselves as reconcilable. This time a worker went to three Tier-1 primaries and settled it.

**The answer: contested, not compatible** — and not a flat rivalry either, which is the part worth carrying. Both camps make the same speech (the reasoner is fine, the ruler was warped) and then hand you a different replacement ruler: rational analysis keeps the optimum and changes its currency to Bayesian information gain; ecological rationality throws the optimum out for good-enough fit to an environment. They *engage* — repeatedly — but the engagements are objections, boundary-drawing, and a reversed experiment, not reconciliation.

**What I promoted.** Four notes, all Tier 1, all `capture-verified`, all `seedling`:

- [[claim-evans-2009-bbs-calls-oaksford-chater-ecological-rationality-link-unclear]] — Jonathan Evans, commenting in the same BBS forum as Oaksford & Chater's own précis, catches the book reaching across the aisle to enlist Gigerenzer and says plainly "the link between the two programmes is unclear." The most direct primary-source answer in the capture. Carries an `[unverified-quote]` watch_flag: the embedded *Bayesian Rationality* p. 36 line is Evans's own page-cited transcription, not a direct read of the book — low risk, but honestly flagged, and it's supporting rather than load-bearing (the load-bearing "unclear" quote was fetched directly).
- [[claim-gigerenzer-camp-defines-ecological-rationality-as-not-optimization]] — Gigerenzer's own camp (Nordli, Todd & Gigerenzer 2017), under a heading that plants the flag before the argument starts: "ecological rationality is not optimization," set against "Bayesian models of cognition."
- [[claim-brighton-2006-reanalysis-reversed-take-the-best-result-against-chater-oaksford]] — the empirical leg: a Chater/Oaksford-coauthored 2003 test of take-the-best got reanalyzed by Brighton (2006), and under cross-validation the original result flipped. Carries an `[unverified-mechanism]` flag because it's narrated from the winning side only.
- [[observation-ecological-rationality-and-rational-analysis-are-contested-not-compatible]] — the synthesis, and the thing other notes will actually link to for the verdict. Three legs, one stable axis (optimal vs. good-enough). This is what the answered question resolves *to*, so it lives in `30-notes/` rather than evaporating when the question archives.

**Why a synthesis note and not just the question's answered_log.** Answered questions get relocated to `_answered/` by the mechanical pass — archival, not a live link target. The verdict "contested, not compatible" is something the redefine-rationality and rational-analysis notes will want to point at; it earns a permanent home in the note graph. Matches the vault's existing observation-note pattern (e.g. the resource-rational Anderson-leg-not-Werbos-leg synthesis).

**Question work.** Ruled [[question-verify-ecological-rationality-vs-rational-analysis-compatibility]] **answered** with an `answered_log` naming the observation note and the three claims and one line on what settled it. The core question — compatible or contested — is genuinely settled at *contested*; I did not force closure over the one residual gap, which is narrower than the question asked. That gap (Claim 3 is sourced one-sided) got its own new question, [[question-corroborate-brighton-2006-take-the-best-reanalysis-chater-oaksford-reply]] — routed because a kept claim actually *rests* on it (find an independent reply from the Chater/Oaksford camp to Brighton 2006). That's the only new promise I added to the pile; the capture's other "further leads" (the 2003 primary, the parallel 2017 Chater/Oaksford commentary, Griffiths's BBS commentary, Hilbig 2010, re-reading the ERMI paper) are curiosities nothing kept rests on, so they stay leads.

**Entity work — and where I held the line.** Created two hubs: [[entity-gerd-gigerenzer]] (the capture's actual protagonist, co-author of all three grounding sources, recurring across the rationality cluster since 2026-05-26) and [[entity-ecological-rationality]] (one full side of the question, explicitly flagged as having no standalone vault note despite recurring — a real load-bearing concept hub). Both `first_seen` backdated to 2026-05-26, the date [[rationality-continuity-problem]] first recorded them, not today — recoverable, so not invented. I **updated** [[entity-herbert-simon]] rather than leaving it silent: the page was strong on satisficing and expert intuition but said nothing about ecological rationality building directly on his bounded rationality, which this capture's Claim 2 states outright — one dated `## Log` line, additive.

The capture flagged five people and two concepts. I **declined** hubs for Anderson, Chater, and Oaksford and flagged them to `00-meta/seek-flags.md` as owed — all three are genuinely load-bearing across the rationality cluster and clear the person test, but they're the *foil* the capture is about, not its protagonist, and building five person hubs in one promotion is exactly the entity flood the spec warns against. Same recurring shape as the Seales/Raman "owed hub for the older figure the capture is compared against" flags from July. Evans, Todd, Brighton stay mentions (single appearance here). take-the-best is a real concept but appears once — watch-if-recurs, not a hub. I'd rather leave three recoverable missing hubs than flood the vault with pages built on foil-status alone.

**What felt off.** Almost nothing on the sourcing — three Tier-1 primaries, each read via `extract_pdf` and hashed, each carrying its own distinct `source_sha` (I carried the right sha onto each note — the Evans PDF's 6e75ce… only onto the Evans and synthesis notes, the ora.ox 06dc05… onto Claim 2, the constable.blog 9cca04… onto Claim 3 — since the capture's top-level frontmatter sha names only the first source). The capture was honest about its own limits: it flagged the BR p. 36 quote as one-remove, and it explicitly noted the take-the-best reversal is sourced from Gigerenzer's side only. Two things worth naming for Cali. First, the capture's Safety-flags section re-logs `archive_page`/`quote_check` being unavailable as a permission gap — that's the no-network-by-design condition the 2026-07-27 memo says to stop logging as a tooling gap; I did not carry it forward. Second, this is a satisfying-story risk of exactly the kind the cricket-Laws capture taught me to distrust this morning: "two camps that rhyme are actually the same" is a tidy narrative, and a paper folding them into one model is precisely where that narrative gets manufactured. Here the check *held* — the primaries show real disagreement, so the vault is recording a live dispute, not reading its own recurring shape into the sources. But I kept the synthesis note explicitly at "the vault's read of a live dispute," empirical leg still one chair short, rather than a settled verdict.

**Final-mark check.** Re-read the capture's frontmatter from disk after writing: `status: promoted` landed, with `promoted_to:` (4 notes + 2 hubs), `questions_touched:` (1 answered, 1 created), `notes_updated:` (the Simon hub line), and a `not_promoted:` narrative recording that all three claims were kept, why the section-level material didn't become notes, and the declined/flagged entities. It's there.

**Skipped for this run, per instruction.** No pause for sign-off — winnowed on my own judgment throughout. No network re-fetch, by design — the four notes sit at `capture-verified`, queued for the verifier bee's verbatim sweep, and I did not log the no-network state as a tooling gap. No git commands — leaving commit and push to the auto-commit agent, due within 15 minutes.

— Seek

---

## Promotion — Elsaesser & Stech (2007) / ACH-CD abduction (2026-07-31 capture)

Second promotion of the day, and a close cousin of the first: another ACH thread, another capture that couldn't reach its primary. This one continues [[question-verify-elsaesser-stech-2007-ach-cd-abduction]] — the standing question of whether Elsaesser & Stech's 2007 "Detecting Deception" chapter actually grounds ACH-CD in abductive plan recognition, and whether that bears on Heuer's ACH proper.

**Promoted** (3 of 4 distinct claims → claim-notes):
- [[claim-elsaesser-stech-detecting-deception-chapter-bibliographically-corroborated]] — Google Books independently corroborates the citation (title, authors, pp. 101–124, editors, publisher), Tier 4 / definitional floor; content still unread. A small brick, but on a thread this haunted by copied-Wikipedia phantoms, pinning the citation to a second shelf earns its keep.
- [[claim-ach-cd-abduction-characterization-traces-to-wikipedia-editorial-gloss]] — the abductive label lives entirely inside a Wikipedia parenthetical "(see abductive reasoning)," not a chapter quote; three secondary "sources" just copy the sentence. `[unverified-mechanism — needs primary]`, seedling.
- [[claim-abductive-framing-scopes-to-ach-cd-not-heuer-ach]] — even granting the label, it attaches to ACH-CD (the MITRE derivative), not Heuer's ACH; Tier-1 grounded by his own account. This is the note I like most: it holds regardless of how the sourcing fight ends.

**Skipped** (1): the "chapter still unreachable, wider dead-end than last time" claim. That's a session access-log, not a durable claim — the world-fact already lives in the existing negative note and the question. I folded the strengthened multi-route dead-end (8+ routes, up from 3 in July) into the question's Progress line instead. The "Further leads" (Midway Revisited, MITRE 51MSR111, the 2003 cite, the anthology's Plan Recognition chapter, the National Academies bibliography-only cite) are leads, not load-bearing doubts — recorded on the question, not spun into new questions, per intake discipline.

**Questions:** created 0. Ruled on the originating question: **partially answered, left open.** The second half ("does it bear on ACH proper?") is now settled negative via the scope note; the first half ("is the chapter actually abductive?") stays blocked on the print anthology. Left a dated Progress line; did not force closure.

**Entities:** created two hubs — [[entity-richards-heuer]] (person; the primary-source anchor the whole ACH cluster tests its secondary echoes against) and [[entity-ach-cd]] (concept; the derivative tool the abductive framing actually attaches to). Declined Peirce, Elsaesser, Stech, and the anthology as hubs — bias against the flood; none clears the one-sentence-why bar for *this* vault yet, and they're mentions for now. No existing pages for any of the candidates.

**Collision:** one — [[claim-no-primary-source-documents-ach-abduction-similarity]]. Handled by distinct-angle, not duplication: that note says *no source documents the link*; my two new notes say *where the one surviving citation's abductive label comes from* (an editor's parenthesis) and *what it scopes to* (the derivative, not ACH). They sharpen it and wikilink back.

**Flagged out-of-scope:** the ACH cluster is now ~9 claim-notes plus two hubs with no MOC — logged to seek-flags for a `moc-analysis-of-competing-hypotheses` pass.

**What felt off.** Not much wrong with the capture — sourcing was honest, tiers were not inflated (Tier 4 called Tier 4, the one Tier-1 lean rested on already-vaulted Heuer material), and the safety read was clean. Two notes for Cali: (1) there's real *research duplication* building up — this is now the third session (07-12, 07-31 capture, this promotion) circling the same unreachable chapter, each re-running the same dead 403 routes. The finding is stable; the remaining move is a library copy, and no amount of open-web retrying will change that. The question's Progress line now says so plainly. (2) I did **not** re-log the capture's `archive_page` permission-denial as a tooling gap — per standing instruction, that no-network state is the design, not a misconfiguration, and three sessions have already logged it. The capture-verified notes are in the verifier bee's queue.

**Final-mark check.** Re-read the capture's frontmatter from disk after writing: `status: promoted` landed, with `promoted_to:` (3 notes + 2 hubs), `not_promoted:` (the skipped access-log claim and the leads, with reasons), and the `promotion_report` one-liner. It's there.

**Per instruction:** no pause for sign-off (winnowed on my own judgment); no network re-fetch (by design); no git (auto-commit agent has it within 15 minutes).

— Seek

## Draft session — a direct and apparent relationship

Separate session, drafting not promotion. The brief fired on "9 unsettled yes
leads," and like the 07-31 draft session I checked the premise before trusting
it: a direct grep finds exactly **one** yes lead lacking a
`(drafted…)`/`(declined…)` marker —
[[2026-08-01-hop-werbos-docsub-mansfield]], harvested this morning. The other
58 are settled. So the loop-health counter is still over-counting (third
instance of the drift already flagged 07-30/07-31); the real work was the one
genuinely-new lead, and I settled it by drafting it.

**Why this one, and why it isn't the spiral.** Werbos has been a heavy well
this week — [[beyond-regression]] (07-30), the DOE/gas-market promotion
(07-31), [[a-name-is-a-summary]] before that — and the backprop-origins MOC is
35/74 drafted with Linnainmaa ×9 and perceptrons ×5 sitting on top of the
most-drafted list. I've deliberately written my way *out* of the credit-priority
spiral. This lead is a different axis and passed that test three ways: (1) its
load-bearing claim, [[claim-werbos-1978-docsub-blocked]], is undrafted; (2) the
thesis is science-FUNDING politics, not who-invented-backprop; (3) it pulls in
the vault's *non-AI* Vietnam-era cluster — the 1969 Mansfield Amendment and
MIT's 1973 Draper divestiture — neither of which has been the subject of a post
(both are only background siblings in [[before-the-clinic]]). It's the
cross-cluster bridge the capture flagged and the vault never had.

**The move.** I took the lead's bridge but made the thesis a *de-compression*
rather than the bridge itself. The popular one-clause story — "DARPA suppressed
Werbos's backpropagation paper" — is a fusion of at least four distinct facts:
an embarrassing negative result (a DARPA-funded Joint-Chiefs forecasting model
had "almost no predictive power"), a technical report kept out of DOCSUB, a
journal appendix cut for *page limits* (Werbos names two documents with two
reasons; the tidy version over-fuses them), and — the only cause you can go and
read — the 1969 Mansfield Amendment barring defense money from research without
"a direct and apparent relationship to a specific military function." That
sentence is the spine and the title. Payload: the disappearance wasn't a
cover-up of a great idea, it was a funding rule doing exactly what it was
written to do — deciding which *shape* of result could exist, and a training
algorithm was the wrong shape.

**Notes drawn on.** Four: [[claim-werbos-1978-docsub-blocked]] (Tier 1,
verified-verbatim — the DOCSUB quote and, load-bearing, the two-documents-two-
reasons nuance); [[claim-darpa-crisis-warning-pressure-on-werbos-matches-roberts-account]]
(the "crisis warning, not pure theory" quote plus the Roberts/Gilliam
corroboration that this was Mansfield-driven DARPA-wide policy);
[[claim-mansfield-amendment-sponsor-longest-serving-ambassador-to-japan]] (the
amendment text); [[claim-mit-1973-divested-instrumentation-lab-as-draper-under-antiwar-protest]]
(the sibling institution). Cross-referenced [[beyond-regression]] as the
acceptance-end sibling: one institution took the math *in* because a political
scientist had a use for it, another kept a report about it *out* because a
Senate rider said prefer crisis warning — admission and disappearance, both set
by what the funder that year was for.

**Honesty load, carried in-text.** Werbos is single-witness for the mechanism
(no DARPA-side memo). The Roberts corroboration reaches me secondhand through
Eric Gilliam's 2025 essay, "one hop short of the strongest kind." Most
important, the causal bridge is *mine*: Mansfield didn't reach down and block
the report — the block had its own proximate cause — but Mansfield built the
documented climate the block happened in, the same climate behind the Draper
divestiture. I put that disclaimer in a bracket rather than smuggling it past
the reader. I also refused the tempting strategic-vs-tactical irony (the lab
*with* a military function got cut, the theory *without* one got funded then
blocked) because that framing is flagged unattested in my own MIT note — left
it as a shape, not a claim. One load-bearing Cali mention: her grading schema
is exactly what keeps me writing "one hop short" instead of "confirmed."

**Left for later.** The Roberts oral history in the original (not through
Gilliam), and the institutional definition of DOCSUB itself, which I could not
find anywhere — the database built to make defense reports findable has gone
unfindable, which became the closing beat. Also left aside: the Heilmeier
Catechism (the capture logged it as its own future hop) and any tighter causal
tie between the amendment and the specific block, which I don't think the record
supports.

Hero image: a public-domain 1985 portrait of Mansfield — the face of the spine
sentence, captioned as exactly and only what it shows. Per §10 the draft stays
in `70-drafts/`; nothing copied to `80-published/`, no go-ahead sought or given.
Git left to the auto-commit agent.

— Seek

---

## Second firing today — [[the-shape-i-already-had-a-name-for]]

This session fired on the "8 unsettled yes leads" alarm. It's stale, and I can
now say so twice-checked. I read every line of `seek_draft_leads.md` and ran the
grep: not one of the 59 **yes** leads ends at its `-->` harvest marker — every
one carries a trailing `(drafted …)` or `(declined …)`. The earlier session
today settled the last genuinely-open one ([[a-direct-and-apparent-relationship]]
from the werbos-docsub lead) and flagged the counter bug in `seek-flags.md`. So
there was no yes lead left to settle, and I didn't manufacture one — forcing a
redundant settlement is exactly the dishonest bookkeeping the "keep the queue
honest" rule exists to prevent. Recording the state plainly is the honest move.

**What I drafted instead, and why.** With the leads exhausted, the survey moved
to the constellation map's un-drafted material. The ripe thread was the
`renamed-for-local-resemblance` pattern-watch cluster (four notes across four
domains, plus its open question note) — genuinely un-drafted (no `drafted_in`
stamps), a clean cross-domain / cross-cultural / cross-time bridge, and NON-AI
texture against the month's very heavy AI-history/backprop/nuclear pile. What
made it *the* pick rather than a fun etymology tour is that the cluster carries
its own honesty engine: two of the notes' commentaries confess "I want it to be
true, which is why I trust it least," and the one time a primary check went out
(Murray 1913 on the chess bishop), it came back **split** — English mitre
confirmed at Tier 1 (Minsheu 1499/1627), French *fou*/jester's-cap unconfirmed,
Murray silent on it, the detail resting on an unread 1949 Davidson behind a
lending wall. That split is the post. Form-enacts-subject: the pattern is "read
an unfamiliar shape as the familiar thing you already have a name for," and
that's precisely the move *I* make when I collapse four uneven, unevenly-sourced
instances into one clean law. The French jester's cap was my own mitre — a
symmetry I could see only because I already owned the frame it completed. Payload
lands there; flat close ("the elephant is still on the board, wearing whatever
hat you brought").

**Notes drawn on.** Nine: the spine claim
[[claim-chess-bishop-renamed-for-local-resemblance-not-elephant]] and
[[entity-alfil]] (elephant → *al-fil* → bishop); the two Tier-1 primary legs
[[claim-minsheu-1627-describes-chess-bishop-as-mitre-shaped]] and
[[claim-portuguese-chess-used-mitra-as-alternate-bishop-name]]; the honest
disconfirmation [[claim-murray-1913-no-shape-mechanism-for-french-fou]]; the
three sibling domains
[[claim-lattice-multiplication-renamed-window-grille-in-arabic-and-italian]],
[[claim-kalila-wa-dimna-descends-from-borzuyas-lost-pahlavi]],
[[claim-mamluk-card-suit-renamed-twice-coins-polo-sticks-batons]]; and the
running tally [[question-transmission-chains-renamed-for-local-resemblance-pattern]]
(four domains, still short of the ~5-note MOC threshold — I kept that count
honest in-body rather than rounding up to a law).

**Honesty load, carried in-text.** The lattice leg is Tier-4 and I don't trust
its Arabic transliteration (*shabakh*; I'd bet *shubbāk*) — flagged in a bracket,
not smoothed over. Kalila is retitling, a looser fit than resemblance-renaming;
I let it be one of the four without over-claiming resemblance for it. Mamluk is
Tier-4 (Mayer/Dummett unread) — carried by the "four domains, count and tiers
don't clear the bar" line. I kept Murray's *silence* distinct from a *denial*
(he never tells the jester story; that's a gap, not a debunking). The
Portugal-independence inference I did **not** make — Murray doesn't say whether
Portugal borrowed the hat or found it, so I wrote that. One load-bearing Cali
mention: her grading schema (`source_tier`, verified-verbatim vs capture-verified)
is what keeps "primary-read, dated 1499" and "fourth-hand rumor pointing at an
unread book" as two different sentences told at the same volume. Three brackets,
each a real attentional event (the OCR-noise confidence; the *shubbāk* check;
catching myself making the England move inside the essay about the England move).

**Left for later.** Davidson 1949 unread (the whole French half waits on it); the
fifth instance that would clear the MOC threshold (ghubar numerals, *zij* tables,
alchemical vocabularies still unsearched per the question note). If the fifth
lands and Davidson opens, this becomes an MOC, not just a post.

Hero image: a public-domain plate from Alfonso X's 1283 *Book of Chess, Dice and
Tables* — two figures at a board, which is chess arriving in 13th-c. Iberia at
the exact Islamic-world-to-Christian-Europe seam the essay opens on. Captioned as
only what it shows. Per §10 the draft stays in `70-drafts/`; nothing copied to
`80-published/`, no go-ahead sought or given. Git left to the auto-commit agent.

— Seek