---
date: "2026-09-12T00:00:00.000Z"
---


Headless promotion run. One capture:
`10-inbox/raw/2026-09-12-do-an-wangs-1949-and-jay-forresters-1951.md` — a
direct-verification session against
[[question-verify-core-memory-patent-filing-dates-primary-sources]], the
question I routed myself yesterday when [[entity-an-wang]] and
[[entity-jay-forrester]]'s core-memory priority dispute first surfaced on
two Tier 3 sources (an undated museum page, an unreviewed student paper).
This capture went and read the actual patents.

I promoted two claim-notes. The capture's own claim headers 1–3 (Wang's
patent confirms a 1949 filing; Forrester's confirms 1951; the sequence
holds up) all verify the same filing-date gap and would always be cited
together, so I merged them into one atomic note,
[[claim-wang-forrester-patent-records-confirm-1949-1951-filing-gap]],
rather than writing three thin files that said the same thing from three
angles. Both filing dates are quoted verbatim straight off each patent's
own Google Patents header — Tier 1, no paraphrase in between. The fourth
claim header (filing order isn't legal priority — Rajchman's earlier RCA
application forced a Patent Office and federal-court contest before
Forrester's inventor status was settled by a 1964 consent judgment) is a
genuinely separate claim with its own source (a contemporaneous 1964 MIT
press statement, also Tier 1) and became
[[claim-rajchman-rival-filing-forced-legal-contest-over-forresters-inventor-status]].
Retrieve-before-write against `30-notes/` found the obvious neighbor —
yesterday's
[[claim-an-wang-1949-patent-filing-predates-forresters-1951-core-memory-patent]]
— immediately; I did not duplicate it. The new note states a genuinely
distinct, higher-tier angle (primary confirmation of two specific dates)
and wikilinks back, and I appended a short `audit_status` note to the
older note explaining exactly what's now resolved and what still isn't.

What's still not resolved, and I want this plain: this capture only
verified the Wang/Forrester half of a four-name sequence. Viehe's 1947
filing and Rajchman's own exact filing date and patent number remain
unread against a primary, and Pugh's 1984 *IEEE Transactions on
Magnetics* paper — the peer-reviewed history both the original question
and this capture name as the real escalation target — is still unread by
any vault session. I flagged the `eight-months-earlier` Rajchman/Forrester
gap (a quantitative detail, Tier 3 only, Tom's Hardware) inside the new
note's `audit_status` rather than promoting it as a clean number, and I
did not open a new question for it — it isn't load-bearing for the
claim's core point (that the contest happened and was settled by
litigation), and the existing open question already covers exactly this
gap. I appended a dated progress line to
[[question-verify-core-memory-patent-filing-dates-primary-sources]]
instead of closing it: partially answered, genuinely still open.

Entity work: one new hub page, [[entity-jan-rajchman]]. He clears the
person-hub bar cleanly — real, recurring now across two sessions, and I
can say in one sentence why he matters: he's the rival filer whose own
earlier application is the reason filing order and legal inventorship
diverge in Forrester's case. I declined hubs for Frederick Viehe and
Emerson Pugh — both are named leads this capture explicitly did not read
directly, and giving either a page on the strength of being *mentioned*
again is exactly the flood the entity spec warns against. Research
Corporation (the patent-management nonprofit that held Forrester's
patent and was itself a party to the litigation) I also declined — it
acts within this one cluster only, and the org bar is deliberately
stricter than the person bar for exactly that reason. I updated both
existing hubs additively rather than leaving them silent: [[entity-an-wang]]
gets a dated line noting his filing date is now Tier-1-confirmed rather
than resting on a museum page, and [[entity-jay-forrester]] gets a dated
line recording the Rajchman contest and the $13,000,000 settlement figure
— a fact neither his page nor any existing note had before today. I also
appended a short update to [[moc-attribution-and-origin-myths]]'s open
thread on this exact domain, noting it's now partly Tier 1 rather than
Tier 3 top to bottom, without promoting it to full membership — Viehe and
Pugh are still missing and I'm not going to let the MOC imply a confidence
the sourcing doesn't have yet.

What felt off: nothing about this capture's sourcing discipline — it's
careful in a way I appreciated, explicitly scoping its own Tier 1 read to
the Wang/Forrester pair and naming, rather than quietly dropping, the two
legs (Viehe, Rajchman's own date) it didn't verify. The one thing that
did catch my eye is the shape of the capture itself: this is now the
second session in two days circling the exact same four-name sequence,
and the genuinely hard part — Pugh 1984, the one peer-reviewed source
named from the start — is still sitting unread on both days' "further
leads" lists. Easy verification (read the patent, it has a date on it)
keeps getting done; the one source that would actually settle the whole
sequence keeps getting named and not fetched. Not a defect, just a
pattern worth noticing: a question can look like it's making progress
every session while its hardest dependency doesn't move at all.

No new `seek-flags.md` entry — the Pugh-1984 gap is already visible in
the open question's own text and in the MOC's open-thread bullet; writing
it a third time in the ledger wouldn't route it anywhere new.

Re-checked the capture's frontmatter after writing: `status: promoted`
with the `promoted_to:` (3 items — two claims, one entity) and
`not_promoted:` (3 items, each with reasoning) lists are both in place on
disk.

Skipped, per this run's standing instructions: the pause-for-Cali step
(headless, no one to ask) and the git commit (the auto-commit agent has
it within 15 minutes).

## Second promotion, same day

A second capture in this same cluster:
`10-inbox/raw/2026-09-12-does-a-peer-reviewed-history-pugh-1984-or.md` —
the direct-verification session against the *other* open question from
yesterday, [[question-verify-forrester-self-credit-characterization-pugh-1984]]
(the self-mythologizing charge itself, not the patent-filing-date leg the
first capture handled). This one went looking for Pugh 1984 and for
Wang's own oral history — the two sources the routing question named as
most likely to settle whether Forrester really did promote himself as
core memory's sole "hero inventor."

The dead link from yesterday resolved. Wang's 1970 Smithsonian oral
history is now read directly, in full, for the first time — Tier 1,
first-person, the actual man most likely to be aggrieved — and it says
the opposite of what the routing question expected: Forrester's matrix
scheme is described as a separate, later technical contribution, not
usurped credit. I promoted that as
[[claim-an-wang-1970-oral-history-frames-forrester-contribution-as-separate-not-usurped]].
Pugh 1984 itself stayed out of reach — IEEE Xplore served non-PDF
content, and the Internet Archive's scan is lending-restricted — but the
capture surfaced a decent secondary account of it (J. A. N. Lee, IEEE
Computer Society), which states Pugh gives Wang full credit and locates
the actual erasure of Wang's role in Redmond & Smith 1980 and MIT's own
1990 archives newsletter, not in Forrester personally. I promoted that
too, flagged `[unverified-historical — needs primary]`, as
[[claim-lee-1995-account-says-pugh-1984-credits-wang-fully]].

The capture's own third claim header — "neither source corroborates the
charge" — I did not promote as its own note. It's the conjunction of the
first two claims with no independent source under it; turning it into a
third file would have been three angles on one finding wearing different
hats. It belongs where a synthesis with no source of its own belongs:
I folded it into the open question's Progress log and into
[[moc-attribution-and-origin-myths]]'s open thread instead, both updated
today, both still honest that Pugh's own words are the thing that would
actually close this out and neither route reached them.

Entity work: one new hub, [[entity-william-papian]] — the MIT engineer
Wang's own testimony names as the one who physically visited him to learn
the technique. Real, named performing a specific action in a Tier 1
primary quote, easy one-sentence case. I declined a hub for Emerson
Pugh even though he's the whole reason this capture exists, on purpose:
this morning's other promotion session already ruled that being named as
an unread lead isn't enough, and today all I have on him is still
secondhand — Lee's characterization of what his book says, not his book.
Giving him a page on the strength of a citation about a citation is
exactly the flood the entity spec warns against, and I'd rather be
consistent with this morning's ruling than carve an exception because
the mention got slightly more specific. J. A. N. Lee, Redmond & Smith,
and Richard Mertz I declined for a related reason — none of them are
actors *in* the 1948-1951 history, they're people who later wrote or
recorded *about* it, and that's a thinner claim on a hub than the spec's
one-sentence test is really asking for. Howard Aiken I also declined,
not on principle but on bookkeeping: he's genuinely significant (he
assigned Wang the founding problem) but he only appears in this
capture's own Entity-candidates line, not inside any claim-note text I
actually wrote today — no anchor yet. Both existing hubs,
[[entity-an-wang]] and [[entity-jay-forrester]], got additive dated
lines instead of silence: Wang's page now records that his own words
don't read as aggrieved, and Forrester's page now records that neither
source named as most likely to confirm his self-credit charge actually
does.

What felt off, and it's the same thing I flagged this morning from the
other capture: this vault keeps naming Pugh 1984 as the source that would
settle this, and Pugh 1984 keeps not getting read. Today's session tried
two separate routes — IEEE Xplore, the Internet Archive — and both
blocked, which is at least a more thorough attempt than "not read this
session," but the result is the same shape of gap. I added a `seek-flags.md`
line ([spec]) suggesting sources.md gets a proper known-blocked entry for
Pugh 1984, the way it already has one for ethw.org and rand.org, so a
future session doesn't re-spend a whole cycle rediscovering the same two
dead ends before trying something else — Google Books, a library ILL
request framed as a lead, a different institutional mirror. The sourcing
discipline in this capture itself was otherwise careful: it earned its
`[unverified-historical]` flag honestly instead of quietly dropping it,
and its own commentary called out the Tier-3-telling-me-about-Tier-3
problem before I had to.

Re-checked this capture's frontmatter after writing: `status: promoted`
with `promoted_to:` (3 items) and `not_promoted:` (6 items, each with
reasoning) are both in place on disk.

Skipped again, same reasons as above: the pause-for-Cali step and the
git commit.

## Third promotion, same day

A third capture, from a different chain entirely:
`10-inbox/raw/2026-09-12-hop-ludwik-rajchman-unicef-cold-war-squeeze.md`.
This one started as an unfollowed hook from yesterday's Forrester capture
— Jan Rajchman, the RCA rival filer, left unresearched to avoid
over-branching — and wandered one generation sideways into his father,
Ludwik Rajchman: League of Nations Health Organization director from
1921, founding chairman of UNICEF from 1946. A computing-hardware patent
fight and a UN institution's founding turn out to share a household.

I promoted two claim-notes and one new entity hub. The bridge itself —
[[claim-ludwik-rajchman-unicef-founder-was-jan-rajchmans-father]] — is a
biographical/definitional pairing (Tier 4 Wikipedia for the father-son
line, corroborated in kind by a named-author Tier 3 account of the
UNICEF founding), which clears the sourcing floor for an uncontested
biographical claim even though it's the more surprising half of the
capture. The second note,
[[claim-ludwik-rajchman-squeezed-out-by-both-cold-war-blocs]], is the
capture's real payload: his career ended within a few years via a US
McCarthy-era subpoena *and* a Polish revocation of his passport — pressure
from both blocs at once. I kept this whole note at `seedling` and flagged
it `[unverified-mechanism]`, because the McCarthy leg is a single,
uncited Wikipedia sentence with no corroboration, while the Polish leg is
solidly Tier 3 with a named author. A note is only as strong as its
weaker leg, and I said so plainly in the note rather than letting the
neater-sounding "squeezed from both sides" framing paper over the
asymmetry. Routed to a new question,
[[question-verify-ludwik-rajchman-mccarthy-subpoena-fbi-file]] — the FBI
file that would settle it directly was unreachable this session
(archive.org, 502/timeout, three attempts per the capture), and this is
a genuine load-bearing gap, not a nice-to-verify hedge, so it earned a
question rather than just a `watch_flag`.

Retrieve-before-write against `30-notes/` turned up nothing on UNICEF, the
League of Nations, or Ludwik Rajchman by name — the capture's own claim of
"pure orphan territory" held up. The semantic-index hint surfaced the
existing Wang/Forrester/Rajchman patent cluster (correctly — Jan Rajchman
is the hinge) and also a cluster of Lepsius "squeeze method" notes, which
share only the word "squeeze" with this capture's title and nothing else;
I checked and set those aside as a false friend rather than force a link.

Entity work: one new hub, [[entity-ludwik-rajchman]] — clears the bar
cleanly (real, founded a major UN institution, and I can say in one
sentence why he matters here: he's Jan Rajchman's father, bridging the
computing-patent cluster to an entirely separate institutional history).
I updated [[entity-jan-rajchman]] additively rather than leaving today's
earlier-created page silent about a fact learned two sessions later in
the same day — a dated `## Updates` line naming the father and linking
the new claim and entity page. I declined hubs for T.V. Soong and Jean
Monnet (named only in the capture's Further-leads section, unanchored in
any claim-note text, same reasoning this vault applied to Howard Aiken
earlier today) and for the International School of Geneva, Aleksander
Rajchman, and Ludwik Hirszfeld (unfollowed family/institution hooks, no
independent research this session). All four are named in the
capture's `not_promoted:` list with reasoning rather than silently
dropped.

I also added one `seek-flags.md` line, tagged `[post]`: the bridge is a
strong candidate for a longer piece, but I don't think it's ready to
draft until the McCarthy leg is confirmed or the whole "double squeeze"
framing is honestly a single-sided one. Flagging it now means the
first-seen moment isn't lost even though the writing itself waits.

What felt off: nothing structurally wrong with this capture's sourcing —
it was unusually candid about its own weak point, flagging the McCarthy
claim as uncorroborated in its own body rather than making me discover
it. If anything, the capture undersold how clean the good half of the
finding is: the father-son link and the UNICEF/LNHO biography are
solidly sourced and would stand as claims on their own even without the
double-squeeze framing. The one real gap is the same shape as this
morning's Pugh-1984 pattern — a specific, named primary (the FBI file)
that would settle the load-bearing question directly, sitting one fetch
away and unreachable this session. I did not re-flag that as a tooling
gap; it's a genuine access failure on this session's attempt (502/timeout,
three tries), not a known-blocked route worth adding to `sources.md` yet.

Re-checked this capture's frontmatter after writing: `status: promoted`
with `promoted_to:` (4 items) and `not_promoted:` (4 items, each with
reasoning) are both in place on disk.

Skipped, same reasons as the other two promotions today: the
pause-for-Cali step (headless, no one to ask) and the git commit (the
auto-commit agent picks this up within 15 minutes).

## Fourth promotion, same day

A fourth capture, back in the Song Jian/Greenhalgh cluster:
`10-inbox/raw/2026-09-12-what-genuinely-connects-greenhalghs-1976-leadership-consensus-predates.md`
— another bridge-seed check, this one on the pairing between
[[claim-greenhalgh-1976-predates-1978-sequencing-depends-on-contested-song-jian-dating]]
and
[[claim-greenhalgh-2003-article-independently-corroborates-june-1978-leading-group-meeting]]
(cosine 0.87, never checked as this specific pair before).

I promoted one note:
[[observation-greenhalgh-1976-predates-and-june-1978-notes-share-landlord-not-argument]].
The capture read like it had found something, and it had — just not as
much as its own three "Claim:" headers suggested. Retrieve-before-write
caught the overlap immediately: the exact "fifteen pages apart, p.170 and
p.185, same 2003 article" fact its first claim header presents was
already sitting in
[[observation-liang-2009-and-greenhalgh-2003-are-symmetric-shared-landlord]]
from 2026-09-08, almost sentence-for-sentence. Rather than skip the
capture or silently restate the duplicate, I wrote the one thing that
actually was new — that these two *specific* target notes had never been
read against each other, and that the June-1978 note's independent
robustness can't be borrowed to defend the 1976-predates-1978 note's
contested dating against Olsder — and credited the prior note by name for
the fact it had already established. The capture's third claim header
("this is the cluster's now-repeated pattern") I folded into the new
note's commentary as framing rather than writing it up as its own file;
it's true and worth saying, but it isn't a new primary finding, it's
narration about the finding shape, and this cluster already has enough
observation-notes doing exactly that job.

Two threads got progress lines instead of new files. The capture's
"further leads" section surfaced IFAC's own commissioned institutional
history (Kahne et al. 2017) confirming the 7th Congress was a five-day
Helsinki event opened by President Kekkonen with 1,100 attendees — solid
Tier 1, but no month, so it can't confirm the "12-16 June 1978" day-range
the capture was actually chasing (which would have put Song's trip within
two weeks of the 26-28 June Leading Group meeting). I appended that as a
progress line to the already-open
[[question-song-jian-1978-europe-trip-identify-as-ifac-helsinki-congress]]
rather than promoting an unverified-quant claim or opening a new question
for a lead that question already owns. I did the same for
[[question-verify-song-jian-1975-twente-delegation-visit]] — this
session's finding sharpens what that dispute is and isn't touched by, but
doesn't move it toward resolution, so a progress line was the honest
move, not a new claim.

Entity work: no new pages. IFAC itself was flagged by the capture as
"worth a page of its own," and I declined — it's a single-cluster
mention and it doesn't act in the argument (fund, decide, block), it just
hosts a congress Song attended, which is exactly the org-promotion bar
entity-page-spec-v0.1 sets deliberately high to prevent. I did update
three existing hubs additively rather than staying silent about a known
entity learning something new, per the standing rule: one dated line each
on [[entity-song-jian-1986-essay]], [[entity-susan-greenhalgh]], and
[[entity-geert-jan-olsder]], each recording the same underlying fact from
that hub's own angle. I left [[entity-li-xiuzhen]] untouched and said so
in the capture's `not_promoted:` list — her page already covers the p.185
citation in full; there was nothing this capture taught about her
specifically that her page doesn't already say.

What felt off: the capture's own bridge-seed methodology is sound — it
did check whether this exact slug pair had been named together before,
and it hadn't — but it didn't check whether the underlying *facts* it was
about to present had already been recorded under a different pairing.
Three of this cluster's last five bridge-seed captures have now
rediscovered a fact a sibling session already banked, from a slightly
different angle each time. That's not fabrication or bad sourcing — every
quote in this capture checked out verbatim against the same sha-matched
PDFs already on file — it's a retrieval gap specific to a cluster this
dense: checking "have these two slugs been paired" is cheaper than
checking "has this specific page-and-citation fact been stated anywhere
in the cluster's ~40 notes," and the batch worker did the cheap check. I
didn't open a `[defect]` flag for it — the retrieve-before-write step at
promotion time is exactly the backstop that caught it here, working as
designed — but it's worth naming as a pattern if it happens a fourth
time.

Re-checked this capture's frontmatter after writing: `status: promoted`
with `promoted_to:` (1 item) and `not_promoted:` (6 items, each with
reasoning) are both in place on disk.

Skipped, same reasons as the other three promotions today: the
pause-for-Cali step (headless, no one to ask) and the git commit (the
auto-commit agent picks this up within 15 minutes).

## Fifth promotion, same day

A fifth capture, back in the Song Jian/Greenhalgh cluster for the third
time today:
`10-inbox/raw/2026-09-12-what-genuinely-connects-liang-zhongtangs-2009-essay-and.md`
— a bridge-seed check on the pairing between
[[claim-liang-2009-and-forrester-1971-essays-connect-only-through-song-jian-note]]
and
[[claim-greenhalgh-2003-and-2005-1978-dating-footnotes-cite-identical-song-1986-essay-pages]]
(cosine 0.87, never checked as this exact pair).

I promoted zero claim-notes from this one, on purpose. The capture's
verdict is real and I don't doubt the read: the Tier-1 quote grounding
[[claim-song-jian-missile-scientist-engineered-one-child-policy-via-cybernetics-of-population]]
(Greenhalgh's 2005 abstract sentence) is itself a compressed restatement
of the same footnote-17 passage that
[[claim-greenhalgh-2003-and-2005-1978-dating-footnotes-cite-identical-song-1986-essay-pages]]
already traced to Song's unread 1986 essay. But retrieve-before-write
found this dependency, or something close enough to it that a new note
would be a sixth or seventh restatement, already sitting in two existing
notes from adjacent angles
([[observation-liang-2009-sentence-bridges-forrester-note-and-olsder-1975-note]]
via the Olsder-contradiction route, the identical-essay-pages claim via
the footnote-comparison route). The capture's second and third "Claim:"
headers (dependency-not-duplication; two independent routes converging on
one soft spot) are the same underlying finding narrated twice more. I
folded the genuinely new sliver — which specific sentence in which
specific note traces to which footnote — into a progress-log line on
[[question-verify-song-jian-1975-twente-delegation-visit]] and a dated
Updates line on [[entity-song-jian-1986-essay]], and left it at that. The
capture's fourth claim (the MOC's "upstream" and "sourcing scaffolding"
sections aren't cross-linked) I agreed with but didn't act on — its own
text correctly names this as a MOC-editing call, not a promotion's — and
routed it to `seek-flags.md` under `[entity]` instead.

This is the pattern this morning's fourth promotion named and declined to
flag yet ("worth naming as a pattern if it happens a fourth time"). It has
now happened a fourth and fifth time in one day, on the same document. I
wrote the `[watch]` flag that promotion held back: at least six sessions
this week (2026-09-03, 09-05, 09-08, 09-10, 09-11, and two today) have
independently re-confirmed some version of "the 1978 dating traces to one
unread essay, quoted twice by one author, never checked against itself,"
each from a new textual angle, and the sources.md single-source
concentration cap — no more than three claim-notes on one unrefereed
primary without independent corroboration — reads as already well past
its limit for this essay once the observation-type bridge notes are
counted alongside the claim-type ones. Nothing here is fabricated or
badly sourced; every quote checked out verbatim against sha-matched PDFs
already on file. The problem is shape, not accuracy: a batch pipeline
keeps generating high-cosine bridge-seed pairs inside one already-dense
cluster faster than the cluster's one real bottleneck — Song Jian's 1986
essay itself, still unread by any session, and *Just One Child*, also
still unread — actually gets any closer to being read. Six sessions
confirming the same soft spot is not six times the evidence; it's one
finding, well-established by now, that no amount of further bridge-seed
work on Greenhalgh's footnotes is going to move. I flagged this as a
Cali-level call: whether future bridge-seed batch sessions on this exact
document should pause until the essay or the book is actually located and
read.

Re-checked this capture's frontmatter after writing: `status: promoted`
with `promoted_to:` (0 items — genuinely zero this time) and
`not_promoted:` (4 items, each with reasoning) are both in place on disk.

Skipped, same reasons as the other four promotions today: the
pause-for-Cali step (headless, no one to ask) and the git commit (the
auto-commit agent picks this up within 15 minutes).

## Sixth promotion, same day

A sixth capture, back in the persistent-homology cluster:
`10-inbox/raw/2026-09-12-what-genuinely-connects-persistent-homology-is-a-gradient.md`
— a bridge-seed check on the pairing between
[[observation-persistent-homology-gradient-free-bridge-widrow-byzantine]]
and
[[observation-hub-selection-artifact-absent-by-design-in-founding-ph-generalization-papers]]
(cosine 0.87, never checked as this exact pair). Unlike today's fourth and
fifth promotions in the Greenhalgh cluster, this one held up all the way
through — the capture found a genuinely new primary read, not a restated
old one.

I promoted three notes. The first,
[[observation-ph-bridge-and-hub-selection-absence-form-one-argument]], is
the capture's own first claim: the two flagged notes aren't two independent
resemblances, the second note's opening question is the first note's
closing paragraph, asked again eleven days later by a different session.
I kept this at neutral synthesis rather than editing either of the two
existing notes to cross-link them directly — the new note does that job by
linking both, and I didn't want to invent an ad-hoc append protocol for
routine relinking when the operating spec only sanctions dated append
blocks for corrections. The second,
[[claim-rieck-2019-neural-persistence-computed-without-subsampling]], is a
clean new Tier 1 finding: the capture actually fetched and quote-checked
Rieck et al.'s 2019 "Neural Persistence" paper this session (not just cited
it by reference, unlike the other three sources in its frontmatter) and
found the same absence-of-subsampling property the vault's other two
founding NN-PH diagnostics already showed. Three-for-three now. The third,
[[observation-hub-selection-risk-needs-incomplete-object-nn-diagnostics-read-complete-record]],
is the capture's most interesting move: not just "three papers, no
selection step" but *why* — all three read a complete, directly-recorded
object (a network's own weights), while the Byzantine study's vulnerability
exists specifically because its trade network is a partial reconstruction
of something no one recorded in full. I kept the scope honest in the note
itself: this explains an absence in three examined diagnostics, it doesn't
prove immunity for the field.

I did not promote the capture's fourth "Claim:" header. It restates the
first and third claims combined — "the bridge holds at the shared-operation
level, doesn't extend to shared vulnerability, and the resemblance is real
not superficial" — without an independent finding of its own, so a fourth
file would have been a third angle on the same two arguments. I also left
the capture's four "Further leads" bullets unpromoted and unrouted to
`50-questions/`: none of them is a load-bearing doubt a kept claim actually
rests on (Corneanu et al., Chowdhury et al., Rieck's appendix, and a
dedicated search for structurally-selective diagnostics are all genuine
next steps, but nothing I wrote today depends on any of them being
resolved).

Retrieve-before-write against `30-notes/` confirmed no existing note
already covered any of the three claims — the semantic-index hint's other
candidates (the Widrow, Birdal, and Gutiérrez-Fandiño notes and entities)
were all cited *by* this capture rather than colliding with it.

Entity work: two new hubs and one concept page, plus two additive updates.
[[entity-bastian-rieck]] clears the person bar cleanly — first author of a
paper this session actually read and quoted, third founding diagnostic in
an active cluster. [[entity-herbert-edelsbrunner]] is the more interesting
call: no claim-note this session or any prior one reads his own work
directly, but the capture named a real blind spot — he's the acknowledged
co-originator of persistent homology itself, the formalism every note in
this cluster rests on, and the vault had given hub pages to several later
co-authors but never to him. I promoted him anyway, on the strength of an
uncontested, easily-stated biographical fact (Tier 3–4 clears the floor
for that kind of claim per sources.md) rather than treating "no primary
read yet" as disqualifying — the entity spec's bar is "real, matters, one
sentence why," not "already quoted." [[entity-neural-persistence]] gets a
concept hub, load-bearing in this exact cluster now. I declined a hub for
Karsten Borgwardt, the paper's senior author — "runs the lab" is true of
almost every last author and isn't a distinguishing fact on its own; he
stays a mention via Rieck's page. I updated [[entity-tolga-birdal]] and
[[entity-asier-gutierrez-fandino]] additively, each with a one-line dated
note that a third diagnostic now confirms the same design property their
pages already describe about themselves.

I added one `seek-flags.md` line, tagged `[entity]`: Edelsbrunner's gap is
probably not unique to this cluster — the capture's own framing ("co-authors
get caught, the older figure does not") reads like a general pattern, and
it's worth a pass checking other established clusters for a foundational
figure with no page of their own, rather than waiting for each cluster's
batch capture to happen to notice it.

What felt off: nothing about this capture's own sourcing — the Rieck quote
is a genuine direct read this session (`extract_pdf`, quote-checked), and
the capture was honest about which of its four listed sources were
re-fetched versus cited by reference to already-verified notes. If anything
this is the cleanest of today's six captures: no restated finding, no
tier inflation, and its own fourth claim header correctly recognized (in
its text, even though I still declined to promote it as a separate file)
that it wasn't adding anything the first and third hadn't already said.

Re-checked this capture's frontmatter after writing: `status: promoted`
with `promoted_to:` (6 items) and `not_promoted:` (3 items, each with
reasoning) are both in place on disk.

Skipped, same reasons as the other five promotions today: the
pause-for-Cali step (headless, no one to ask) and the git commit (the
auto-commit agent picks this up within 15 minutes).

— Seek

---

## Promotion — Maslow 1966 hammer-wording verification capture

Promoted `10-inbox/raw/2026-09-09-does-maslows-the-psychology-of-science-1966-pp.md`,
and this one promoted to **zero claim-notes** — which is the honest outcome, not a
miss. The capture was a dedicated recon session that set out to answer one open
question — does Maslow's *The Psychology of Science* (1966), pp. 15–16, actually
read "I suppose it is tempting, if the only tool you have is a hammer, to treat
everything as if it were a nail," read directly off the book rather than via Quote
Investigator? — and it failed on every route. Both Internet Archive scans are
behind controlled-digital-lending walls (the OCR transcript of one separately
marked private), archive.org's search-inside 403'd across subdomains, HathiTrust
403'd, Google Books is snippet-only and its API rate-limited. The whole capture is
one flagged negative result: `[unverified -- could not confirm or deny after search]`.

A "we couldn't verify" is not a claim-note. The vault's model is one assertable
claim per note, and this capture asserts nothing about the world — it reports a
failure to reach a primary. Its correct home already existed:
[[question-verify-maslow-1966-psychology-of-science-hammer-wording]], the very
question the session was chasing. So per question-closure discipline I left the
question **open** and gave it a dated **Progress** line recording every route tried
and blocked, plus the fresh leads worth a retry when a route reopens (the Google
Books API once the 429 clears; the 2002 Bassett reprint; a HathiTrust manual
consultation; the Millersville Bland/deRobertis articles). Writing a claim-note
would only have duplicated the question — and made a promise the vault would have
had to keep pretending was an answer.

**Winnowed and left behind** (all logged in the capture's `not_promoted:`): the
central negative result (→ the question); the access-barrier facts, whose real home
is sources.md's known-blocked catalog, not 30-notes/ (→ a [spec] seek-flags line);
Wikipedia's Tier-4 citation of pp. 15–16, which corroborates the page *location*
nobody disputes and not the *wording* everyone does (→ folded into the question);
and Doeben-Henisch 2020's omission of the passage, a weak negative corroboration
and a curiosity, not a durable claim (→ folded into the question).

**Questions:** none created — the exact verification question already existed and
is precisely scoped. Question intake discipline says make few promises; this one
was already on the books.

**Entities:** [[entity-abraham-maslow]] already has a hub, so I appended one dated
line — the vault now records on his page that a direct-read attempt was made and
blocked, which it didn't say before (it only said the leg was Tier-2-only). I did
**not** create a Garson O'Toole / Quote Investigator hub, though the capture flagged
him as "arguably worth" one and he genuinely is the Tier-2 backbone the whole
misattribution cluster rests on. A hub's first sentence is public-facing and needs
verifiable biographical detail (his real name, the 2017 book) I have no network to
confirm from the promotion organ — and the entity spec's tie-breaker is "when
unsure → don't promote." Flagged [entity] for a Warden pass with a live route.

**Retrieve-before-write:** the local index hint was dead-on — the cluster
([[claim-law-of-the-instrument-named-by-kaplan-predates-maslow]],
[[claim-clark-2016-hammer-nail-quote-matches-weizenbaum-1982-not-maslow]],
[[entity-abraham-maslow]], and the open question) already holds everything this
capture touched. No collisions to resolve because there was nothing new to file.

**What felt off / worth flagging:** nothing off about the capture itself — if
anything it's a model of honest recon. The sonnet-5 batch worker tried a genuinely
wide net of routes, recorded each 403 and 429 with its exact endpoint, kept its own
Tier-5 IA-reviews data point explicitly caveated as "description, not evidence," and
raised no safety flags on clean sourcing. The one structural observation worth
keeping in view: this is now the *third* corner of the hammer-nail genealogy where
the vault's evidence bottoms out at Quote Investigator (Tier 2) — the Weizenbaum leg
got rescued to Tier 1 via a Wayback capture of the 1982 NYT, but the origin leg,
Maslow's own page, stays locked. The cluster's earliest and most-quoted link is its
least-verified one. That's not a defect to fix tonight; it's the shape of the thing,
and the open question already carries it. There's a small irony worth naming: three
strangers on archive.org went looking for the same sentence and hit the same missing
pages. We didn't triangulate the quote. We triangulated the difficulty.

Re-read this capture's frontmatter from disk after writing: `status: promoted`,
`promoted_to: []`, and `not_promoted:` (5 entries, each with reasoning) are all in
place.

Skipped, as on every headless promotion: the pause-for-Cali step (no one to ask)
and the git commit (the auto-commit agent picks this up within 15 minutes).

— Seek

---

## Promotion — "same surface behavior via opposite mechanisms" (ELIZA/PARRY → LLM circuit)

Promoted `10-inbox/raw/2026-09-09-does-same-surface-behavior-via-opposite-mechanisms-the.md`,
a batch recon that set out to check whether the "same output, opposite mechanism"
shape recurs in the vault's imitation-game and model-collapse material. Three primary
sources, all read directly this session at capture time and all Tier 1: Colby, Weber &
Hilf 1971 (Stanford CS124 full-text PDF), Weizenbaum 1966 (UMBC CS331 mirror), and
Lindsey et al. 2025 on transformer-circuits.pub. Careful sourcing — each paywalled
venue of record is named honestly with its course-hosted full-text reproduction, and
the single `[unverified]` flag is scoped precisely to "the published model-collapse
literature beyond this vault," not smuggled in as a clean fact.

**Two notes out of three claims.** Claim 1 — PARRY and ELIZA were judged by the same
indistinguishability test on architecturally opposite mechanisms (simulated internal
affect-states vs. stateless keyword transformation) — is a genuinely new, atomic, Tier-1
finding with no existing home, so it became
[[claim-parry-eliza-same-indistinguishability-test-opposite-mechanisms]]. Claim 2 — the
Anthropic circuit-tracing paper shows one model reaching the identical output token via
two coexisting opposite pathways — I deliberately did **not** give its own claim-note:
the factual content already lives, verbatim quote and all, in
[[claim-biology-llm-dallas-texas-austin-genuine-two-step-reasoning]] (which was audited
2026-07-12 and quotes "coexists alongside 'shortcut' reasoning"). A duplicate would
restate an existing audited note. The genuinely new thing is the *cross-domain
recurrence* of the shape — so that, plus Claim 3's disambiguation, went into one
observation note,
[[observation-same-output-opposite-mechanism-recurs-eliza-parry-to-llm-circuit]], which
links the existing Dallas note rather than duplicating it. Claim 3 — the model-collapse
corpus carries no such shape, only a categorically different "same mechanism, different
pace" ([[claim-model-collapse-bottleneck-width-sets-pace-not-shared-timescale]]) — is a
negative/scoping finding that ages poorly as a standalone file, so its durable kernel
folded into the observation's third section with the `[unverified]` caveat preserved.

**Questions:** none created, none closed. The lone unverified flag is a negative-search
caveat about outside literature, not a load-bearing doubt any kept claim rests on — so
per intake discipline it stays a body caveat, not a 50-questions promise. I checked
50-questions/ for a matching open question to rule on; there is none (the capture's
`derived_from` lists claim/observation notes, not a question).

**Entities.** One new `watching` stub: [[entity-indistinguishability-test]] — Colby's own
term, an emerging bridge between Turing's imitation game, PARRY's evaluation, and later
LLM benchmark design; stamped with first_seen 2026-09-12 because that date can't be
backfilled, and kept a stub rather than a hub because recurrence isn't proven yet. I
declined hubs for the two 1971 co-authors Sylvia Weber and Franklin Hilf — named once,
as co-authors, with no vault-domain role I can state in a sentence; that's the flood the
spec warns against. Three existing hubs got additive dated lines rather than silence:
[[entity-kenneth-colby]] (PARRY's mechanism + his own "indistinguishability test" name),
[[entity-joseph-weizenbaum]] (ELIZA as the stateless opposite), and [[entity-alan-turing]]
(the imitation-game criterion enters as a third, unrelated axis on his page). All three
pages previously said nothing about this contrast; the capture's own note that the
Turing→Colby lineage "is not yet stated on either entity page" was correct, and is now
discharged.

**seek-flags.md:** two lines. `[post]` — "same-X-opposite-Y" may be a named vault genre
the way embedding "false friends" already is; the capture names four cross-corpus notes
sharing the shape, and a whole-vault synthesis essay is the natural home, not this
promotion. `[watch]` — Colby's 1971 paper cites a 1972 follow-up indistinguishability
study (Heiser et al.) whose actual empirical result the vault has no note for; worth a
direct read if a session lands near it, no action owed now.

**What felt off:** genuinely little. This is one of the cleaner captures I've promoted —
it caught its own commissioning error (the topic pointed at the RFC 439 / Paxos
joke-bridge as the shape's origin; that note is about opposite *reception outcomes*, not
opposite *mechanisms*, and the capture said so plainly instead of forcing the fit) and it
refused to stretch the model-collapse bottleneck-width note to cover a shape it doesn't
have. The one thing to keep in view is the near-duplication risk on Claim 2: the capture
framed "Anthropic names a second coexisting pathway" as something the Dallas note "does
not itself make," but the Dallas note's own source_quote is "coexists alongside 'shortcut'
reasoning" — so the new content was the cross-domain framing, not the fact, and writing it
as a fresh claim-note would have been a restatement. Retrieve-before-write caught that;
working as designed.

Re-read this capture's frontmatter from disk after writing: `status: promoted`,
`promoted_to:` (2 items — one claim, one observation), and `not_promoted:` (3 entries,
each with reasoning) are all in place.

Skipped, as on every headless promotion: the pause-for-Cali step (no one to ask) and the
git commit (the auto-commit agent picks this up within 15 minutes).

— Seek

---

## Seventh promotion, same day — Polanyi's Logic of Liberty (spontaneous order / Mont Pelerin)

Promoted `10-inbox/raw/2026-09-11-read-michael-polanyis-own-1951-the-logic-of.md`,
a batch capture that did something the last several didn't: a real Tier-1
primary read (Polanyi's own 1951 *Logic of Liberty*, fetched via extract_pdf,
236pp) cross-checked against Struan Jacobs's 1997 Polanyi/Hayek comparison and
Boettke's review of the Hoover Mont Pelerin transcripts. It's the follow-up to
[[observation-michael-polanyi-person-bridges-three-vault-clusters-invisible-to-vault-bridge]],
which had left an open hook: is Polanyi's Mont Pelerin life a genuinely
separate third chapter, or does it tie back into the tacit-knowledge cluster?

**Five claim-notes out of four capture headers.** I split the first header —
it bundled two genuinely distinct assertions with different load-bearing
sources — into [[claim-polanyi-published-spontaneous-order-1948-predating-hayeks-own-use]]
(the priority, resting mainly on Jacobs) and
[[claim-polanyi-1951-logic-of-liberty-names-hayek-only-three-times-not-in-spontaneous-order-chapters]]
(the primary-read finding that Polanyi never staged a Hayek dispute in his own
book — Hayek named only three times, all on the economic-calculation debate,
never in the spontaneous-order chapters). The other three headers each became
one note: the substantive divergence on ends
([[claim-polanyi-hayek-spontaneous-orders-differ-on-directedness-toward-ideal-ends]]),
the continuity thesis
([[claim-polanyi-logic-of-liberty-continuous-with-tacit-knowledge-epistemology]]) —
which is the actual answer to the observation note's hook, and it runs opposite
to "separate chapter": the political and epistemological writing are one
continuous fiduciary argument — and Popper's Mont Pelerin role
([[claim-popper-attended-mont-pelerin-1947-after-objecting-to-hayeks-exclusionary-format]]).

**Retrieve-before-write.** No collisions. The vault had nothing on spontaneous
order, the Polanyi-Hayek relationship, or Popper's Mont Pelerin objection. The
closest neighbors — the observation note and the tacit-knowledge/Dreyfus
cluster — I linked densely rather than duplicated. The continuity note in
particular closes the loop the observation note opened.

**One question routed.** [[question-verify-hayek-first-published-use-spontaneous-order]] —
the priority claim's load-bearing negative (Hayek didn't use the term before
1960) rests on one Tier-2 scholar, and "first use" negatives are exactly the
sentences that hide an unchecked earlier counterexample. That's a genuine
load-bearing doubt, so it earned a question. I did *not* open questions for the
softer gaps — the Hayek "cosmos has no purpose" quote reaching me secondhand
through Jacobs, the Tier-3 Hoover participant roster — those are body caveats,
not promises. Intake discipline: few promises.

**Honoring flags / audit_status.** All five notes are `capture-verified` at
`seedling`. The primary was read directly at capture, but I have no network to
re-check it, by design; the verifier bee sweeps them. Where a quote reaches me
through a secondary (Hayek via Jacobs) or a roster is Tier 3, the note says so
in its own body and audit_status rather than presenting a clean fact.

**Entities.** Two new hubs, one additive update, three declines. [[entity-friedrich-hayek]] —
load-bearing across this capture and the observation note, founder of Mont
Pelerin, the figure Polanyi's priority is measured against; clean one-sentence
case. [[entity-karl-popper]] — I promoted him on the strength of a real second
cluster, not fame: he's already in the vault since 2026-07-11 as the Popperian-
falsification grounding of Heuer's ACH
([[claim-heuer-grounds-ach-in-cognitive-psychology-decision-analysis-scientific-method]]),
so his first_seen is that date, and the Mont Pelerin note gives him a second,
independent cluster — a genuine bridge person, not a one-mention lead. I
reordered nothing on his page because it's new, but I made sure the first
sentence introduces the man (falsifiability, Open Society) before the vault,
per the public-first-sentence rule. [[entity-michael-polanyi]] already had a
hub, so I appended one dated 2026-09-12 line (additive, per the never-silent-
about-a-known-entity rule) linking all four new Polanyi claims. Declined hubs
for Struan Jacobs, Peter Boettke, and Bruce Caldwell — all cited authors or
custodians rather than actors in the history, and Caldwell specifically is
named as keeper of a transcript volume this session never fetched, which is
the "unread lead" case yesterday's rulings already declined. All three declines
are in the capture's `not_promoted:` with reasoning.

**seek-flags.md.** Two lines. `[watch]` — the Polanyi-Hayek material is now
three notes deep on a single Tier-2 secondary (Jacobs 1997); the concentration
cap formally targets unrefereed primaries so it doesn't trip, but a second
independent scholar on the same two men is worth having before this branch
grows. `[post]` — "the drama is added in post": the whole capture is a clean
instance of an intellectual-history conflict assembled by later readers rather
than staged by the people living it, and it pairs with the vault's attribution-
and-origin-myths thread. Real essay candidate, not ready to draft.

**What felt off.** Honestly, very little — this is the cleanest batch capture
I've promoted in a while, and a relief after a day of Greenhalgh-cluster
bridge-seeds that kept re-banking facts the vault already held. It did a real
primary read, scoped its Tier-1 claims to the pages it actually read, and was
scrupulous about the two admissibility lines: it flagged the unfetched Chicago-
visiting-stint lead as `[unverified — needs primary]` itself, and it refused to
quote Popper's transcript words because they'd only come through a search-
summary layer. That's the fabrication rule being honored by the capture, not
just by me at promotion. The one substantive thing to keep in view is the
Jacobs single-analyst concentration I flagged — not a defect in this capture,
just the shape of a cluster that's growing fast on one good secondary. And a
small tier note: the capture labels its own Jacobs-based comparison "Tier 2 for
the comparison itself, Tier 1 for the Polanyi side," which is exactly right and
the opposite of tier inflation — it split the tiers the way I would have.

Re-read the capture's frontmatter from disk after writing: `status: promoted`
with `promoted_to:` (9 items — five claims, two new hubs, one hub update, one
question) and `not_promoted:` (9 items, each with reasoning) are both in place.

Skipped, as on every headless promotion: the pause-for-Cali step (no one to
ask) and the git commit (the auto-commit agent picks this up within 15 minutes).

— Seek

---

## Third promotion, same day — the Greenhalgh bridge-seed capture

Another headless run, another capture from the batch worker:
`10-inbox/raw/2026-09-11-what-genuinely-connects-in-greenhalghs-2005-china-quarterly.md`.
A bridge-seed pairing — the 2005 tight-arc observation against the 2003
diffuse-critique claim, cosine 0.87, unlinked — asking whether the two notes
were really connected or just riding a shared author to a friendly similarity
score. The capture's verdict was that the bridge holds *more precisely* than
either note stated alone, and reading it against the existing cluster I agree.

I found three distinct claims and promoted all three. The 2005 Dutch-work
critique (pp. 266–267) is a *fourth constituent beat* inside the
consensus-to-dissent arc, not merely adjacent to it —
[[claim-greenhalgh-2005-dutch-work-critique-is-a-constituent-beat-of-the-consensus-to-dissent-arc]].
The 2003 analogous critique falls *entirely outside* its article's pp. 178–187
citation-to-dissent run, bracketing it from both sides —
[[claim-greenhalgh-2003-dutch-work-critique-falls-outside-the-citation-to-dissent-run-on-both-sides]].
And the two together make a *third independent measurement* of the "2005
welds, 2003 disperses" compositional pattern, alongside the narrative-structure
and consensus-position findings already on file —
[[observation-greenhalgh-dutch-critique-placement-is-a-third-measurement-of-the-2005-welds-2003-disperses-pattern]].

Retrieve-before-write mattered here, because this cluster is dense and the
easy failure was writing notes that already exist. The two closest neighbors —
[[claim-greenhalgh-2003-dutch-work-critique-present-but-diffuse-not-co-located-with-citation]]
and
[[claim-greenhalgh-2005-dutch-work-critique-conceptually-matches-clark-attributed-phrases]]
— each measure something adjacent but not identical. The existing diffuse-critique
note measures *distance from the citation* (eight pages each way); my new 2003
note measures *placement relative to the whole run* (outside it, on both ends).
The existing Clark-match note established *what* the 2005 critique says; my new
2005 note fixes *where* it sits (inside the arc, as a beat). Distinct angles,
wikilinked back rather than duplicated. No collisions I had to resolve by
overwriting.

**Questions routed: zero.** The capture's two "further leads" — does the 2003
article weld its critique to the *dissent* rather than the citation, and does
any fifth Greenhalgh-2005 claim fall inside the same span — are genuine future
work, but they're curiosities, not doubts any kept note rests on. Per
question-intake discipline they stay leads in the inbox, not promises in the
pile. The one load-bearing subtlety — whether the p. 187 critique passage is
the last line of "A policy set in political stone" or the opening of
"Conclusions," a page-boundary call where the capture and the vault's existing
run-map read slightly differently — I put in the note's `watch_flag` rather
than a question, because the finding (critique outside the tight run) survives
either resolution. The verifier bee re-fetches and can settle the seam.

**What felt off.** The capture's `## Entity candidates` section flagged
Kwakernaak first with "no entity page exists for him yet despite repeated
wikilinks across this cluster" — but `entity-huibert-kwakernaak.md` has been a
live hub since 2026-08-14, with eight dated update lines. All four candidates
(Kwakernaak, Greenhalgh, Song Jian, Liang) already have pages. The bee's
entity-candidate step doesn't seem to check `40-entities/` before declaring a
page missing; I logged that as a `[defect]` in `seek-flags.md`. The finding
itself is about *Greenhalgh's composition*, so I added one dated line to her
hub (the third-measurement convergence) and left the other three pages
untouched — silence there is correct, not a miss. I also flagged the
"welds vs disperses" cluster as an MOC candidate (`[entity]`): it's at five+
notes now, but building it unprompted in a headless run felt like scope creep,
so I left it for a judgment session.

No open question matched this capture's topic, so nothing to close.

**Final-mark check.** Re-read the capture's frontmatter from disk after
writing: `status: promoted` with `promoted_to:` (three notes) and
`not_promoted:` (three entries with reasoning — two leads and the
entity-candidate adjudication) are both landed.

Skipped, as on every headless run: the pause-for-Cali step (no one to ask) and
the git commit (the auto-commit agent picks this up within 15 minutes).

— Seek

---

## Promotion — the BTW/Bak "necessary vs. sufficient" primaries capture (headless)

I promoted `10-inbox/raw/2026-09-12-do-bak-tang-wiesenfelds-own-198788-papers-and.md`,
the capture that finally went and read the two SOC primaries the vault had been
citing only through Watkins et al.'s quotation of them: Bak, Tang & Wiesenfeld's
1988 *Phys. Rev. A* companion paper (a freely-hosted mirror) and Per Bak's 1996
*How Nature Works* (an archive.org scan). The topic question — do BTW's own
papers and Bak's book phrase the threshold as "necessary" rather than "necessary
but not sufficient"? — the capture answers with a cleaner no than expected:
neither primary uses "necessary" *or* "sufficient" about thresholds at all.

**Two notes written** (both `seedling`, both `capture-verified`, writer_model
me):

- [[claim-bak-how-nature-works-independently-confirms-soc-no-tuning]] — Bak's
  book confirms the no-tuning property in his own first-person voice ("we had
  just blindly pushed the pendulums"), a second independent primary beyond the
  1987 letter Watkins quotes, and — the part that earns the note — reserves the
  word "necessary" for the *non*-SOC (tuned) case every time he uses it.
- [[claim-necessary-sufficient-soc-threshold-framing-absent-from-primary-record]]
  — the necessary/sufficient vocabulary is absent from the primary record (1988
  paper read end to end; book agrees), making it a secondary-literature import
  (Golyk's Tier-3 gloss, then Watkins' Tier-1 reformulation). This one merges
  the capture's claim 2 and claim 3.

**Winnowing.** Three claims in the capture; I promoted two by merging 2 and 3.
Claim 3's durable nub (the framing is absent from the primary record) *is* the
merged note's core; its "no revision needed elsewhere" half — the avalanche-term
sweep turning up only the already-corrected
[[claim-engineered-threshold-is-not-self-organized-criticality]] — is
vault-maintenance, not an encyclopedic claim, so it lives here and in the
capture's `not_promoted:` list, not in a third file. I did not split Tang and
Wiesenfeld into hubs, or make one for Golyk or van der Ziel (see below).

**Entities.** Updated two existing pages append-only: [[entity-per-bak]] (added
*How Nature Works* as a directly-read second primary) and
[[entity-self-organized-criticality]] (added an Updates block noting the
no-tuning property is now grounded in two directly-read primaries). Created no
new hubs — bias against the flood.

**Question closure.** The matching question,
`question-verify-soc-no-external-tuning-necessary-not-sufficient`, was already
answered and archived back on 2026-08-30 via Watkins. This capture discharges
its one remaining caveat ("the BTW originals and Bak's book were still not read
directly"), so I added a dated progress line to it rather than reopening —
answered stays answered, now with the primaries actually in hand. No new
question routed: the only open doubt is the two-column-PDF quote-verification
gap, which is a per-note watch the verifier bee owns, not a load-bearing
question for the pile.

**Flags logged** (`00-meta/seek-flags.md`): one `[entity]` — Tang & Wiesenfeld
recur across 4+ notes without hubs, left for the Warden; one `[watch]` — a
1/f-noise priority thread (BTW's 1988 footnote 9 credits van der Ziel 1950 and
frames their own result as "a small generalization"), a real capture waiting to
be written but nothing owed now.

**What felt off about the capture.** Honestly, very little — this is a
well-behaved capture. It correctly diagnosed its own weak spot without inflating
past it: the 1988 paper is two-column, pdftotext interleaves the columns, and so
the load-bearing no-tuning sentence could be *read* but not handed to an auditor
as one contiguous verbatim string. The capture flagged that inline every time
rather than pretending a quote_check pass it never got, which is exactly the
discipline I'd want. Its central finding is also an *absence* claim ("necessary"
and "sufficient" appear nowhere), and an absence is the one thing no quote can
ground and no verifier bee can mechanically confirm either way — so I kept that
note at seedling and said so plainly in its audit_status. No tier inflation
(the book and 1988 paper are genuinely Tier 1, read directly), no duplicated
research (it built *on* the existing Watkins cluster rather than re-deriving it),
sourcing clean. The one thing I'd gently note is that the capture's writer_model
is `claude-sonnet-5` and it leaned on `quote_check`/`extract_pdf` receipts I
cannot re-run headless — but that's the pipeline working as designed, not a
defect. Skipped as always: the pause-for-Cali step and the git commit (auto-
commit within 15 minutes).

— Seek