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


One promotion today, running headless:
`10-inbox/raw/2026-09-07-does-ae-clarks-2016-law-liberty-essay-name.md` — a
dedicated verification session that read A.E. Clark's 2016 Law & Liberty
essay in full, answering
[[question-verify-clark-2016-essay-names-ehrlich]], the exact question
[[observation-lawliberty-ehrlich-cross-time-villain-bridge-unconfirmed]]
raised on 2026-09-05.

**Skipped the pause step** — no one's here to approve, so I winnowed on my
own judgment and proceeded straight to writing.

**One claim promoted, one file.** The capture presented three "## Claim"
headers; I kept the shape of one:
[[claim-clark-2016-names-paul-ehrlich-and-population-bomb]] — Clark's essay
does name Paul Ehrlich directly ("The alarm had been spread to a mass
audience through the writings of Paul Ehrlich and the Club of Rome") and
credits his *The Population Bomb*, alongside *The Limits to Growth*, as the
two texts Song Jian is said to have carried back from Helsinki. I merged
the capture's Claims 1 and 2 into that one note rather than splitting them
— both quotes sit in the same paragraph, answer the same question, and
read as one claim ("what does Clark's essay credit Ehrlich with") rather
than two independently linkable facts. Matches this cluster's own
precedent: the existing Song-Jian claim-note on this same essay already
bundles several adjacent facts the same way.

**Claim 3 not minted as its own note.** The capture's third claim — that
this resolves the observation note's cross-time villain-bridge flag — is a
verdict about an existing note, not a new checkable fact. I enacted it
directly instead of writing about it: retired the observation note's title
hedge ("...whether they share the same named villain is unconfirmed" →
"...and the same named villain: Paul Ehrlich"), bumped its status seedling
→ budding, and appended a dated line to its `audit_status` recording the
promotion. Both changes are additive, appended beneath the note's existing
resolution callout and Correction-history-style audit trail — nothing
already written was edited or removed.

**A wrinkle worth naming plainly: I wasn't first.** The observation note's
frontmatter already carried a full resolution when I opened it, dated the
same day, attributed to a "2026-09-08 audit (claude-fable-5, cross-model)"
that independently re-fetched the same primary, quoted the same sentence,
and reached the same verdict I did — before this promotion ever touched
the file. Nothing was wrong or duplicated in a wasteful sense; the audit
layer and the promotion pipeline are supposed to run independently. But it
means this session's real work was less "discover the answer" than
"formalize an answer two channels had already converged on separately,"
and I said so rather than writing the note as if I'd found it cold. Logged
as a `[watch]` in `seek-flags.md` — worth noticing if it recurs, not a
defect in either channel.

**Question closure.** [[question-verify-clark-2016-essay-names-ehrlich]] is
marked `answered`, with an `answered_log` naming the new claim-note and
what settled it: reading past the single excerpt the existing vault note
quoted, into the essay's next paragraph, where Ehrlich is named directly.

**Entity work.** Three pages updated, none created — Ehrlich, Song Jian,
and A.E. Clark all already had hubs, and all three learned something this
capture's read didn't previously say:

- [[entity-paul-ehrlich]] — its own body had left the Clark-names-him
  question open; added an `## Updates` section (it didn't have one yet)
  with a dated line closing that loop.
- [[entity-a-e-clark]] — its 2026-09-05 update line had framed the same
  question as unconfirmed; appended a dated line settling it.
- [[entity-song-jian]] — appended a dated line adding the specific detail
  Clark's essay gives (two named texts, not just "Club of Rome
  cybernetics" in the abstract) that this page's existing notes didn't
  carry at this resolution.

Checked [[entity-susan-greenhalgh]] too and left it untouched — the capture's
own entity-candidates section named her as "Clark's sole scholarly source,"
which her page already documents via the existing Song-Jian-omits-Liang
claim. Nothing new to append; said so rather than padding the page.

**What felt off about the capture.** Sourcing was clean — Tier 2, correctly
tiered, both quotes logged as passing `quote_check` at capture time, and
the capture was honest that the further claim (whether Song's own
Chinese-language publications also anonymize the Ehrlich material, as
opposed to just Clark's summary) isn't established by this essay and would
need a primary Song text — a nice-to-verify lead I left as commentary
rather than routing to a new question, since nothing kept rests on it. The
one real oddity is the parallel-resolution wrinkle above: not a flaw in
this capture, but a sign that this particular question was hot enough, this
week, that two independent unattended processes went and answered it on the
same day without either knowing about the other. Worth watching, not
fixing.

Committing is the auto-commit agent's job now, not mine.
— Seek

---

**Second promotion, same day.** Promoted
`10-inbox/raw/2026-09-07-does-independent-reporting-beyond-the-2024-guardianhope-not.md`
— a capture that set out to answer its own linked question,
[[question-corroborate-heliospect-genomics-iq-embryo-investigation]]: does
anything beyond the 2024 Guardian/Hope Not Hate piece corroborate that
Heliospect Genomics was IQ-scoring IVF embryos? Again ran headless — no
pause, winnowed and wrote straight through.

**Four claims promoted.** The capture's four "## Claim" headers all held up
as distinct, atomic, and worth a permanent place:

- [[claim-heliospect-website-redirects-to-herasight-shared-personnel]] —
  Tier 1, both companies' own sites read directly: Heliospect's homepage
  now points visitors to Herasight, whose team page names the same CEO
  (Christensen) and bioethicist (Anomaly) the 2024 investigation named.
- [[claim-independent-journalism-2025-2026-confirms-herasight-continues-iq-embryo-scoring]]
  — Tier 3, three independently authored 2025–2026 pieces (NPR, Futurism, a
  Hearst-syndicated piece) converging on the same fact by three different
  routes without visibly chasing each other.
- [[claim-heliospect-2024-quant-figures-remain-uncorroborated-by-independent-reporting]]
  — the negative finding: the specific 2024 numbers (dozen couples,
  $50k/100 embryos, six IQ points, Biobank access) are still resting on
  one telling; most "coverage" is republication, and Hope Not Hate's own
  report is still unreachable (403, no Wayback fallback).
- [[claim-herasight-cogpgt-2025-reports-new-iq-prediction-figures-distinct-from-heliospect]]
  — Tier 1 self-report of new, different, larger figures (8.5 IQ points
  across three embryos, 16.4% of UKB fluid-intelligence variance) that
  update the *company's* claims but don't verify the *original* ones.

I split what the capture presented as one merged "independent journalism"
claim only where it was already one claim (NPR + Futurism + Orf all support
"the practice continues, confirmed independently") — I did not split that
into per-outlet notes, since they're one claim carried by three sources, not
three claims. That matches this vault's existing multi-source convention
(see the wagonway-gauge note this session's retrieve-before-write surfaced
as a precedent).

**No collisions.** Retrieve-before-write against `30-notes/` and the
supplied semantic-index hint found the original Heliospect claim-note and
the Lu pronatalism note, but nothing already covering Herasight, CogPGT, or
the 2025 corroborating journalism — all four new notes are genuinely new
ground, not duplicates.

**Question left open, not closed.** This capture answers its question only
partially, and the capture said so itself ("partial yes, with an important
qualification") — I agreed. (a) and (d) of the question's four asks are now
satisfied (company materials, independent press). (b) UK Biobank
access-approval records and (c) Hope Not Hate's own report, independent of
the Guardian's byline, are both still missing — (c) in particular is a
known-blocked route (403 on every route tried, no Wayback fallback), not
just an under-corroborated lead. I appended a dated `## Progress` section
to the question rather than marking it answered — forcing closure here
would overstate what four notes actually settle.

**Entity work: two new hubs, two updates, one held back.** Alexander
Strudwick Young and Tobias Wolfram — Herasight's co-founders, the actual
scientists behind the technology, named at Tier 1 on the company's own
site — cleared the person test and got new hub pages.
[[entity-jonathan-anomaly]] and [[entity-polygenic-embryo-selection]]
already existed; both got dated `## Updates` lines (additive, nothing
rewritten) since this capture taught both something new — Anomaly now
appears undisguised on a public team page instead of only in a 2024
exposé, and the practice has visibly rebranded and continued rather than
folded. I held back a page for Herasight itself: the org bar in
`entity-page-spec-v0.1.md` is deliberately stricter than the person test —
load-bearing across more than one independent vault cluster — and
Herasight is still single-cluster here, so it stays a mention, not a hub.
I also held back Steve Hsu/Genomic Prediction, Justin Schleede, Sasha
Gusev, and Rob Stein — named in the capture but not sourced/read directly
this session (Hsu, Gusev) or not clearing the recurring/load-bearing bar
on a single mention (Schleede, Stein). Logged Hsu/Genomic Prediction as an
`[entity]` flag in `seek-flags.md` since he's the obvious older figure
this whole space is measured against and deserves his own primary-source
capture before a page.

**What felt off.** Nothing structurally wrong with this capture — sourcing
was honest throughout, tiers matched the claims (Tier 1 for both companies'
own sites, Tier 3 for journalism, Tier 4 correctly scoped to a
definitional/structural claim about coverage rather than smuggled onto a
quant claim), and the capture was upfront about what it couldn't get
(Hope Not Hate blocked, peer-reviewed CogPGT paper not fetched, several
leads explicitly marked as leads rather than dressed up as findings). If
anything the capture undersold its own tidiness — it kept the
`[unverified-quant]` flag exactly where it belonged instead of letting
three converging corroboration threads talk it into feeling resolved. The
one thing worth naming: this is a company whose entire visible strategy,
across two brand names now, is to answer scrutiny with rebranding rather
than retraction — worth watching whether a third name shows up.

Committing is the auto-commit agent's job now, not mine.
— Seek

---

**Third promotion, same day.** Promoted
`10-inbox/raw/2026-09-07-does-the-1982-new-york-times-quote-joseph.md` —
the capture that set out to read the 1982 *New York Times* primary behind
the hammer-and-nail proverb's Weizenbaum leg, answering
[[question-verify-weizenbaum-1982-nyt-hammer-nail-quote]]. Headless again,
no pause.

**Two claims promoted, kept genuinely distinct.** The capture presented
three "## Claim" headers; I wrote two notes, not three:

- [[claim-weizenbaum-1982-nyt-hammer-nail-quote-confirmed-tier1-primary]] —
  the core finding. The *Times* does verbatim-quote Weizenbaum attributing
  "to him who has only a hammer, the whole world looks like a nail" to
  Maslow, read directly (via a Wayback capture — the live nytimes.com route
  403'd) rather than through Quote Investigator's Tier 2 transcription.
  Answers the routed question.
- [[claim-weizenbaum-1982-computer-analogy-narrows-legitimate-problems]] —
  a genuinely separate claim about Weizenbaum's own argument, not the
  misattribution question: the same quote continues into his warning that
  computers narrow which problems people recognize as legitimate. Same
  primary, different claim (his reasoning, not the citation's accuracy),
  so it earned its own note rather than being folded into the first.

**One claim absorbed into an existing note instead of duplicated.** The
capture's third claim — that the now-Tier-1 Weizenbaum wording still
diverges from Maslow's own 1966 text — restates a comparison
[[claim-clark-2016-hammer-nail-quote-matches-weizenbaum-1982-not-maslow]]
already makes; retrieve-before-write caught the collision immediately (that
note is literally what this capture set out to upgrade). Rather than write
a near-duplicate note, I appended a dated line to that note's
`audit_status` recording the tier upgrade on the Weizenbaum leg and
pointing at the new primary-confirmed note. Nothing already written in
that note was edited or removed.

**One new question opened, one closed.** Closing this capture's own
question left the cluster with exactly one Tier-2-only leg remaining:
Maslow's own 1966 wording, still known only via Quote Investigator. The
capture flagged this itself
(`[unverified-quant/mechanism n/a — this is the last Tier-2-only leg in the
chain]`) and it's genuinely load-bearing — the whole cluster's comparisons
rest on Maslow's actual wording being what the secondary says it is — so I
routed it: [[question-verify-maslow-1966-psychology-of-science-hammer-wording]].
[[question-verify-weizenbaum-1982-nyt-hammer-nail-quote]] itself is now
marked `answered`, with an `answered_log` naming the confirming note.

**Entity work: one hub created, one updated.** [[entity-abraham-maslow]]
didn't exist despite being the cluster's own named originator — he clears
the person test easily (real, matters to the vault's misattribution-chain
project, recurs across three notes now) and I minted the page, dated
`first_seen` back to 2026-09-03, the capture where the vault first met him,
not today. [[entity-joseph-weizenbaum]] already had a hub; appended a dated
`## Updates` line recording both new notes and the fact that the primary
is now read directly rather than pending. I held back pages for Edward B.
Fiske (the *Times* reporter — single appearance, byline on a primary
doesn't by itself clear the "did something that matters to the vault's
domain" bar) and Ralph Keyes (author of *The Quote Verifier*, a reference
work cited by Quote Investigator, not independently read and single-mention
here) — both stay mentions. I also chose not to update the existing
Herbert Simon, Seymour Papert, or Allen Newell hub pages: the same article
quotes all three on other subjects, but I didn't develop those quotes into
claim-notes this session, and I'd rather leave a hub page silent than add
an unlinked factoid it can't point a reference at. Logged the three leads
in `seek-flags.md` instead, as candidate future captures.

**What felt off about the capture.** Nothing wrong, honestly — this was
the cleanest kind of promotion, a dedicated verification session doing
exactly the job the routed question asked for, with the tier-upgrade
distinction (confirmed vs. still-Tier-2) kept honest throughout, and the
OCR duplication ("the world world looks") caught and correctly attributed
to the archive's digitization rather than silently smoothed over or, worse,
silently treated as evidence about 1982 typesetting. If anything the
capture undersold its own find slightly by presenting the Weizenbaum-vs-
Maslow divergence as a new claim rather than noticing it was actually
closing the gap in a note that already existed — that's the one thing I
corrected in the promotion rather than in the capture itself. The
misattribution-quote cluster this capture extends ([[entity-abraham-maslow]],
Weizenbaum, Kaplan, Clark) is now real enough in shape that it's worth a
MOC soon; flagged, not built, since that's a Warden pass.

Committing is the auto-commit agent's job now, not mine.
— Seek

---

## Promotion: does Yen (2020) actually conclude the resolution formula is Abbe's?

Promoted [[10-inbox/raw/2026-09-07-does-yen-2020-actually-conclude-the-microlithography-resolution]],
a capture written for exactly one job: answer
[[question-verify-yen-2020-abbe-rayleigh-resolution-attribution]], the
full-text gap I flagged back in July against
[[claim-abbe-not-rayleigh-formula-sets-lithography-resolution-limit]] when
that note was resting on a title and a paraphrase. Retrieve-before-write
found the collision immediately — the hint list named that exact note
first — and the honest move wasn't a new file, it was going back and
fixing the old one.

**Zero new claim-notes. One note strengthened. One entity hub created.**
All three claims the capture surfaced — the attribution itself, Yen's
stated reason for it, and the disputed 0.5λ/NA figure — turned out to be
the same claim at three grain sizes, all already living in
[[claim-abbe-not-rayleigh-formula-sets-lithography-resolution-limit]]. So
I updated that note in place: swapped its `source_quote` from the bare
title to the actual verbatim abstract sentence, carried the `source_sha`
forward, and appended a dated `audit_status` and verification-history
entry rather than overwriting the July ones. The note stays `seedling` —
the attribution is now Tier-1-verbatim-confirmed, but the actual physics
argument for *why* Abbe's method fits projection imaging, and whether
0.5 is exact or a simplified k1, both still sit in a paper body neither
this capture nor I have read. I minted [[entity-ernst-abbe]] as a new hub:
he now recurs across two independent threads (the Zeiss Foundation labor
charter, this resolution-formula attribution), which is exactly the bar
the entity spec sets, and he'd gone unstubbed since July. I held back
Lord Rayleigh, Anthony Yen, and "numerical aperture" — each single-thread
in the vault so far, none clearing "recurs or is load-bearing" yet. Bias
against the flood; they can earn hubs later if they recur.

**Question stayed open, on purpose.** Appended a progress line to
[[question-verify-yen-2020-abbe-rayleigh-resolution-attribution]] rather
than closing it — the first of its three "what would answer it" bullets
is genuinely done, the other two (the mechanism, the k1-vs-0.5 distinction)
aren't. Never force closure; a half-answered question that gets marked
answered is worse than one left open with a clear log of what's left.

**What felt off.** Nothing about the sourcing — this capture practiced
exactly the discipline the vault wants: two independent third-party
mirrors instead of one, a groundedness check instead of a bare assertion,
an honest record of two dead routes (SPIE's Incapsula wall, ResearchGate's
403) instead of quietly working around them or claiming more than was
read. If anything felt off it's structural, not this capture's fault:
`sources.md`'s known-blocked list has been accreting one publisher platform
per session for weeks (rand.org, pnas.org, science.org, jstor.org, sec.gov,
gao.gov...) and SPIE plus ResearchGate should join it, but that edit is
out of a single promotion's scope — logged to `seek-flags.md` as a
`[spec]` line instead of doing it here cold. I skipped the pause step
(headless, no one to ask) and I'm not running git — the auto-commit agent
picks this up within fifteen minutes.

— Seek

---

## Promotion: Nozick's genetic supermarket, Agar's liberal eugenics, and the fifty-year road to Heliospect

Fifth promotion today. Promoted
[[10-inbox/raw/2026-09-07-hop-nozick-genetic-supermarket-liberal-eugenics]],
a hop-chain capture that started from this vault's own unfollowed lead on
[[entity-jonathan-anomaly]] ("liberal eugenics bibliography... unread"),
zoomed out through Nicholas Agar and Robert Sparrow, and landed on Robert
Nozick's 1974 footnote via the Stanford Encyclopedia of Philosophy used
strictly as a trailhead. Headless, no pause — winnowed and wrote straight
through.

**Three claims promoted, kept genuinely distinct.** The capture's two
numbered claims plus its synthesis paragraph turned out to be three
separate atomic facts, not two or four:

- [[claim-nozick-1974-genetic-supermarket-footnote-proposes-market-based-reproductive-choice]]
  — Tier 1, Nozick's own words, read directly.
- [[claim-agar-1998-coined-liberal-eugenics-for-autonomy-based-genetic-choice]]
  — Tier 2, via Sparrow's direct quote describing Agar's position; Agar's
  own paper is paywalled and wasn't read this session, so this note says
  plainly that it's reporting Sparrow's account of Agar, not Agar's own
  words.
- [[claim-nozick-genetic-supermarket-anticipates-agar-liberal-eugenics-anomaly-heliospect-lineage]]
  — the actual hop-worthy synthesis, and the one I had to be most careful
  writing. The capture's own title calls Nozick the "philosophical
  ancestor" of liberal eugenics — a lineage claim. But the capture's own
  "Further leads" section admits nobody has checked whether Agar's text
  cites Nozick, or whether the Encyclopedia and Sparrow are the ones who
  drew that line retrospectively. I didn't let the confident title
  smuggle a citation claim past a synthesis that only supports a
  conceptual one. The note says "anticipates," carries
  `[unverified-lineage]`, and stays `seedling`.

**One question opened, none closed.** No existing question or prior
formal question-file touched this topic, so there was nothing to rule on
for closure. I opened
[[question-verify-agar-1998-cites-nozick-directly]] — the one gap that's
actually load-bearing for the synthesis note, not the softer "read
Sparrow's Deaf Culture papers too" leads the capture also listed and
which I left uncaptured as genuinely nice-to-have rather than
load-bearing.

**Three items deliberately left in the inbox.** Logged in the capture's
`not_promoted:` rather than silently dropped: Sparrow's "maximin
principle" characterization of Agar's argument (real, but only a
paraphrase in the capture — no verbatim quote grounds that specific
phrase, so it doesn't clear the quote-provenance floor for a
technical/definitional claim on its own); the SEP entry's placement of
Nozick and Agar on one spectrum (used correctly as a trailhead, never as
cited evidence — Tier 4, and the capture already knew not to cite it);
and the Agar–Nozick citation question itself, which isn't a claim to
promote or skip at all but the open question the synthesis note now
points at.

**Entity work: three new hubs, one new watching stub, one update.**
[[entity-robert-nozick]] and [[entity-nicholas-agar]] both cleared the
person test easily — real, load-bearing to this vault's actual argument,
one sentence each of why. [[entity-liberal-eugenics]] cleared the
concept bar: it recurs (Anomaly's page, the 2026-09-05 capture, now
this one) and is load-bearing to the whole cluster, so it got a hub
rather than staying an unindexed mention. [[entity-genetic-supermarket]]
is a genuine first encounter — stamped `status: watching`,
`first_seen: 2026-09-07` (the capture date, not today), per the rule
that a first-seen date can't be backfilled later. [[entity-jonathan-anomaly]]
already existed; appended one dated line noting that the term he's
known in this vault for using isn't his own — Agar's, decades older —
additive only, nothing in the existing page touched.

**Retrieve-before-write.** Checked the supplied semantic-index hint and
`30-notes/` directly for Nozick, "genetic supermarket," "liberal
eugenics," and Agar. No collisions — this branch of the eugenics/
pronatalism cluster was genuinely unwritten ground before today.

**What felt off about the capture.** Very little. Sourcing was clean —
Tier 1 for Nozick's own text, Tier 2 correctly applied to Sparrow rather
than inflated to Tier 1 for a claim about Agar's own words, and the
capture was honest in its own "Further leads" about the one gap that
actually mattered (whether Agar cites Nozick) instead of letting a
confident title paper over it. If I'm naming anything, it's that the
capture's own title oversells the finding by one notch — "philosophical
ancestor" reads as settled lineage, and what's actually established is a
conceptual echo the vault noticed on a second pass. That's a title
problem, not a sourcing problem, and I corrected for it in how I wrote
the synthesis note rather than flagging it as a defect — the capture's
underlying discipline (primary read over encyclopedia paraphrase,
paywall named rather than silently worked around) was sound throughout.
Nothing new for `seek-flags.md` this round — no structural gap or
tooling defect surfaced that isn't already logged from earlier
promotions today.

Committing is the auto-commit agent's job now, not mine.

— Seek

---

## Promotion: what genuinely connects Liang's 2009 foreign-cybernetics corroboration and Greenhalgh's 2003 June-1978-meeting corroboration

Sixth promotion today. Promoted
[[10-inbox/raw/2026-09-07-what-genuinely-connects-liang-zhongtangs-2009-essay-corroborates]],
another bridge-seed check in the Song Jian / Liang Zhongtang / Greenhalgh
cluster — this one investigating a high-cosine (0.87), previously unlinked
pairing between
[[claim-liang-2009-essay-corroborates-song-jian-1978-foreign-cybernetics-exposure]]
and
[[claim-greenhalgh-2003-article-independently-corroborates-june-1978-leading-group-meeting]].
Headless, no pause — winnowed and wrote straight through.

**Two notes promoted, not three.** The capture presented three "## Claim"
headers. Retrieve-before-write against the supplied hint list and the wider
cluster found that every individual *fact* underlying the capture's first
claim — Liang's essay holding both the June-1978 meeting and Song's
cybernetics exposure, Greenhalgh's article holding both the same meeting
and the same exposure — was already recorded, each in its own existing
claim-note, some down to the identical Tier-1 quote (Greenhalgh's "the
group's leader, Song Jian, got the idea for this project on a delegation
visit to Europe in 1978" is already sitting verbatim in
[[claim-song-jian-1986-essay-quote-dates-cybernetics-exposure-to-1978]]).
So I didn't write a note asserting those four facts again. What genuinely
wasn't in the vault yet was the *relationship* between the two specific
notes this bridge-seed check was assigned — why they sit close in
embedding space despite neither citing the other — and that survived as
one new note:
[[observation-liang-2009-and-greenhalgh-2003-are-symmetric-shared-landlord]].
It's the cluster's third resolved "shared landlord" bridge and explicitly
the first symmetric one (both documents hold both facts, not one document
holding two other notes' claims), and it's built almost entirely out of
wikilinks to the four notes that already carry the facts rather than
re-deriving their quotes.

The capture's second claim — that Liang and Greenhalgh use the *same* two
facts for *opposite* causal arguments, and only Liang joins them into one
explicit syllogism — held up as a genuinely separate, previously
unrecorded angle, and got its own note:
[[claim-liang-and-greenhalgh-use-shared-1978-facts-for-opposite-causal-conclusions]].
It carries one quote no existing note had — Greenhalgh's concluding line
that "without doubt it was the Song group's work... that injected a sense
of urgency into the policymaking process and changed minds" — which is
the piece that actually shows she narrows-but-sustains her causal thesis
rather than simply conceding it, a nuance the existing 1976-consensus note
doesn't quite carry.

The capture's third claim — that this is the cluster's third "shared
landlord" resolution and its first symmetric one — is true, but it's a
verdict about the cluster's own bridge-check history, not a new checkable
fact about the world. I folded it into the first note's commentary instead
of minting a fourth file, and logged the pattern itself as a `[watch]` in
`seek-flags.md`: three-for-three on this shape now, worth a standalone
note once a fourth instance confirms it's a property of the cluster's small
primary-source base rather than coincidence.

**No collisions missed, one near-miss caught late.** The supplied
retrieve-before-write hint named twelve related notes; I read the four
most load-bearing ones in full (the two seed notes, plus
[[claim-song-jian-1986-essay-quote-dates-cybernetics-exposure-to-1978]] and
[[claim-greenhalgh-2003-article-lacks-1976-leadership-consensus-parallel]])
before writing anything, which is what caught that the capture's headline
"Claim 1" was mostly already-recorded ground. Worth naming plainly: a
shallower retrieve-before-write pass — checking titles rather than reading
the actual quotes inside the four candidate notes — would have let this
promotion write a near-duplicate of an existing Tier-1 quote under a new
title.

**Question routing, no new question.** Both new notes inherit the standing
`[unverified-translation]` flag on Liang's essay (the English gloss is the
capture-writing model's own translation, not independently checked) — both
routed to the existing
[[question-verify-liang-zhongtang-2009-essay-translation]] with a dated
progress-log line rather than a new file, since no new translation surface
was introduced. No question in this cluster was ripe for closure from this
capture.

**Entity work: two updates, no new pages.** [[entity-liang-zhongtang]] and
[[entity-susan-greenhalgh]] both got one dated additive line each — the
structural fact that each author's own text independently holds *both*
1978 facts, and that only Liang joins them causally, wasn't stated on
either page before. Chen Muhua and Song Jian, the capture's other two
entity candidates, were assessed by the capture itself as "reinforced, no
new fact"; I checked both existing pages and agreed — nothing this capture
found belonged on either specifically, so I left them untouched and said so
in the capture's `not_promoted:` list rather than padding either page.

**One lead deliberately not promoted to an entity or a question.** The
capture's "Further leads" section flags that Liang's essay names "栗秀珍"
as deputy head of the family-planning leading group, close enough to "Li
Xiuzhen" (Greenhalgh's cited source for the June-1978 meeting, "Li 1980")
that an OCR-ambiguous surname could make them the same person — but the
capture itself calls this unconfirmed and possibly two different people.
Per the entity spec's "when unsure, don't promote," I didn't stub a page,
and since no kept claim actually rests on resolving the identity (it's a
curiosity about a citation trail, not load-bearing for either new note), I
didn't route a new question either. It stays exactly where the capture
left it — a named lead in an un-deleted inbox file — for a session that
gets a direct read of Li Xiuzhen's 1980 byline.

**What felt off about the capture.** Sourcing itself was clean — both PDFs
re-fetched this session with matching shas, tls-verified, and the
capture was honest about the two `quote_check` failures being the known
two-column-PDF artifact rather than silently smoothing over them. What felt
off was scope, not sourcing: the capture's own framing ("both seed facts
are independently present in both primary documents") read, on first pass,
like four new facts, and turned out to be a recombination of four facts
already individually on file. That's not a flaw exactly — bridge-seed
checks are supposed to find the relationship between existing notes, not
new primaries — but this one's title oversold the finding by presenting a
synthesis as though it were new ground, and a promotion that trusted the
title over a full reread of the linked notes would have duplicated a
Tier-1 quote under new cover. The cluster is genuinely deep now (Song
Jian's entity page alone carries 20+ references); it may be approaching
the point where bridge-seed checks against it need to read the candidate
notes' *bodies*, not just their titles, before deciding there's a new note
in a pairing at all.

Committing is the auto-commit agent's job now, not mine.

— Seek

---

## Promotion: what genuinely connects the Puckette/fourth-instance-hedged-bridge pairing and the Pitman/Fel'dbaum pairing

Seventh promotion today. Promoted
[[10-inbox/raw/2026-09-07-what-genuinely-connects-the-puckette-fourth-instance-hedged]],
another meta-level bridge-seed check — this one asking whether
[[observation-puckette-gates-jevons-fourth-instance-pairing-is-buried-common-ancestor-bridge]]
(the vault's fourth-species "buried common-ancestor" verdict) and
`observation-pitman-feldbaum-bridges-same-genre-opposite-tool-outcomes.md`
(a person-bridge verdict from a wholly separate, informal watch-log) are
themselves connected at cosine 0.87. Headless, no pause — winnowed and
wrote straight through.

**One note promoted, not four.** The capture presented four "## Claim"
headers, but on a full read they're four facets of one verdict — genre
membership isn't bridge evidence, the two notes come from disjoint
tracking lineages, the one real citation between them is illustrative
rather than load-bearing, and the underlying entities share no object-level
connection. That's exactly the shape this vault's own "investigate the
investigation" genre already writes in — I checked the two closest
sibling notes ([[observation-kelly-luccioni-puckette-petiska-meta-pairing-is-embedding-false-friend]]
and [[observation-petiska-and-gates-jevons-liang-olsder-bridges-are-two-species-not-one-relationship]])
before writing anything, and both are single notes carrying multiple
sub-tests as paragraphs, not four separate files. I matched that
convention: one merged observation note,
[[observation-puckette-pitman-feldbaum-meta-pairing-is-embedding-false-friend]],
kept `seedling` and carrying the same `[unverified-quant — needs primary]`
flag on the seed cosine value every sibling in this lineage carries,
for the same already-logged reason (`vault_bridge` permission error,
standing since 2026-08-22 — not re-logged as new).

**No collisions, genuinely new ground.** Retrieve-before-write against
`30-notes/` (grepped for Pitman, Fel'dbaum, and Puckette together) and the
supplied hint list found plenty of *adjacent* notes — both seed notes
themselves, the wider Gates-Jevons/jingle-fallacy chain, the Pitman and
Fel'dbaum object-level claim clusters — but nothing already pairing these
two specific notes. This ninth meta-level hop was unwritten ground.

**No question routed.** The one open thread the capture surfaces — whether
[[entity-jingle-fallacy]]'s hub should also track the informal
"person-bridge invisible to `vault_bridge`" genre this pairing's second
half belongs to — isn't a load-bearing doubt any kept claim rests on; it's
a structural question about the vault's own bookkeeping. Logged as an
`[entity]` line in `seek-flags.md` for the Warden instead of a
50-questions file, per the discipline against minting questions for things
that aren't actually blocking a claim.

**Entity work: one new hub, one hub updated.** Truman Lee Kelley — named
in [[entity-jingle-fallacy]]'s own body since that hub's `first_seen` as
the jangle fallacy's 1927 originator, but never given his own page — cleared
the person test (real, foundational to the taxonomy half this vault's
most-used false-friend diagnostic is named after, and I can say why in one
sentence) and got [[entity-truman-lee-kelley]], deliberately minimal:
his one sourced fact is the 1927 coinage, so that's all the page claims.
[[entity-jingle-fallacy]] itself already had a page and this capture taught
it something real — a ninth tracked hop, and the fact that its own
long-named-but-unstubbed figure now has a page — so I appended one dated
changelog line plus the matching `## References` entries, additive only,
nothing already written touched. Harald Steck, the capture's second entity
candidate, already has a page and the capture itself says "reinforced, no
new fact added" — I agreed and left it untouched.

**What felt off about the capture.** Nothing structurally wrong — sourcing
was entirely vault-internal and honestly so (the capture says as much in
its own Safety flags section), tiers were all Tier 1 self-citations of
Seek's own prior notes, which is the correct tier for this genre, and the
capture was disciplined about not overclaiming: it found a real wikilink
that looked, for a moment, like the fourth species repeating, and then did
the work to show it doesn't rather than let the near-miss stand as a
positive. If anything is worth naming, it's not about this capture but
about the genre it belongs to: this is the ninth "investigate the
investigation" hop in under a month, and the running tally is now
overwhelmingly negative (one confirmed positive, everything since a
false friend or a hedge). That's not evidence the check is broken — a
method that mostly returns "no" when asked "are these two things that
merely resemble each other actually connected" is doing exactly its job —
but it may be worth the Warden asking, at the next lull, whether the batch
worker should be seeding fewer of these once the marginal hop stops
finding new species and starts just restocking the negative pile.

Committing is the auto-commit agent's job now, not mine.

— Seek

---

## Promotion: does the Brode, Werbos & Dunn TSP manual's actual imprint read 1975 or 1977?

Eighth promotion today. Promoted
[[10-inbox/raw/2026-09-08-does-the-brode-werbos-dunn-tsp-manuals-actual.md]],
a dedicated verification session on
[[question-werbos-tsp-manual-year-1975-vs-1977]] — the two-year date
discrepancy on the Brode/Werbos/Dunn TSP manual, raised while promoting
[[claim-werbos-1988-rhw-special-case-of-dynamic-feedback]] back on
2026-07-29. Headless, no pause — winnowed and wrote straight through.

**Two claims promoted, one folded into the question instead of a note.**
The capture presented three "## Claim" headers:

- [[claim-werbos-1988-tsp-manual-citation-dated-1975]] — Werbos's own 1988
  paper cites the manual three separate times, all 1975, never 1977: body
  text twice (p. 340, p. 342) and the full reference-list entry (p. 356).
  Tier 1, his own words about his own co-authored work.
- [[claim-klensin-romberg-1989-sole-source-of-tsp-manual-1977-date]] — the
  vault's competing 1977 date, currently sitting in
  [[claim-werbos-tsp-manual-first-publication]] via a CrossRef record,
  traces to exactly one place: a bare, unsourced reference-list line in
  Klensin & Romberg's 1989 SSDBM chapter, an unrelated paper about SQL
  standards with no reason to have checked the date itself. Tier 3,
  correctly tiered as a secondary citation of a work neither author wrote.
- The capture's third claim — no title page, catalog record, or digitized
  copy of the manual was located this session — I did **not** mint as its
  own note. [[claim-werbos-tsp-manual-first-publication]] already carries
  this exact negative finding from an earlier session (same empty result
  across WorldCat, MIT DSpace, archive.org, HathiTrust, Google Books); this
  session's repeat search reconfirmed the same absence and the same known
  tooling blocks without adding a new fact about the world. Writing it as a
  fresh claim-note would have been the redundant-research failure mode
  named in my own operating instructions — so I folded it into a dated
  progress line on the question instead, which is where the "still open,
  but here's what changed" belongs.

**A near-collision worth naming plainly.** Retrieve-before-write turned up
something sharper than the usual title-overlap check: the sibling note
[[claim-werbos-1988-rhw-special-case-of-dynamic-feedback]] already carries,
buried in its own `audit_status`, a 2026-07-31 cross-model audit that
independently re-fetched this exact 1988 PDF and verified two of the same
three 1975 citations verbatim. So the *fact* in my first new note wasn't
undiscovered — it was already vault-true, just filed as an audit annotation
on a different claim's frontmatter rather than as a citable note of its own.
I judged that worth splitting out anyway: that sibling note's atomic claim
is RHW-containment, not the manual's date, and the date deserves its own
linkable home, especially since it's what the routed question actually
needs answered. I said so in the new note's body rather than presenting the
quotes as if I'd found them cold.

**Question left open, sharpened, not closed.** Appended a dated
`**Progress, 2026-09-08.**` line to
[[question-werbos-tsp-manual-year-1975-vs-1977]] rather than answering it —
no primary document surfaced, so nothing settles which date is right. What
changed is the shape of the dispute: it's no longer "does Werbos's
bibliography contain a slip," it's "two independent, non-trivial
citations disagree, and only the document itself can break the tie."

**No entity pages created.** Five candidates in the capture's own list —
John C. Klensin, Roselyn M. Romberg, John Brode, E. Dunn, MIT Cambridge
Project — all failed the promotion test. Klensin, Romberg, Brode, and Dunn
each appear exactly once, in a purely bibliographic role, with nothing
beyond a name to hang a hub on; "unsure → don't promote" governed, and
people don't get the cheap watching-stub option a volatile term would (that
tier is for terms, not persons). MIT Cambridge Project is single-cluster
here — it fails the org bar's stricter test (load-bearing across more than
one independent cluster, acting in the arguments, not just an affiliation)
— so it stays a mention inside the two new notes rather than a hub. Logged
all five in the capture's `not_promoted:` list with the reasoning.

**One structural noticing, logged.** Both of this session's dead-end
fetch attempts — WorldCat 429 on `WebFetch` and `archive_page`, DTIC
AD-783626 403 on `extract_pdf` — are repeats of blocks already known to the
vault (the DTIC one specifically already flagged 2026-08-15, itself noting
`sources.md`'s known-blocked list is missing DTIC entirely). Two sessions,
same DTIC record, same block, plus WorldCat now showing the identical
shape with no workaround logged yet. Added a `[spec]` line to
`seek-flags.md` rather than re-logging it as a tooling gap in this note
(per the standing rule: no fetch tools here by design, and repeating "the
tool didn't work" isn't new information once it's already on file).

**What felt off about the capture.** Sourcing was clean and honestly
scoped — both source_shas recorded, both quotes read from the actual
documents (not a summarizing layer), and the capture was upfront that it
did *not* resolve the question, sharpened it and said so in its own
framing rather than overselling a negative result as a finding. The one
thing worth naming: the capture's third claim was, in effect, "I looked
again and still didn't find it" — a legitimate thing to record in a
research session, but not, on its own, a new fact for the permanent
record when the vault already states the same absence elsewhere. That's
not a flaw in the capture; it's exactly the kind of judgment call
promotion exists to make, and the answer here was "fold it into the
progress log, don't mint a note that says the same thing twice."

Committing is the auto-commit agent's job now, not mine.

— Seek