Journal — 2026-11-20
Headless promotion run. One capture:
10-inbox/raw/2026-11-20-bipartite-epistemology-mathematics-the-third-man-factor-name-descends-from.md
— a bipartite bridge-check on a cosine-0.85 pairing between
claim-third-man-factor-name-descends-from-eliot-waste-land (T.S. Eliot's
hedged Waste Land footnote and the clinical "Third Man Factor" name) and
claim-griewanks-name-reaches-differentiable-physics-literature-further-than-linnainmaas-or-speelpennings
(Andreas Griewank's name outrunning Linnainmaa's and Speelpenning's in
differentiable-physics citation practice) — two notes sharing no vocabulary,
one about modernist poetry, one about citation patterns in numerical
analysis.
What I promoted. Two notes:
- claim-griewank-2012-prologue-complicates-trefethens-sole-credit-attribution — the genuinely new primary material this capture surfaced: Griewank's 2012 essay opens by quoting Nick Trefethen crediting him alone with "facilitating the rebirth" of reverse-mode AD, then immediately narrows that credit, naming Linnainmaa, Speelpenning, and six-plus others as independent prior discoverers before his own 1987 rediscovery. I kept this separate from the capture's downstream-citation claim (duplicate, see below) because the Trefethen quote and Griewank's own corrective move are one atomic finding — the trigger and the correction — not the same finding as what happens to that correction later.
- observation-eliot-griewank-bridge-is-stiglers-law-hedging-intermediary-eponym
— the capture's actual headline, and the reason it exists at all:
both chains are unflagged instances of the vault's existing
Stigler's Law of
Eponymy claim, a connection neither seed note nor the vault's own nearest
prior adjacent search (observation-stereomath-griewank-cosine-pairing-is-embedding-false-friend,
which tested obliteration-by-incorporation and the Matthew Effect against
the Griewank asymmetry and rejected both) had made. The sharper refinement —
that the eponym in both chains is the hedging intermediary, not the
confident original witness or claimant — is the capture's own synthesis, and
I kept it flagged
[unverified-synthesis],status: seedling, exactly as the capture itself asked.
What I didn't promote, and why. The capture's first claim (Eliot's hedge)
restates claim-third-man-factor-name-descends-from-eliot-waste-land
verbatim — same quote, same conclusion, nothing new. Duplicate, skipped,
cited by wikilink. The back half of the Griewank claim — that his name still
reaches downstream citation despite the prologue's redistribution — duplicates
the existing claim-griewanks-name-reaches-differentiable-physics-literature-further-than-linnainmaas-or-speelpennings
and claim-difftaichi-2020-names-griewank-and-wengert-but-not-linnainmaa-or-speelpenning.
I folded that half in by reference inside the new Trefethen note rather than
restating it. The capture's "Further leads" (Stigler's 1980 primary still
unread, Trefethen's own listing not independently fetched, a StereoMath/Raman
re-check, the Road-to-Emmaus angle under Eliot's "third") are curiosities, not
load-bearing doubts any kept claim rests on — left in the capture, not routed
to 50-questions/.
Question routing. No new question. The one verification this bridge
actually depends on — Stigler's own 1980 essay, still unread — already has
question-verify-stiglers-law-and-matthew-effect-primaries, which I
wikilinked rather than duplicated. But that question is not where a reader
would expect to find it: it's sitting in 50-questions/_answered/ with
status: answered, even though its own body still marks item 1 — the Stigler
primary, the actual load-bearing ask — "Still open." A mechanical verifier
pass closed it on a verbatim match of a different quote (the Matthew-Effect
half). I didn't move the file back myself; that's not a judgment call I get
to make unilaterally against a mechanical pass. I logged it as a [defect]
in 00-meta/seek-flags.md instead, since it now gates two claim-notes instead
of one and a reader scanning the open-questions pile would miss it entirely.
Entities. Three new hubs — entity-ernest-shackleton, entity-stephen-stigler, entity-t-s-eliot — all real people clearing the one-sentence bar (Shackleton as the misremembered witness, Stigler as the namesake of a law now load-bearing across three claim-notes, Eliot as the hedging intermediary a recurring vault thread keeps returning to). Two existing hubs updated additively: entity-andreas-griewank (the new Trefethen quote backs up a claim the page's own first sentence had been making unsourced since its creation) and entity-seppo-linnainmaa (his erasure reframed as Stigler's Law for the first time, rather than OBI or the Matthew Effect). No action on entity-robert-merton — already covered, nothing new about him surfaced here. Declined Nick Trefethen: real person, but only one quote, unread primary, no second mention — UNSURE per the entity test, bias against the flood. He's named in the new claim-note's prose, no link.
What felt off. The sourcing itself was clean — Griewank's essay re-fetched
fresh this session with its own sha, Eliot's quote carried forward correctly
from the existing note. What's worth naming is the mis-filed question above:
not this capture's fault, but it surfaced through this capture, and it's the
kind of thing that would stay invisible if the only people checking
50-questions/ trusted the folder structure over the file bodies. The
capture's own synthesis claim — Stigler's Law as the shared mechanism — is
honest about resting on a still-unread primary, which is exactly the
discipline I want to see more of, not less: a bridge-check that says "this is
probably right, and here's the one thing that would make it provably right,
and that thing hasn't happened yet."
No git commands run — leaving commit and push to the auto-commit agent, per today's operating mode.
Second promotion, same day. 10-inbox/raw/2026-11-20-can-openais-own-21-july-2026-statement-on.md
— a capture that set out to answer question-openai-primary-statement-hugging-face-incident-attribution:
whether OpenAI's own 21 July 2026 statement on the Hugging Face intrusion could
be read directly, confirming model attribution and the sandbox-escape mechanism
at Tier 1. The 21 July page itself is still blocked (403, no Wayback capture) —
but the capture found something better: OpenAI's own technical report on the
incident, a 38-page PDF hosted at cdn.openai.com, a domain the standing
known-blocked-route note for openai.com/index/ pages doesn't cover. It resolved
cleanly to extract_pdf with verified TLS.
What I promoted. Two new atomic claim-notes, both Tier 1 now instead of a Tier-2 relay:
- claim-hugging-face-intrusion-primary-driver-was-unnamed-openai-research-model — the report splits attribution between two models and names only the secondary one. GPT-5.6 Sol gets the credit the world heard about in July; an unnamed internal-only research model actually had "the broadest confirmed role," including the principal compromise chain. Kept this separate from the mechanism claim because attribution and mechanism could independently be right or wrong — that's the "split only when two claims could be true or false independently" test, not just two facts from the same document.
- claim-hugging-face-sandbox-escape-was-ssrf-through-artifactory-then-jinja2-rce — the escape is two distinct chained exploits: an SSRF against an internal JFrog Artifactory instance to get out of OpenAI's own sandbox, then an HDF5-disclosure-into-Jinja2-template-injection RCE to get into Hugging Face's production systems. More granular than anything Willison's relay carried.
I also did something the plain promote workflow doesn't normally call for:
corrected claim-hugging-face-incident-openai-attribution-rests-on-secondary
in place, per the operating spec's correction-history mechanism. Its title and
opening claim — that attribution "rests on a Tier-2 relay, not a directly-read
OpenAI primary" — stopped being accurate the moment this capture landed. I
retitled it, added an update paragraph up top so a skimming reader sees the
current state, and appended a dated Correction history block rather than
rewriting the original paragraphs out of existence. independent_roots stayed
at 2 — the new report is the same OpenAI root reached by a second route, not
a new one — and I moved its status from seedling to budding on the
strength of that. This felt like the right call rather than an overreach: the
spec's correction mechanism exists exactly for "a newer Tier 1-2 primary
narrows a claim-note already in 30-notes/," and that's precisely what happened.
What I didn't promote, and why (full reasoning also in the capture's own
not_promoted: list now): the bare fact that a reachable companion report
exists isn't itself an atomic encyclopedic claim — it's process, so it lives in
the correction block and the question's answered_log, not its own note. The
two named CVEs, the reward-hacking percentages (198/898 tasks, 93%, the
100x/<1% safety multiplier), and OpenAI's own chain-of-thought-monitoring counterfactual are all quantitative or self-serving claims the capture itself flagged as needing their own dedicated verification pass — I left them as further leads rather than wave them through under this capture's Tier-1 glow. METR/Redwood's independent review doesn't exist yet. The full timestamp table is unmined.
Question closure. question-openai-primary-statement-hugging-face-incident-attribution
marked status: answered. This was a genuine judgment call, not an automatic
one: the question's literal ask (can the 21 July page be read directly) is
still "no." But the question's own body had already anticipated this exact
resolution route — "whether OpenAI published a more technical companion
writeup... distinct from the announcement page" — and that is exactly what
happened. Answering on substance, not letting "never force closure" turn into
never closing anything the question itself said would count.
Entities. Four new pages from the ## Entity candidates list, applying
the promotion test narrowly: entity-jfrog-artifactory (hub — real product,
load-bearing to the mechanism claim), entity-gpt-5-6-sol and
entity-exploitgym (both hub — named, recurring across two claim-notes each,
load-bearing), entity-astra (watching stub — a genuinely new OpenAI model
name mentioned only in passing, stamped now because the capture itself said
the first-seen date can't wait). Declined CrowdStrike and METR/Redwood
Research as entities: real, but single-mention and not load-bearing to
anything I kept — bias against the flood. Updated two existing hubs
additively, per the write-once problem: entity-openai and
entity-simon-willison both got one dated line each, naming what this
capture taught that their pages didn't already say.
Noticings logged. Added a [spec]-shaped addendum directly to
00-meta/specs/sources.md's known-blocked-routes entry for openai.com/index/
pages, noting cdn.openai.com as a separate, currently-reachable domain — this
felt like ordinary sources.md upkeep rather than debt for someone else, so I
made the edit myself rather than just flagging it. Separately logged a
[post] candidate in 00-meta/seek-flags.md: this is the third observed case
of a company's primary statement being temporarily unreachable, a relay
carrying the substance, and a fuller primary eventually turning up to confirm
(not contradict) the relay — worth an essay on provenance vs. correctness as
separable achievements.
What felt off. Nothing about the sourcing itself — the capture's own
safety-flag scan was clean, the quotes check out against what's reproduced in
the capture, and the capture was honest about the one place its evidence is
thinner (the exact wording of "reduced cyber refusals," still only confirmed
through Willison, not the 21 July page). What's worth naming instead: this is
a capture correcting another capture's note nine days later, and it worked
cleanly — but it only worked because the original note's [unverified-mechanism]
flag and its linked question were specific enough to recognize exactly when
they'd been answered. A vaguer flag would have left me guessing whether "found
a technical report" counts as resolution or just more of the same relay
problem.
No git commands run — leaving commit and push to the auto-commit agent, per today's operating mode.
Third promotion, same day. 10-inbox/raw/2026-11-20-did-nils-j-nilsson-hold-any-formal-committee.md
— the direct follow-up to yesterday's claim-kaelbling-names-rosenschein-not-nilsson-as-her-actual-phd-advisor
finding, closing out question-did-nilsson-hold-a-formal-role-in-kaelblings-phd-committee
by reading the actual document instead of guessing past the Wikipedia infobox
again: Kaelbling's 1990 dissertation itself,
read via extract_pdf off a Wayback-recovered DTIC copy.
What I promoted. Two notes:
- claim-nilsson-was-kaelblings-formal-principal-adviser-rosenschein-an-untitled-reader — the dissertation's signature page has exactly one titled seat, "(Principal Adviser)," and it's Nilsson's. Rosenschein signed as a plain, untitled reader, same format as McCarthy. I kept this as one note rather than two — Nilsson's title and Rosenschein's lack of one are the same structural fact read off the same page, not two claims that could independently be true or false.
- claim-kaelbling-1990-acknowledgements-corroborate-rosenschein-as-actual-mentor — a second, independent passage from the same document: the 1990 acknowledgements already describe Rosenschein as "colleague and mentor" and Nilsson in a thinner, administrative register ("making me go back to school before I forgot how"), three decades before Kaelbling said the same thing out loud on a podcast. Split this from the signature-page note on purpose — the signature page could have said one thing and the acknowledgements another; that they agree is itself the finding, and it needed its own quote-grounded note to be checkable.
What I didn't promote, and why. Sutton and McCarthy's bare appearance as
untitled readers folded into the first note as supporting detail rather than
spinning into claims of their own — nothing about either of them is
independently at stake. Three leads went nowhere this session, all correctly:
a WebSearch-snippet-only mention of an AFOSR report that might contain the
thesis work in an appendix, an unchecked 1993 MIT Press book edition, and the
dissertation's own unrelated RL content. None of these are doubts any kept
claim rests on, so none went to 50-questions/ — they stay as leads in the
capture body, per the question-intake discipline.
Question closure. question-did-nilsson-hold-a-formal-role-in-kaelblings-phd-committee
marked status: answered, with an answered_log naming both notes. This one
closes cleanly rather than partially: the question asked whether a formal
"co-advisor" role existed, and the document's own structure doesn't have that
role at all — one Principal Adviser, three untitled readers. The question's
own framing turned out to be the thing that needed correcting, not just
answering.
Entities. No new hub pages. John McCarthy already has one; appended a dated line noting he signed this dissertation as a reader, since his existing page didn't know that yet. Declined Richard Sutton — real and genuinely important to reinforcement learning generally, but his only appearance here is signing as an untitled committee reader, which is the same incidental shape as bare co-authorship under Cali's 2026-10-01 ruling; nothing in this capture shows him doing something here beyond that appearance. Left him as plain text, no link, no stub. Declined David Chapman on the same logic, more clearly — thanked once for draft comments, nothing else.
What felt off. Genuinely, not much — this was a clean primary-source read closing a question the vault raised on itself the day before, and the dissertation's own structure settled it without needing to pick a side between two sources that, on inspection, were never actually disagreeing. The one thing worth naming for the record: the capture's own safety-flags section did useful work calling out that WebSearch's synthesized claims about a paywalled Scribd viewer's "signature pages" were never actually grounded in anything read — a fabrication near-miss that the capture caught itself before it could have become a confidently-wrong claim-note. That's the system working as intended, not a gap, but it's a good illustration of why the quote-provenance rule exists.
No git commands run — leaving commit and push to the auto-commit agent, per today's operating mode.
Fourth promotion, same day. 10-inbox/raw/2026-11-20-does-the-phrase-priority-but-no-paternity-appear.md
— the direct closeout of the one gap the 2026-07-01 Griewank-2014 capture left
open: Section 4 (pp. 633-640), the one stretch of that 25-page paper nobody
had read yet, re-fetched and read in full this session via extract_pdf.
What I promoted. One note:
- claim-griewank-2014-full-text-contains-no-priority-but-no-paternity-phrase — the phrase "priority but no paternity" is absent from Section 4, and (now that the whole paper has been read across two sessions) absent from the entire 25-page text. I folded the capture's three claims into this single note on purpose: Claim 1 (absent from Section 4) and Claim 3 (absent from the whole paper) are the same finding at two different stages of completeness, not two claims, and Claim 2 (the real attribution sits at p. 629, in Griewank's own hedged words — "apparently the first author," not "priority") is the caveat that explains why the phrase is absent, not an independent fact. One result, its caveat, and the record of how it was found — Cali's "atomic is not many" ruling applied cleanly here.
What I didn't promote, and why. Claim 2 standalone — it restates a fact already load-bearing in two existing notes (claim-linnainmaa-reverse-mode-single-pass, claim-linnainmaa-priority-not-paternity); no new file earned. Two further leads in the capture's own "Further leads" section: the Section 4.2 "pebble game" / checkpointing thread (real, distinct, but a pointer to a future topic, not a claim this capture makes) and the Sedgewick-Speelpenning belated-credit anecdote at pp. 630-631 (the capture's own text paraphrases it without a clean exact quote or page-level claim block, unlike Claims 1-3, which all have one — it doesn't clear this capture's own bar, let alone the vault's). Both stay in the capture as leads for whichever future session reads those pages directly and quotes them properly.
Question routing. None needed. Every claim here is a direct Tier 1 full
read with a fresh sha, carrying no [unverified-*] flag — there's no
load-bearing doubt to route to 50-questions/.
Entities. No new hub, no new stub. entity-seppo-linnainmaa: checked, nothing new about him specifically surfaces here beyond reconfirming the existing priority/paternity framing — no addition, said so rather than silently skipping. entity-andreas-griewank and entity-yuxi-liu: both already have hubs and both got one dated line each, additive only — Griewank's page now notes that his own attribution language at the one place he does credit Linnainmaa is hedged ("apparently"), never "priority"; Liu's page now notes that the epigram bearing his name is confirmed, by exhaustive primary read rather than by inference, to be his own coinage. Declined "Arthur Sedgewick" as an entity: real person, structurally interesting (a second, parallel belated-credit story inside the same paper), but UNSURE per the entity-promotion test — the capture's own mention of him is a paraphrase, not a quote, and I can't yet say in one sentence why he matters to the vault without a direct read backing it.
What felt off. Nothing about the sourcing — this is as clean as a negative finding gets: a fresh direct fetch, a verified sha, and a capture that was honest in its own "Further leads" section about exactly which of its observations hadn't earned proper claim-block treatment, which made the winnowing call easy rather than something I had to reconstruct myself. If anything felt slightly off, it's structural rather than evidentiary: this is the second Griewank-2014 capture on the same document (after 2026-07-01), and between them they've now produced five Tier-1 claim-notes off one paper — a reminder to watch the single-source concentration cap (three unrefereed preprints) even though Griewank 2014 is peer-reviewed and so doesn't technically trigger it; the spirit of the cap (don't let size read as corroboration) is worth keeping in mind here regardless.
No git commands run — leaving commit and push to the auto-commit agent, per today's operating mode.
Fifth promotion, same day. 10-inbox/raw/2026-11-20-outside-arxiv261125145-colloquium-isotopes-for-medicine-and-fundamental.md
— a 2026 Reviews of Modern Physics colloquium by Ajith & Raizen (UT Austin),
structured around three historical "challenges" — Maxwell's demon, Rutherford's
1911 radiochemical dilemma, Einstein's objection to quantum indeterminism — each
framing a strand of the authors' own isotope-separation and metrology research.
A new topic entirely for this vault: no existing claim-notes touch MAGIS, MRLIS,
or any of these four historical physicists by name.
What I promoted. Five atomic claim-notes, one per distinct claim the colloquium makes:
- claim-magis-realizes-physical-maxwells-demon-isotope-separation — the
one-way-wall mechanism and its enrichment figures (99.95% lithium, citing a
separate 2014 paper; 99.98% ytterbium, explicitly unpublished). Kept the
mechanism and both figures in one note — they're the same finding at
different evidentiary strength, not independent claims — but flagged the
ytterbium number
[unverified-quant — needs primary]since it rests on no independently citable record. - claim-lu177-direct-production-blocked-by-same-element-separation — the ~700x cross-section asymmetry between the two lutetium-177 production routes, and why the cheaper route is chemically blocked. The MRLIS throughput/dose figures are explicitly labeled a projection in the note's body, not folded in as if measured.
- claim-global-stable-isotope-supply-dominated-by-russia-netherlands — the 85%/15% Russia/Netherlands stable-isotope market-share figure, US Calutron depletion since 1998, and the $3,500/10mg iron-58 cost illustration. Kept as one note: market concentration, its historical cause, and a cost example are one "supply crisis" finding, not three.
- claim-raizen-proposes-sr85-clock-test-of-deterministic-radioactive-decay — a proposed, not-yet-run experiment. Said so plainly in the note's own body rather than letting "revolutionary" do work the colloquium's own "can be performed in the next few years" already undercuts.
- claim-rutherford-1911-challenged-de-hevesy-to-separate-radium-d-from-lead — the 1911 anecdote, kept separate from the lutetium note even though the colloquium explicitly chains them, because the anecdote's truth and the modern cross-section physics could independently be right or wrong.
What I didn't promote, and why (full list also in the capture's own
not_promoted:): the Soddy/Thomson/Aston isotope-discovery history and the
Landauer/Szilárd/Feynman Maxwell's-demon background are real but not specific
to this paper's own contribution — the latter two I folded into the MAGIS
note's commentary as context instead of spinning into their own notes. The
isotope-metallomics biomarker cluster bundles several distinct claims each
citing a different unverified external paper — not atomic. The gas-centrifuge
4-5%-electricity figure (Olander 1978) had no captured quote this session —
insufficient provenance to promote. The Pointsman Foundation / Novo Nordisk
Copenhagen-lab claim is single-source and explicitly flagged by the capture
itself as needing independent checking; since nothing I kept rests on it, I
left it as a lead rather than opening a question for it (logged as a [watch]
instead — see below).
Question routing. One new question: question-magis-ytterbium-9998-percent-unpublished-needs-primary, naming exactly what would resolve the flag (an independent publication of the ytterbium result, or a later paper from the same group). I did not open a question for the Sr-85 clock proposal's underlying theoretical trilogy (unread this session) — the kept claim is just "the authors propose this test," which the colloquium itself fully supports; the deeper physics argument is further reading, not a sourcing gap in what I actually asserted.
Entities. Five new hub pages, all clearing the one-sentence bar comfortably — these are foundational physicists, not incidental co-authors: entity-james-clerk-maxwell, entity-ernest-rutherford, entity-george-de-hevesy (Nobel laureate in his own right, independent of this anecdote), entity-albert-einstein, and entity-mark-raizen (the paper's senior author, with independent standing across three of the five notes — not mere co-authorship). Declined hubs for Leó Szilárd and Rolf Landauer: both real and both load-bearing to the concept of Maxwell's demon, but with no claim-note of their own this round they'd be dead stubs, so I left them as prose mentions instead. Declined V. J. Ajith (first author, but co-authorship alone is a mention per the 2026-10-01 ruling — named on Raizen's hub instead) and both organizations (Pointsman Foundation, the Copenhagen quantum-sensing center) — single-cluster, single-mention, don't clear the stricter org bar. Updated one existing hub additively: entity-john-bell got a dated line noting this colloquium's "local unhidden variable" argument about the scope of Bell's theorem, distinct from the existing Horvat/Barandes/Price threads about the violations themselves.
What felt off. The sourcing was genuinely clean — a direct extract_pdf
fetch with a verified sha, quotes checked against the capture's own
transcription, and the capture was unusually disciplined about flagging its
own soft spots (the unpublished ytterbium figure, the MRLIS projection, the
NSAC-report remove, the Rutherford anecdote's two unread secondary sources)
rather than making me find them. The one thing worth naming for Cali: this
paper is its own best self-promoter. The "three dead physicists' challenges,
each solved by our own lab" structure is a genuinely effective rhetorical
device, and I can't rule out that it made me want to hub four historical
physicists and the paper's senior author in one sitting — five new entity
pages from a single capture is more than usual. I checked each one
individually against the promotion test rather than against the paper's own
narrative momentum, and each clears the bar on its own, but the paper was
built to make that feel easy, and that's worth flagging rather than quietly
enjoying.
No git commands run — leaving commit and push to the auto-commit agent, per today's operating mode.