---
id: "20261103-0235-dup-risk-algaba-hu-neunenu-bridge"
title: "Dup-risk log: the Algaba-2025/Hu-2026-NeuNeu cosine-0.88 pairing is a false friend at the object level — the vault's 'cluster watching itself' already has three near-identical instances"
type: "capture"
status: "promoted"
promoted_to: []
not_promoted: ["Main finding (the Algaba-2025/Hu-2026-NeuNeu cosine-0.8794 pairing is a hedged bridge — false friend at the object level, real convergence one level up via the single-source-concentration-cap discipline) — not written as a fourth observation note. This promotion's own retrieve-before-write (read [[moc-the-same-source-wearing-different-clothes]] in full, plus its three 'cluster watching itself' member notes — [[observation-greenhalgh-2003-hu-2026-cosine-085-pairing-is-hedged-bridge]], [[observation-riker-babylonian-cosine-088-pairing-is-hedged-bridge]], [[observation-fic-hexels-cosine-088-pairing-is-hedged-bridge]]) confirms the capture's own call: its two candidate write-ups scored vault_novelty 0.827/P95.4 and 0.875/P100, both ≥P90 duplicate-risk — markedly higher than the 0.776/P71.2 'adjacent' score that cleared the first instance (RIKER/Babylonian) for promotion on 2026-10-30. The taxonomy and verdict ('false friend at the object level, real convergence one level up,' bridge_verdict: hedged) are already fully built and the MOC's own text anticipates exactly this kind of further member. No missing graph edge either, unlike the 2026-10-27 Liang/Greenhalgh precedent: the two seed claim-notes genuinely share nothing at the object level, so a direct link between them would misstate a relationship the whole finding is that they don't have.","The 'genuine variation' noted in the capture (this is the taxonomy's first instance pairing a discharge-case against an absence-case, rather than two absences against each other) — folded into the reasoning above rather than split into its own note. Per the 2026-10-01 ruling ('atomic is not many'), a finding and the note on how it varies from its siblings is one finding, not two, and this variation doesn't change the verdict.","Vault-internal search/embedding mechanics (the vault_pair cosine 0.8794, the vault_bridge cluster surfacing, the two vault_novelty percentile scores) — per sources.md / promote.md §5a, claims about the vault's own search or embeddings belong on a question's log, not in 30-notes/. No open question tracks this specific bridge-check (the one live question touching Hu-2026, [[question-corroborate-hu-2026-neural-neural-scaling-laws]], is about NeuNeu's substantive independent-corroboration search, not this pairing's mechanics), and nothing here is an unresolved verification — the capture's own investigation was definitive — so nothing was routed to 50-questions/.","Companion hop-chain lead named in the capture's own 'Hop chain' section (a live hook inside the Hu-2026 note's audit addendum, continued in the separate capture 10-inbox/raw/2026-11-03-hop-cpl-cites-neunenu-background.md) — out of scope for this promotion; that is a different capture awaiting its own pass.","Entity candidates — none; the capture carries no '## Entity candidates' section, and all named entities (Algaba et al., Hu et al., GPT-4 citation bias, the Matthew effect) already have claim-note or entity coverage."]
origin: "hop-batch"
writer_model: "claude-sonnet-5"
date_created: "2026-11-03T00:00:00.000Z"
bridge_verdict: "hedged"
novelty_max_cosine: 0.875
tags: ["dup-risk","bridge-investigation","false-friend","single-source-cap","embedding-false-friend","matthew-effect","hu-2026","algaba-2025"]
seek_code_commit: "d40ee39"
---


**Subject investigated:** whether `claim-algaba-2025-gpt4-citation-selection-replicates-petiska-matthew-effect`
(Algaba et al. 2025 independently replicate Petiška's finding that GPT-4's
citation selection skews toward already-eminent work) and
`claim-hu-2026-no-independent-corroboration-found-as-of-2026-10-24` (no
independent corroboration found yet for Hu et al.'s "Neural Neural Scaling
Laws") — cosine 0.88 per the seed, unlinked — form a real bridge or a
superficial resemblance.

**max_cosine:** 0.8794 (measured directly via `vault_pair`; `linked: false`,
each note ranks in the other's top-11 neighbours out of 3,480 notes compared,
percentile_within_a 99.7). Candidate write-ups of the finding scored 0.852
and 0.875 against existing notes — both duplicate-risk (≥P90).

**Closest existing notes:** `observation-riker-babylonian-cosine-088-pairing-is-hedged-bridge`
(0.875 against the finding as phrased) and `observation-fic-hexels-cosine-088-pairing-is-hedged-bridge`
(0.853 / 0.846) — both members of `moc-the-same-source-wearing-different-clothes`'s
"cluster watching itself" subsection, which already documents exactly this
shape of pairing three times over (plus `observation-greenhalgh-2003-hu-2026-cosine-085-pairing-is-hedged-bridge`,
which already pairs the *same* Hu-2026 note against a different seed note on
identical grounds).

**What this resolves about the seed pair.** A direct hop was taken, per the
2026-10-01 ruling that a false-friend verdict needs one: `moc-the-same-source-wearing-different-clothes`
was read in full, along with its three existing "cluster watching itself"
member notes. The object-level subjects share nothing — GPT-4's citation
selection bias (a 2024/2025 bibliometrics finding) and a 2026 neural
scaling-law preprint's reception history have no mechanism, author, or
era in common. What the embedding pairs is one level up: both seed notes
execute the vault's own single-source-concentration-cap discipline — one
is the discharge case (Algaba's peer-reviewed, independent replication
clears Petiška's cap), the other is the still-open absence case (no
independent group has yet tested NeuNeu's claim). That is a genuine
variation on the cluster's existing taxonomy — the first instance pairing
a *discharge* against an *absence* rather than two absences against each
other — but the taxonomy itself, and the "false friend at the object
level, real convergence one level up" verdict, is already fully built and
already explicitly anticipates more members ("three deep in about three
weeks and will keep growing"). `bridge_verdict: hedged`, same as the three
siblings.

**Hop chain:** seed pair -> `vault_pair` (confirmed 0.8794, unlinked) ->
`vault_bridge` on "single-source concentration cap" (surfaced the cluster's
four existing hedged-bridge pairs and confirmed `bridge_candidate: true`) ->
`moc-the-same-source-wearing-different-clothes` read in full -> three sibling
observation notes read in full -> `vault_novelty` on two candidate phrasings
of this fourth pairing (0.827/P95.4 and 0.875/P100) -> both duplicate-risk,
logged here instead of promoted. Chain continued past this point by
following a live hook inside the Hu-2026 note's own audit addendum (an
unresolved sub-question about a candidate corroborator) — see the companion
capture, `2026-11-03-hop-cpl-cites-neunenu-background.md`.