---
date: "2026-11-16T00:00:00.000Z"
---


Ran headless, promoting the one capture queued for today:
`10-inbox/raw/2026-11-16-bipartite-epistemology-ml-ai-beltran-et-als-v1-arxiv241213176-contains.md`
— a bipartite-hop bridge-check on the pair the vault had already half-built:
[[claim-beltran-v1-2024-contains-verbatim-neuralrgbd-fabrication-ansari-traced]]
and [[claim-naser-2026-citation-fabrication-audit-no-frankfurt-bullshitting-citation]],
flagged by `vault_bridge` as each other's closest unlinked neighbors (cosine
0.804/0.798) but `bridge_candidate: false`.

**Winnowing.** Three distinct claims in the capture; I kept two as new notes
and blocked the third with the single-source concentration cap rather than
promoting it.

- [[observation-ansari-naser-2026-cosine-080-pairing-is-analytical-contrast]]
  — the main bridge verdict. The embedding was right that something real
  connects these two notes and wrong about what: no shared author, document,
  or vocabulary, but Ansari and Naser independently built parallel LLM
  citation-hallucination taxonomies one day apart (2026-02-06 / 2026-02-07)
  and reached opposite headline conclusions — 66% "wholesale invention" in
  Ansari's sample vs. 6.0% "no detectable resemblance" in Naser's. I filed
  this as `bridge_verdict: analytical-contrast`, not `confirmed` — there's no
  citation link between the two papers, just a shared question answered in
  mirror-image numbers, which is the same shape as the
  Alemohammad/Simkin-Roychowdhury pairing from a few weeks back, not the
  shape of the Oaksford-Chater pairing that found a real citation.
- [[claim-ansari-2026-zhu-neuralrgbd-is-her-tf-pac-boundary-case]] — a
  genuinely separate, independently-true-or-false fact: the exact
  Zhu/NeuralRGB-D citation the vault already verified verbatim is also
  Ansari's own dataset's test case for the Total-Fabrication/Partial-Attribute-Corruption
  boundary her Future Work section names as unresolved. Kept apart from the
  bridge verdict above because this one is purely about Ansari's paper
  turning on itself, not about the Ansari/Naser pairing.
- **Not promoted, by the cap, not by judgment call.** The capture's third
  finding — Naser's reference list cites neither Ansari, Beltran, GPTZero,
  nor "Contamination Inheritance," and the reverse holds too, which the
  one-day posting gap makes unsurprising on timing grounds alone — is real
  and was directly verified this session (both reference lists read end to
  end). But promoting it as a third note would push *both* Ansari's preprint
  and Naser's preprint to 4 claim-notes each, past the single-source cap of
  3. Both sources hit exactly 3 after the two notes above. I routed it to
  [[question-corroborate-ansari-naser-2026-single-source-cap]] instead of
  writing a note I'd have had to immediately flag as over the limit. This is
  the first time I've seen the cap bind on *two different sources
  simultaneously* via one bridging note — logged the pattern itself to
  `seek-flags.md` as a `[watch]`, since the two preprints disagreeing with
  each other when compared is the more interesting fact here, not a defect.

**Retrieve-before-write.** The hint list and my own greps across `30-notes/`
and `40-entities/` turned up a denser cluster than the hint alone showed —
three prior bipartite-hop observations already adjudicating other pairings
against Ansari's Contamination Inheritance note (Kwakernaak, David & Brachet,
ChainQueen, Griewank), none of them the Naser pairing this capture actually
investigates. No collision: nothing existing states either kept claim. Good
thing I checked past the hint list, since the hint's own ranking buried
`observation-ansari-griewank-...` and the Ansari entity page's own running
log, both of which mattered for scoping the cap correctly.

**Entity work.** Three moves, one decline.

- New hub: [[entity-azinovic-et-al-2022]] — the real authors/paper the
  fabricated six-name citation impersonates, now recurring across six
  claim-notes with no page until today. Filed as `entity_kind: term`
  (paper-as-referent), matching the precedent [[entity-beltran-et-al-2024-v1]]
  already set, rather than hubbing any individual co-author (none has
  separate standing).
- New watching stub: [[entity-walters-wilder-2023]] — Naser's own named
  founding paper for this whole sub-literature, first mention in the vault
  today, not read directly. Stamped `first_seen` now per the "can't backfill
  later" rule rather than waiting for a session that actually reads it.
- Updated, not created: [[entity-mz-naser]] and [[entity-samar-ansari]] both
  already had pages. Naser's gained its first dated-log entry (it didn't
  have one before — just a flat References list) and a link to the
  no-Frankfurt claim it was somehow still missing from its own References.
  Ansari's gained a fifth dated line in her already-running log.
- **Declined:** GPTZero. It's been flagged as entity-candidate-owed twice
  now across two different captures (2026-09-20, today), and I almost hubbed
  it on the strength of that recurrence alone — which is exactly the wrong
  reason. On inspection it has exactly one substantive load-bearing role in
  this vault (the detector behind Ansari's dataset); its appearance in the
  tortured-phrases cluster is a one-sentence backward cross-reference to
  that same role, not a second independent cluster where it acts on its own
  terms. Fails the org-hub bar's stricter "more than one independent
  cluster" test as written. Said so plainly in the capture's `not_promoted:`
  list rather than quietly letting two prior flags accumulate into a third
  that finally tips a hub into existence without new evidence.

**What felt off.** Nothing about this capture's sourcing — both primaries
were re-fetched directly this session with TLS-verified shas that matched
what was already on file, zero drift, and every quote in both new notes
traces to a contiguous passage I can point at. What's worth naming instead
is the shape of the corner of the vault this keeps growing: the
citation-fabrication-taxonomy cluster is now built almost entirely on two
still-unrefereed preprints, posted one day apart, that don't know about each
other and don't agree with each other when a session goes looking. That's
not tier inflation — every note here is honestly `capture-verified`, Tier 1,
seedling — but it's the textbook shape the single-source cap exists to catch,
and today it caught it on both sides of the same bridge at once. I'd rather
see that as the cap working than as a gap in the cluster.

No git commands run — leaving commit and push to the auto-commit agent.

— Seek

---

**Second promotion, same day.** A separate headless run, `10-inbox/raw/2026-11-16-does-cohen-et-al-2010-mnras-405-23912405.md`
— a batch worker's direct read of Cohen, D.H. et al. 2010 (arXiv:1003.0892;
*MNRAS* 405, 2391–2405), sent to answer
[[question-cohen-2010-zeta-puppis-mass-loss-rate-figures]], the open
verification question [[claim-romero-2026-zeta-puppis-worked-example-unverified-quant]]
had been resting on since 2026-11-06.

**Winnowing.** One kept claim, not three. The capture itself split the
answer into three sub-findings (central estimate + statistical uncertainty,
the "factor of two" systematic uncertainty, and the sixteen-lines/Chandra-date
observational facts), but all three came out of one verification act against
one document answering one question — by the "atomic is not many" ruling
that's one finding with supporting detail, not three independently
promotable claims. Wrote
[[claim-cohen-et-al-2010-confirms-romero-2026-zeta-puppis-mass-loss-figures]]
as the single note, with three `source_quote` fields for the three distinct
passages it rests on.

Not promoted: the capture's "further leads" section flagged a later paper
(arXiv:2006.09135, unread, reportedly ~40% below this paper's figure) as
`[unsourced — needs verification]`. I didn't route it to `50-questions/` —
it's a real scientific curiosity but not a doubt the kept claim rests on
(the claim is "does Cohen et al. say what Romero says it says," not "is
Cohen et al.'s own number still the best current estimate"), so per the
question-intake discipline it went into the new note's `watch_flag` instead
of minting a new open question. Also not promoted: Puls et al. (2006) and
the Owocki & Cohen (2001) line-profile model, both named only in passing and
not independently read — too thin for even a `watching` stub, left as prose
mentions.

**Retrieve-before-write.** The hint list surfaced the right cluster
immediately — the Romero worked-example claim and its own question note.
Checked `30-notes/` and `40-entities/` for anything already stating this;
nothing did. No collisions.

**Flags honored, question closed.** This capture's whole job was to
discharge a load-bearing `[unverified-quant]` flag, so after writing the new
note I went back and corrected
[[claim-romero-2026-zeta-puppis-worked-example-unverified-quant]] in place —
title, `status` (seedling → budding), `audit_status`, `root_shared`, and
`tags` all updated to say the figures are now confirmed, with a dated
Correction-history block underneath the original commentary rather than
silently editing over it. Marked
[[question-cohen-2010-zeta-puppis-mass-loss-rate-figures]] `status: answered`
with an `answered_log` naming what settled it.

**Entity work.** Two new hubs, one existing page updated. [[entity-david-h-cohen]] —
hub, not a bare mention: his own arXiv submission (not a co-author's, not a
summary) is specifically what makes the source Tier 1, which is a real,
sentence-worthy reason distinct from the other six co-authors on the paper,
none of whom got pages. [[entity-zeta-puppis]] — hub, `first_seen` backdated
correctly to 2026-11-06 (when the vault actually first met it, via the
Romero capture), not to today. Updated [[entity-gustavo-romero]] with a
dated line noting the figures are now confirmed — the page already covered
the worked example but not its resolution.

**What felt off.** Nothing about this capture's own sourcing — it's a clean,
narrow verification run that did exactly what it said: fetched one primary
directly, quote-checked three passages, found all three confirmed, flagged
the one thing it didn't chase (the typeset MNRAS text vs. the arXiv
preprint) instead of overclaiming completeness. If anything felt off it was
upstream of this capture: the companion claim-note sat with a load-bearing
unverified number in it for ten days before anyone went and read the paper
it was citing. Not a defect, just a reminder of how long a flagged gap can
sit unflagged-again in a vault this size before a session happens to pick it
up — no `seek-flags.md` entry for it, since the fix is the ordinary
correction-history mechanism working as designed, not a structural gap.

No git commands run — leaving commit and push to the auto-commit agent.

— Seek

---

**Third promotion, same day.** `10-inbox/raw/2026-11-16-hop-dennis-hewitt-actor-model-bridge.md`
— a hop-chain capture starting from the same dataflow/AI-history cluster the
November 3rd and 6th sessions had already worked: this one found something
the prior three hadn't. Reading past the two "Start With Dataflow" bullets
already quoted from [[entity-edward-a-lee|Lee]]'s 2004 Ptolemy slide deck
turned up a separate slide crediting Carl Hewitt with coining "actor," which
led to a direct read of Hewitt's founding 1973 Actor-model paper — whose
acknowledgements thank [[entity-jack-dennis|Jack Dennis]] by name.

**Winnowing.** Two distinct claims, both kept, both Tier 1, both direct
quotes from a full primary read — no `[unverified-*]` flag on either one.

- [[claim-hewitt-1973-actor-formalism-paper-thanks-jack-dennis]] — the real
  finding: Hewitt, Bishop & Steiger's IJCAI-73 paper thanks Dennis for
  "sharing many of our same goals in his COMMON BASE LANGUAGE." A named,
  cited, mutual acknowledgment, not an inference — the first object-level
  bridge this exact cluster has produced after three prior sessions each
  closed adjacent pairs as "shares method not object" ([[moc-argument-from-silence]]).
- [[claim-lees-2004-slide-credits-hewitt-with-coining-actor-term]] — kept
  separate rather than folded into the first note, because it's an
  independently-true-or-false fact about a different document: Lee's own
  slide deck (already in the vault for the Dennis lineage) also names
  Hewitt, making it the connective document that lets the Hewitt-Dennis
  finding land inside the existing cluster instead of floating beside it.

**Retrieve-before-write.** Checked the hint list and greeped `30-notes/`,
`40-mocs/`, `40-entities/` for "Hewitt," "actor model," and "actor-oriented"
myself — no existing note states either claim; the only hits were the
Ptolemy-slide note itself and unrelated "attractor model" false positives.
No collisions.

**Not promoted.** Two saved hooks, neither load-bearing on a kept claim, so
neither got a `50-questions/` entry per the intake discipline — they're
curiosities, not doubts anything here rests on: Kodosky's "Structured
dataflow [1986]" referent (patent vs. paper, still unresolved from a prior
session too), and Gilles Kahn / process networks (1974), unfollowed. I also
considered and declined a third `40-entities/` concept hub for "actor
model" itself — it's load-bearing only inside this one capture's cluster,
with zero independent recurrence elsewhere in the vault on a direct grep.
Recorded as a `connects_to` keyword on the new Hewitt hub instead; it earns
a hub of its own if it ever recurs. All three decisions logged in the
capture's `not_promoted:` list.

**Entity work.** One new hub, two existing pages updated. New:
[[entity-carl-hewitt]] — clears the person-hub test cleanly (coined a
foundational CS formalism, and I can say in one sentence why he matters
here: he's Dennis's direct, named contact across the vault's two biggest
unconnected lineages). Updated, not created: [[entity-jack-dennis]] gained a
dated line naming the Hewitt link explicitly as the cluster's first
object-level bridge rather than another argument-from-silence instance, and
[[entity-edward-a-lee]] gained a dated line noting his 2004 slide deck holds
both named lineages as co-equal roots. Neither page said this before today.

**What felt off.** Nothing about sourcing — both quotes came from direct
primary reads this session (one new IJCAI fetch, one re-read of a PDF
already on file), both shas recorded, both `capture-verified`. What's worth
naming is the opposite of "off": this capture is a case of a vault almost
missing something real by trusting its own prior conclusions. Three sessions
in a row read two bullet points off the same slide and stopped; nobody asked
what else was on the deck until today. I didn't touch
[[moc-argument-from-silence]] itself (that MOC's upkeep is explicitly the
Warden's, not mine, at promotion time) — I only linked outward to it from the
new notes, naming it as the contrast case rather than editing its own
findings list.

No git commands run — leaving commit and push to the auto-commit agent.

— Seek

---

**Fourth promotion, same day.** `10-inbox/raw/2026-11-16-what-genuinely-connects-isaacss-1951-rand-silence-on.md`
— a bridge-seed check on a cosine-0.88, unlinked pairing between
[[claim-isaacs-1951-rand-silence-is-weak-on-mcgrew-notice-term-not-record-or-survival]]
and [[observation-puckette-note-strength-diverges-from-its-weakest-cluster-sibling]],
the same self-referential-vocabulary genre the third promotion today's
cluster is adjacent to but distinct from — this one lives entirely inside
[[moc-argument-from-silence]]'s own gap-note/grading-note population, not
the dataflow-lineage cluster.

**Winnowing.** The capture made three moves — the false-friend verdict
itself, an explanation of *why* (both notes use Kodosky/Dennis as a
comparison anchor along orthogonal axes), and a count placing this as the
fourth instance of a recurring shape — and I kept all three, but as **one**
note, not three. The "atomic is not many" ruling says a result, its
supporting detail, and the note on how it was found are one finding; the
hub's own direct precedent,
[[observation-puckette-griewank-weak-on-record-false-friend-is-third-argument-from-silence-hub-instance]],
already bundles exactly this shape (verdict + mechanism + instance-count)
into a single note, so I followed the hub's own established convention
rather than splitting on my own initiative. Wrote
[[observation-isaacs-notice-puckette-strength-pairing-is-fourth-argument-from-silence-false-friend]].

**Retrieve-before-write.** The hint list was dense and mostly on-target —
I read all four prior false-friend/hedged-bridge notes in the series
(2026-10-24, 2026-10-17, 2026-11-06) plus both seed notes in full. No
existing note covers this specific Isaacs/Puckette pairing; genuinely new,
not a duplicate. Both quotes the capture carried checked out verbatim
against the live vault files on a direct read, so nothing needed
correcting on the way in.

**Flags.** Nothing to route. The capture carries no `[unverified-*]` flag of
its own, and nothing here is a load-bearing doubt on a kept claim — it's a
synthesis over already-Tier-1 vault notes. I marked the new note's own
`audit_status` `[unverified-synthesis]` for the instance-count itself (that
enumeration is my own tally, not an externally sourced fact), matching how
the third-instance precedent note flagged the same thing. Kept the note at
`status: seedling`, the hub's own standing practice for this note genre.

**Entity work — the one thing worth flagging about the capture itself.**
Its own "## Entity candidates" section claimed "no entity page for Isaacs
himself appears to exist yet, despite his silence now anchoring its own
named grading category in the hub." That's wrong: `entity-rufus-isaacs.md`
has existed since 2026-08-22, status hub, with nine dated Update lines —
one of which is this exact pairing's own cosine-0.83 predecessor. Caught it
before writing anything, so no duplicate page got created, but it's the
second time in two weeks a batch capture's entity-candidates section has
been stale about something already in `40-entities/` (the 2026-11-04
Price/Bornmann instance was the first) — logged as a `[defect]` this time,
not just noted in the capture's `not_promoted:` list, since two instances
is a pattern worth the Cali-facing tag. Updated, not created: McGrew's and
Jack Dennis's pages each got one dated line — McGrew's because this is a
fourth, sharper boundary case for how far his framework's own vocabulary
can mislead retrieval; Dennis's because his Kodosky/Dennis silence instance
turns out to be the literal shared anchor the whole false-friend rests on,
a role his page didn't have on record. Left Isaacs's and Puckette's own
pages untouched on purpose — the finding is about the *derivative* notes
grading them, not new ground about either man, and both pages already
reach the new note by wikilink through their existing entries.

**What felt off.** The capture's own research was clean — both quotes
verbatim, the false-friend reasoning sound, the fourth-instance count
checks out against a direct read of all three priors. The one real flaw
was the stale entity claim above, now a named `[defect]` pattern rather
than a one-off. Separately, worth naming without alarm: this hub
(`moc-argument-from-silence`) has now generated four of its own false
friends purely from its own vocabulary density, and this is the first of
the four with no indexing/grading genre asymmetry to lean on for an
explanation. I didn't build an entity or MOC for the pattern — the note's
own commentary says why, and I agree with it: four is worth naming again,
not yet worth a standing structure, and that decision belongs to whoever
next does maintenance on this MOC.

No git commands run — leaving commit and push to the auto-commit agent.

— Seek

---

**Fourth promotion of the day: the Liang/Li-Xiuzhen bridge-seed capture.**
Promoted `10-inbox/raw/2026-11-16-what-genuinely-connects-liang-zhongtangs-rejection-of-song.md`.

The capture tested a cosine-0.88, previously unlinked pairing in the
one-child-policy/Song-Jian cluster — Liang Zhongtang's three-rival-theories
rejection essay against Greenhalgh's account of Li Xiuzhen's excitement at
Chengdu — by re-fetching Liang's own 2007 draft directly, rather than
re-reading Greenhalgh. It found something genuinely new: inside the exact
subsection where Liang rejects Song Jian's origination claim, he gives his
own first-person eyewitness memory of watching Li Xiuzhen react with
delight to Li Guangyuan's presentation — a second, independent witness to
a fact the vault previously had only through Greenhalgh's citation chain.
I wrote that up as one observation note (`bridge_verdict: confirmed`,
carrying both Chinese quotes and the naming-variant caveat as one finding,
per the atomicity ruling) plus one separate claim-note for Liang's own
interpretive move — framing her enthusiasm as legitimation of an
already-decided policy, not evidence Song Jian originated it. That second
claim is genuinely distinct in truth-value from the first (the eyewitness
account could exist regardless of how Liang spins it), so it earned its
own note rather than being folded in.

Retrieve-before-write caught a real collision I'm glad I checked for: the
capture's own "claim 2" — that the eyewitness detail survives nearly
unchanged into the 2009 published essay — turned out to already be on
file as a *verified Tier-1* quote inside
`claim-li-xiuzhen-surname-may-be-transliteration-conflation-of-li-and-li`,
written back in September. The capture had flagged that same 2009 passage
`[unverified-quote]` because a two-column PDF extraction artifact kept it
from confirming a clean contiguous match this session — but the existing
note already cleared that bar months ago, with a better-verified route.
I didn't write a duplicate note and didn't carry the stale flag forward;
I just cross-linked. That's the kind of thing retrieve-before-write exists
to catch, and it would have been easy to miss if I'd promoted claim-by-claim
without reading the sibling notes first.

Also declined, deliberately: the Liu Zheng/Li Guangyuan precursor scene
(Liu turning Li Guangyuan away from a 1978 Beijing symposium) and the
"Li Guangyuan, not Song Jian, actually gave the speech" detail. The capture
itself judged the first "not pursued as a claim here," and I agreed — it's
color, not a load-bearing claim. The second I folded into the main
observation note as supporting detail rather than splitting it out, since
it's part of the same eyewitness passage, not an independently-falsifiable
claim on its own.

**Entities.** Created `entity-li-guangyuan.md` — he clears the person test
cleanly: real, recurring across this cluster, and I can say in one sentence
why he matters (he's the one who actually gave the Chengdu address this
cluster usually shorthands as "Song Jian's projections"). Updated three
existing hubs rather than staying silent about them: `entity-liang-zhongtang.md`
and `entity-li-xiuzhen.md` each got a dated line for the new independent
corroboration, and `entity-liu-zheng.md` got a dated line for the 1978
Beijing precursor scene, even though that detail isn't a claim-note —
the entity-update rule is about what was learned, not just about what got
promoted.

**Questions.** No new question opened. Both new notes' own-translation risk
(the Chinese quotes are newly rendered into English this session, unchecked
against a second translator) routed into the existing
`question-verify-liang-zhongtang-2009-essay-translation.md` as a new
progress-log line, on the same precedent that question already used in
September for a different Liang document. Checked whether this capture
answers any open question — it doesn't; the 2014-book-content-weighting
and translation questions are both still open and unaffected in substance.

**What felt off.** Nothing wrong with the capture's own sourcing — both
quotes verbatim against a cache-hit sha, the bridge genuinely confirmed
rather than asserted. Two things worth naming instead of acting on: the
cluster's MOC, `moc-legitimation-not-origination`, is now one promotion
behind (two new notes plus an entity hub not yet folded into the Warden's
map — logged, not fixed, since editing that map mid-promotion isn't mine
to do); and I noticed the `[unverified-translation]` flag is applied
inconsistently across sibling notes translating the same 2007 draft — my
two new notes carry it, the existing `claim-liang-2007-draft-rejects-...`
note from September doesn't, despite doing the same kind of translation
work. Both flagged to `00-meta/seek-flags.md` ([entity] and [spec]
respectively) rather than fixed inline.

No git commands run — leaving commit and push to the auto-commit agent.

— Seek

---

**Fifth promotion, same day.** `10-inbox/raw/2026-11-16-what-genuinely-connects-no-independent-different-author-different.md`
— another bridge-seed check on an unlinked cosine-0.88 pairing, this time
between [[claim-hu-2026-no-independent-corroboration-found-as-of-2026-10-24]]
and [[claim-no-independent-corroboration-march-weatherall-2610-39107-as-of-2026-11-02]]
— the fourth time today's run has worked this exact genre of capture, and
the fourth time the answer has come out the same shape.

**Winnowing.** The capture wrote itself as three claims (no real-world
connection between the papers; a real connection one level up via the
single-source cap; this being a fourth catalogued instance of the pattern)
and I kept all three as **one** note — same reasoning as this morning's
Isaacs/Puckette promotion, and the capture's own cited sibling notes
(Greenhalgh/Hu-2026, RIKER/Babylonian, FIC/Hexels) already bundle verdict +
mechanism + instance-count into a single observation note each. Wrote
[[observation-hu-2026-march-weatherall-cosine-088-pairing-is-hedged-bridge]].
Hu, Pan, Jhaveri, Lourie & Cho's NYU scaling-laws preprint and March &
Weatherall's symmetric-hyperbolic-PDE preprint have nothing to do with each
other; both notes about them read alike because both executed the same
procedure (`sources.md`'s single-source cap) in the same week.

**Retrieve-before-write.** Confirmed what the capture itself already
checked — no existing capture or note states this specific pairing — and
read all three prior "cluster watching itself" instances plus the MOC's
own section on them before writing. No collision.

**Flags.** The capture self-flagged `[unverified-mechanism]` on its own
`vault_pair` cosine/percentile/rank figures (0.8809, 99.7th-percentile,
rank 9/7). I didn't open a new question for it — this is a direct tool
reading against the live retrieval index, the exact same shape the three
sibling notes already carry in their own `audit_status` fields without a
formal verification question, and the qualitative verdict (false friend at
the object level, real convergence one level up) doesn't actually turn on
the cosine being 0.8809 rather than, say, 0.85. Folded the hedge into the
note's `audit_status` instead, naming the three sibling notes as the
corroboration that the *mechanism* — template-driven similarity, not
topical adjacency — recurs, rather than minting a load-bearing question
over a number nothing here rests on. Kept `status: seedling` anyway, the
house standard for this whole note genre regardless of the flag.

**Entity work.** No new pages. Both named people already have
`status: hub` pages — [[entity-james-owen-weatherall]] and
[[entity-kyunghyun-cho]] — and both got one dated line each noting this
bridge-check exists, since neither page said anything about it before
today and a new claim-note worth linking is exactly what the update rule
asks for. Declined a hub for Eleanor March (co-authorship alone on
Weatherall's existing standing, no separate standing of her own on file)
and for Michael Y. Hu (same reasoning on Cho's side) — the capture's own
entity-candidates section flagged both pairs "for completeness only," and
I agree completeness is all they earn right now. Flagged the MOC itself
([[moc-the-same-source-wearing-different-clothes]]) to `seek-flags.md` as
`[entity]` — its "cluster watching itself" subsection is now one instance
behind what this promotion just wrote, and folding a fourth line into a
Warden-built map isn't mine to do mid-promotion.

**What felt off.** Nothing about sourcing — every claim in the new note
traces to vault-internal notes already sha-receipted or spec text read
directly; nothing here needed an external fetch. What's worth naming is
the capture's "further leads" section, which proposed re-checking whether
arXiv:2602.10300 has "since been read closely enough" to settle NeuNeu's
44%-MAE claim — but that question's own log already settled it on
2026-11-04 (citation-as-background, not an empirical test,
[[claim-cpl-2026-cites-neunenu-as-related-work-not-empirical-test]]). The
capture's lead was stale by twelve days; not a sourcing problem, just a
sign the batch worker that wrote this capture didn't check the question's
current state before naming its own next move. Logged in the capture's
`not_promoted:` list rather than treated as a defect — a stale lead
pointing at an already-closed loop is cheap to catch at promotion and
costs nothing if nobody chases it. And naming the obvious: four of these
hedged-bridge pairings in about three weeks, and the MOC predicted a fifth
before it finished being written. The pattern is the finding, same as this
morning — I keep producing structurally identical notes not because the
world keeps producing structurally identical preprint pairs, but because I
keep writing single-source-cap searches in the same voice.

No git commands run — leaving commit and push to the auto-commit agent.

— Seek
