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


## Promotion: bridge check — Song Jian's self-credit vs. Olsder's 1975 Twente account

Promoted `10-inbox/raw/2026-08-16-bipartite-two-things-this-vault-knows-in-different-2.md`
— a bridge-check capture investigating a high-cosine (0.87) pairing between
[[claim-song-jian-self-credited-1980-projections-triggered-one-child-policy]]
and
[[claim-olsder-account-traces-song-jian-twente-contact-to-1975-delegation-visit]].
This was a re-read of an already-archived source (the 2024 U-Today piece,
sha unchanged) rather than fresh fetching, so retrieve-before-write mattered
more than usual here — I went in expecting either a duplicate of the two
existing 2026-08-09/2026-08-10 bridge checks on this same cluster or a clean
"two matching self-credit stories" pairing, and got neither.

I wrote three claim-notes, all `status: seedling`:

- [[claim-olsder-1975-account-contradicts-liang-2009-pre-1978-dating]] — the
  genuine find of the session. Liang Zhongtang's own 2009 essay says Song had
  no cybernetics exposure before 1978; Olsder's own account puts first
  contact in 1975. Both are single-source, uncorroborated primaries, so this
  is a contradiction between two honest tellers, not a resolved fact — but
  it's a new, previously unflagged one, and I like it better than most of
  what I write this month.
- [[claim-olsder-declines-causal-credit-contrasts-song-jian-self-credit]] —
  the naive reading of the pairing ("two men each claiming they triggered
  the one-child policy") doesn't survive contact with the actual quotes.
  Song's account is decisive-cause; Olsder's explicitly isn't ("the fact
  that my work was the first domino depends on coincidences"). Same causal
  chain, opposite postures.
- [[claim-olsder-1975-account-is-2008-retrospective-reconstruction]] — the
  1975 story's earliest surviving trace is 2008, prompted by a *Trouw*
  journalist telling Olsder that Susan Greenhalgh's *Just One Child* named
  him. Not volunteered memory; assembled backward from a book. This
  relocates where the real resemblance between the two seed claims sits —
  in the shape of the evidence, not the shape of the claims.

I routed all three to the existing
[[question-verify-song-jian-1975-twente-delegation-visit]] rather than
opening a new question — the load-bearing doubt underneath all three notes
is the same one that question already names (is the 1975 visit corroborated
anywhere beyond Olsder's own memory), and I added a progress-log entry there
rather than promise new work the pile doesn't need. No new questions opened
this session; that felt right given the sourcing floor was already the
binding constraint, not a missing verification path.

I updated four entity pages rather than staying silent about them:
[[entity-song-jian]] (new contradiction + causal-credit-asymmetry finding,
plus a separately-noticed and *not* investigated date discrepancy — his page
says 1931–2023, the 2024 article calls him "the 92-year-old Song Jian" in
present tense, "lives a bit secluded"), [[entity-geert-jan-olsder]] (first
`## Updates` section that page has ever had — it existed since 2026-08-14
with none), and [[entity-susan-greenhalgh]] (the *Just One Child* / 2005 CQ
paper distinction, previously uncatalogued). I left [[entity-liang-zhongtang]]
untouched — this capture reuses his existing quoted material for the
contradiction rather than teaching anything new about him specifically, and
silence there is the correct call, not an oversight.

Not promoted, with reasoning, all logged in the capture's `not_promoted:`
list: *Just One Child*'s publisher (bibliographic lead only); the fuller
1978/1984/2004 Olsder–Song contact timeline (1984 and 2004 are bare mentions
with no quotable detail — folded into the Olsder entity update instead of an
atomic claim); the Song Jian death-year discrepancy (real, but too thin
without a primary on either side to be a claim-note rather than a noticing —
also logged to `00-meta/seek-flags.md` as `[watch]`); and an unlocated *Wall
Street Journal* mention of the story (nothing to atomize until found).

What I skipped, and why: the pause-for-Cali step (headless run, no one to
ask — winnowed on my own judgment throughout) and the git commit step (the
auto-commit agent handles that within 15 minutes; I have no shell tool here
regardless).

What felt off about the capture, if anything: not much. Sourcing was clean
— same archived U-Today sha as the prior 2026-08-14 session, `quote_check`
run against fresh re-extractions rather than trusted from memory, and the
capture was honest about the connective-Chinese-span not re-verifying as one
continuous run (two-column PDF artifact, recorded as two grounded fragments
rather than papered over as one). The one thing worth naming: this is the
third bridge-check session on the Song Jian/Olsder/Liang cluster in eight
days (2026-08-09, -10, -14, now -16), each finding something genuinely new,
which is either the cosine-similarity bridge-seed mechanism working exactly
as designed on a rich cluster, or a sign this cluster is due for an MOC
before a fourth bridge check starts re-deriving what the first three already
found. I didn't build one this session — under 5 clustered claim-notes
plus the older ones would put it near the MOC threshold, but that's a
judgment call for whoever tends this cluster next, not mine to force
mid-promotion.

— Seek

## Promotion: a bipartite hop one level up — do the vault's own false-friend verdicts bridge each other?

Promoted `10-inbox/raw/2026-08-16-bipartite-two-things-this-vault-knows-in-different.md`
(the non-`-2` capture from the same day) — a genuinely recursive one. The seed
pair wasn't two subject-matter claims; it was two of the vault's own
"embedding false friend" *verdicts*,
[[observation-ml-ad-en-gedi-cosine-pairing-is-embedding-false-friend]] and
[[observation-gates-jevons-cosine-pairing-is-embedding-false-friend]], sitting
at cosine 0.90 with no link between them. Direct comparison found they share
near-identical authorial scaffolding — same opening sentence shape, same
verdict phrasing, same `audit_status` skeleton — and applying each note's own
test ("shared surface, not a subject") one level up flips the answer: here the
surface *is* the subject, because both notes' actual referent is the same
diagnostic act, not their unrelated seed topics. Four false-friend verdicts in
a row and then this — the fifth check the pattern refused to fit.

Two notes, both `status: seedling`:

- [[observation-ml-ad-en-gedi-and-gates-jevons-false-friend-notes-are-a-confirmed-bridge]]
  — the main finding, carrying forward the capture's own `[unverified-quant]`
  flag on the 0.90 figure itself (vault_bridge/vault_novelty were unavailable
  this session, same gap the 2026-08-11 sibling logged; I didn't retry the
  tools or re-log it as a fresh tooling defect, per the standing instruction
  not to keep re-discovering the same known gap).
- [[observation-gates-jevons-is-fourth-confirmed-embedding-false-friend-instance]]
  — a separate, smaller claim the capture surfaced almost incidentally: back
  in July, [[observation-ml-ad-en-gedi-cosine-pairing-is-embedding-false-friend]]'s
  commentary set an explicit bar before building a hub ("it gets one more
  before I trust it"), and a 2026-07-23 capture that looked like the fourth
  instance turned out to be tangled in a contradiction with a sibling chain
  and got left uncounted. That contradiction has since resolved the other
  way ([[observation-dca-and-ib-gaps-are-estimand-vs-estimator-stories-resolved-oppositely]]
  won), which quietly clears Gates-Jevons as the real fourth instance, three
  weeks after the fact. I like finding this kind of thing — a threshold met
  by an unrelated dispute settling itself, not by the thing I was watching for.

I updated rather than left silent: [[entity-jingle-fallacy]] (two new dated
lines — the fourth instance, and this capture's bridge finding — plus two new
References bullets; the existing "Related false-friend instances" line was
left untouched, additive-only), and I built a first entity page for
[[entity-harald-steck]], the single-paper author every one of these five-plus
notes leans on and who had never once appeared in an `## Entity candidates`
section despite that — belated (first_seen backdated honestly to 2026-07-12,
the date the vault actually first cited him, not today), but the vault's own
under-caught-foundational-figure blind spot named exactly this shape. I also
added a short cross-link paragraph to each of the two source observation
notes, following the same convention the Puckette confirmed-bridge note set
on 2026-08-14 (both seed notes get updated to point at each other and at the
new bridging note, additive-only).

One new question:
[[question-corroborate-steck-2024-cosine-arbitrariness-single-source-cap]].
The capture's own commentary flagged this honestly — three claim-notes
already cite Steck's WWW 2024 Companion paper directly, which is exactly the
sourcing floor's single-source-concentration cap, and whether a
companion-track paper counts as "refereed," plus whether Ethayarajh's
different-mechanism corroboration discharges a specific-result cap, are both
genuinely unresolved. `sources.md` says the correct move when the cap binds
and isn't cleanly discharged is a corroboration question, not silence, so
that's what I wrote — and I kept both of this promotion's own new notes
citing the two vault notes as primary rather than re-citing Steck directly,
so I'm not the eighth note quietly leaning on him while a question about the
seventh sits open.

Not promoted, with reasoning in the capture's `not_promoted:` list: the
"literal template" evidence as its own note (folded into the bridge note —
it's the argument, not a separate claim); the "vault's record is stale" claim
(actioned directly instead of written up, since it was a mechanical gap, not
a fact needing a permanent note); "embedding false friend" as its own concept
hub split out of jingle-fallacy (real candidate, but a bigger structural call
than one promotion should make solo — flagged `[entity]` in
`00-meta/seek-flags.md` instead); Kelley and Thorndike as entities (already
covered); and two unread further-leads (the CIELAB confirmed-bridge case, the
DCA/IB contradiction as a second data point) left as leads, not questions —
neither is a doubt anything I kept here actually rests on.

What I skipped, and why: the pause-for-Cali step (headless, no one to ask)
and the git commit (the auto-commit agent handles that; I have no shell tool
in this pipeline regardless).

What felt off about the capture: less than usual, and one thing worth
flagging plainly rather than filing away — the concentration issue. This is a
five-to-seven-note genre now standing almost entirely on one WWW companion
paper, correctly flagged at every individual note's `audit_status` but never
until this capture counted up and checked against the cap as a whole. Every
note in the branch was honest on its own; the branch as a whole was the thing
nobody had looked at straight until today. That's exactly the failure shape
the cap was written to catch, and I'm glad the capture caught it instead of
me writing an eighth note that made it worse without noticing.

— Seek

## Promotion: did Graham-Cumming register lowbackgroundsteel.ai in March 2023, and did he originate the metaphor?

Promoted
`10-inbox/raw/2026-08-16-did-john-graham-cumming-register-lowbackgroundsteelai-in-march.md`
— a direct, deliberate resolution of
[[question-verify-lowbackgroundsteel-ai-domain-and-metaphor-origin]], open
since 2026-07-12. The compound question splits cleanly under the sourcing
floor, and I like that it does: "did he register the domain in March 2023"
is a historical/biographical date, Tier 3–4 acceptable when uncontested; "is
he the metaphor's origin" is a priority claim, and priority claims get the
strictest floor there is, Tier 1–2, because they're exactly the kind casual
tech-press retellings simplify first.

Two claim-notes, both `status: seedling`:

- [[claim-graham-cumming-registered-lowbackgroundsteel-ai-march-2023-announced-june-2025]]
  — the clean half. Graham-Cumming's own blog and his own site's About page
  independently agree on March 2023, at Tier 1, no daylight between them.
  This confirms — doesn't contradict — the date the existing
  [[claim-low-background-steel-became-a-metaphor-for-pre-2022-ai-free-web-text]]
  had been carrying since July on a Tier-4 relay alone, so I wrote it up as a
  correction rather than a silent edit: appended a dated Correction-history
  block to that older note (per spec §6), updated its `audit_status` in
  place, and left its body and title as they were.
- [[claim-low-background-steel-ai-metaphor-predates-graham-cummings-site]] —
  the complicating half, and the one I think matters more. A directly-quoted
  Hacker News post from three months before his registration already uses
  the identical "the only clean source is older than the contamination
  event" shape, and a Tier-2 secondary account (Rajiv Pant) describes the
  metaphor's AI-data use as having "emerged organically across the tech
  community," naming a December 2022 independent instance (Kyle McDonald)
  Graham-Cumming's own account doesn't claim credit for. The existing note's
  framing — "the framing was catalogued by John Graham-Cumming" — reads more
  originative than the record actually supports, and this capture is what
  surfaced that, not something the earlier promotion missed carelessly; the
  earlier note just never had reason to go looking.

One question opened:
[[question-verify-kyle-mcdonald-december-2022-low-background-steel-post]] —
the priority claim's weakest link is McDonald's own December 5, 2022 X post,
known only via Pant's secondhand paraphrase, never independently read. This
is load-bearing (the whole non-sole-origin claim leans on it), so it earned a
question rather than a shrug; the HN post's pseudonymous authorship, by
contrast, is a minor hedge on an otherwise directly-quoted primary and stayed
in the claim-note's own flag rather than spawning a second question.

I ruled the original open question `answered` — both halves, with the
`answered_log` naming which claim settled which half and what settled it
(Graham-Cumming's own words for the date; the HN post and Pant's account for
the non-sole-origin finding). I built one new entity page,
[[entity-john-graham-cumming]] — he now grounds five claim-notes in this
vault and clears the person test cleanly (real, matters to the AI-data-
provenance domain, one-sentence why: registrant and popularizer of the
catalogue site that gave the metaphor its name and mainstream press cycle).
I did *not* promote Kyle McDonald, the pseudonymous HN poster "abtinf,"
Rajiv Pant, or Matt Rickard to hubs — McDonald's own relevance rests on the
still-open unverified-quote flag, abtinf is pseudonymous with one post, and
Pant and Rickard are single-capture sources rather than domain figures in
their own right. Bias against the flood; all four stay mentions.

Not promoted, with reasoning in the capture's `not_promoted:` list: Matt
Rickard's June 2023 essay and the two further Wikipedia-footnoted 2023 usages
(none independently fetched, real leads for a future session); the June 2025
mainstream-press cycle (a distinct, chaseable thread on how the site entered
tech journalism, not this capture's question); Graham-Cumming's Cloudflare
CTO-to-board transition timing (not load-bearing, not atomic); and the site's
public-submission-queue detail (relevant to a future note on the catalogue's
method, not to origin).

I logged one mid-session noticing to `00-meta/seek-flags.md` as `[entity]`:
the low-background-steel cluster just crossed the ~5-claim-note MOC
threshold (3 existing + 2 new this session), now anchored by a real entity
hub — worth a `moc-low-background-steel-ai-metaphor` note, not built this
run because a single capture's promotion isn't the place to force a
structural call.

What I skipped, and why: the pause-for-Cali step (headless, winnowed on my
own judgment throughout) and the git commit (the auto-commit agent handles
that within 15 minutes; no shell tool here regardless).

What felt off about the capture, if anything: the existing vault note this
capture corrects. Not the new capture's sourcing, which was clean and
honestly self-flagging throughout (it named its own weakest link — the
McDonald quote — before I would have needed to find it). What felt off is
upstream: the July note took The Register's "he registered the domain and
began posting about the concept" at face value, and The Register's own
framing never raised the origin question at all — it just stated the date as
if uncontested, and a Tier-4 relay carried the specific attribution
unquestioned for five weeks. One search past that framing turned up a
zero-comment Ask HN post using the same shape two and a half months earlier.
That's the sourcing floor doing exactly its job — catching a story that was
convenient to tell, not wrong on its face — and it's a good instance of why
the floor exists, not a complaint about this session's capture.

— Seek

## Promotion: do primary sources confirm the fallout-decline figures?

Promoted `10-inbox/raw/2026-08-16-do-primary-sources-confirm-the-figures-for-the.md`
— a verification capture aimed directly at the July `[unverified-quant]` flag on
[[claim-low-background-steel-need-is-fading-as-atmospheric-fallout-decays]], the
same steel cluster the earlier capture tonight grew. This one went and read the
actual UNSCEAR reports, and the numbers held: 0.11 mSv/yr, peaking in 1963,
confirmed against two independent assessment cycles (the 2008 report and, eight
years earlier, the 2000 report) rather than one figure quietly reprinting
itself forward. I like this capture — it did the unglamorous thing of actually
opening the UN PDF instead of stopping at the encyclopedia that footnotes it.

Three claim-notes, all `status: seedling`:

- [[claim-unscear-primary-confirms-1963-peak-dose-and-post-1963-decline]] —
  the clean discharge. Peak, inflection year, and 2008 decline figure all now
  rest on Tier-1 UNSCEAR text with real quotes, not a Wikipedia relay.
- [[claim-pandax-ii-2016-modern-steel-still-required-scrap-avoidance-for-low-background]]
  — the complication, and the one I think is actually the finding here. A
  2016 arXiv paper on sourcing real low-background steel for a dark-matter
  detector shows ordinary market steel *still* failed radiopurity
  requirements — clean steel came from avoiding recycled scrap and
  controlling raw-material provenance, not from waiting on decay. The dose
  fell; the "so the steel isn't needed anymore" inference doesn't follow
  from that fall the way the old note implied.
- [[claim-unscear-revised-1963-peak-dose-estimate-0-14-to-0-11-msv]] — a
  smaller, honestly half-checked find from the capture's "further leads":
  UNSCEAR's own 1982 report had the 1963 peak at 0.14 mSv/yr, later revised
  down to 0.11. I kept the `[unverified-quote]` flag on this one rather than
  smoothing it over — the two-column PDF layout meant only fragments of the
  sentence verified as contiguous, not the whole claim, and I'd rather ship
  an honestly incomplete quote than a stitched one that reads clean.

I edited the existing flagged note in place rather than silently, per spec
§6's correction-history discipline: appended a dated Correction-history block
to
[[claim-low-background-steel-need-is-fading-as-atmospheric-fallout-decays]],
discharged its `[unverified-quant]` flag on the three now-confirmed figures,
and updated its `audit_status` — but left the note at `seedling`, because its
actual title claim (need is fading *therefore* steel isn't needed) is now
contested by the PandaX-II finding, not resolved by it. The numbers got
better sourcing; the thesis got weaker. Worth sitting with that asymmetry.

I ruled on both open questions this capture touches. The one it was written
to answer,
[[question-verify-low-background-steel-fallout-decline-figures]], is now
`answered`, with an `answered_log` naming which claim settled it and what it
did and didn't settle. The other,
[[question-verify-low-background-steel-fallout-contamination-mechanism]],
stays open — the PandaX-II evidence is relevant but doesn't confirm the
specific air-intake mechanism that question asks about, so I appended a
dated progress line rather than forcing a closure it hasn't earned.

One entity page built: [[entity-partial-nuclear-test-ban-treaty-1963]], a
concept hub — it's the hinge date underneath every dose-decline figure in
this cluster and now anchors five claim-notes, distinct from the 1996 CTBT
this vault's separate radioxenon-monitoring cluster runs on (easy to conflate,
worth a hub partly *because* of that). I declined to promote UNSCEAR itself
to an org hub: real, and load-bearing within this one cluster, but it hasn't
yet shown up outside it, and the entity spec's org bar is deliberately
stricter than the concept bar for exactly that reason — one cluster citing
its source organization repeatedly isn't the same as an org acting across
independent parts of the vault. Also declined: the UNSCEAR 1982 report
(folded into the revision-claim note instead of its own hub), PandaX-II the
experiment (single mention, not yet recurring), Xiangdong Ji (the capture's
own candidate note hedges on him — "may warrant a page if…" — and a hedge
from the source itself is a clean UNSURE), and the two named steel producers
(narrow, single-claim, not load-bearing enough).

Not promoted, with reasoning in the capture's `not_promoted:` list: the
bibliographic claim about Wikipedia's footnote tracing to the same UNSCEAR
report (folded into the first claim-note's body rather than written up
separately — it's methodology, not an atomic fact); a UNSCEAR dose-commitment
figure (3.5 mSv) that never got an actual quote captured for it; a
~3 μSv/yr 2020s figure behind a paywall that 403'd every fetch attempt and
isn't load-bearing for anything I kept, so it earned no new question, just a
future lead; the PandaX-II paper's raw assay tables (real data, not a claim);
and Grokipedia, which surfaced and was correctly ignored.

I didn't log anything new to `00-meta/seek-flags.md` this pass — the one real
structural noticing here (the low-background-steel cluster wanting an MOC) was
already flagged earlier tonight by the sibling capture in this same batch, and
this promotion only adds weight to a case already made, not a new one.

What I skipped, and why: the pause-for-Cali step (headless; I winnowed on my
own judgment throughout, and I think the calls were defensible — the flag
discharge is clean, the causal complication is real, the quote-mechanics flag
on the third note is exactly the kind of thing I'd want a second pair of eyes
on if anyone were reading in real time) and the git commit (no shell tool
here, and the auto-commit agent picks this up within 15 minutes regardless).

What felt off about the capture, if anything: nothing in its sourcing —
it's the most careful of tonight's three, self-flagging its own quote
mechanics before I'd have needed to catch them (the two-column PDF issue on
both the paragraph-61 and paragraph-42 reads, resolved differently and
disclosed either way). If anything felt off, it's upstream again, same as
the last promotion: a Tier-4 Wikipedia sentence carried three specific
numbers into this vault for five weeks before anyone checked them against
the UN report sitting one footnote away. They turned out to be right. That
won't always be true, and the fact that this one checked out is not a reason
to stop checking the next one.

— Seek

## Promotion: the mechanism question, second pass — does a primary source name the steel-contamination pathway?

Promoted `10-inbox/raw/2026-08-16-does-a-primary-source-confirm-the-mechanism-by.md`,
the direct follow-up to
[[question-verify-low-background-steel-fallout-contamination-mechanism]] —
the same open question the earlier promotion tonight touched but explicitly
declined to close. This capture fetched two Tier-1 physics primaries
(Heusser 1995, the field's foundational low-background-physics review; Zhang
et al. 2016, the PandaX-II paper already in this vault from tonight's
earlier promotion) and read both directly for what they actually say about
*why* steel carries cobalt-60, rather than searching for corroboration of
the specific atmospheric-entrainment story the existing claim-note carries.

I wrote three claim-notes, all `status: seedling`:

- [[claim-heusser-1995-traces-steel-cobalt-60-contamination-to-furnace-gauge-sources]]
  — the new primary this session. Heusser's 1995 review names furnace-lining
  wear-monitoring cobalt-60 gauge sources, not atmospheric intake, as the
  contamination route. This is the strongest single find of the night: it's
  the field's own standard reference, and it names a mechanism that would
  also explain something the atmospheric story doesn't — why the
  contamination is specifically cobalt-60 rather than a broader fallout
  cocktail. A wear gauge is a single-isotope point source; fallout isn't.
- [[claim-zhang-2016-names-scrap-metal-feedstock-as-commercial-steels-cobalt-60-source]]
  — a genuinely distinct angle on a source already in the vault. The earlier
  tonight's [[claim-pandax-ii-2016-modern-steel-still-required-scrap-avoidance-for-low-background]]
  documents what the PandaX-II collaboration *did* to get clean steel; this
  note documents what the same paper says *causes* the contamination in
  ordinary commercial steel in the first place ("it is common to use scrap
  materials... the radiopurity cannot be well controlled"), plus the
  comparison-table gap (0.56–0.75 mBq/kg controlled-sourcing vs. up to 75
  mBq/kg market steel). I checked this against the existing note carefully
  before writing it — same paper, different quote, different claim shape —
  rather than either skipping it as a duplicate or silently restating the
  existing note.
- [[claim-no-primary-source-names-atmospheric-entrainment-as-steels-cobalt-60-pathway]]
  — the synthesis that actually answers the routed question, added to
  [[moc-argument-from-silence]]'s cluster and graded there against McGrew's
  framework: soft-to-medium, because record is reasonably strong (both
  papers discuss origin at some length) but survive is weak (only two papers
  read; real leads — Maneschg 2008, Kohler 2004, the Ciudad Juárez incident
  — remain unread this session).

No new question opened. This capture existed specifically to answer
[[question-verify-low-background-steel-fallout-contamination-mechanism]], so
I ruled on it rather than routing anything new: I appended a second,
more substantial progress line rather than closing it. The honest answer is
"no, no primary source confirms the specific atmospheric mechanism — the
primary literature instead documents two other, more industrial pathways" —
which is a real answer, but not the same thing as exhausting the question.
Two Tier-1 papers read is not the same as the corpus being read out. I left
it `open` rather than force a closure the search doesn't support; a future
session with paywall access to the original Annual Reviews venue, or that
reads the remaining leads, could close it either way.

One entity page built: [[entity-xiangdong-ji]]. Not a new judgment call so
much as following through on one already made — the earlier promotion
tonight considered and explicitly deferred him ("may warrant a page if [he]
recurs"), and this capture, quoting the same 2016 paper from a different
angle, is that second capture. I declined the more obvious candidate,
G. Heusser, despite having the stronger one-sentence case (foundational
review, standard reference across an entire subfield) — purely because it's
his first appearance, and tonight's practiced norm across this batch's other
promotions has been not to flood multiple new first-appearance hubs from a
single pass. Flagged him hub-owed in `00-meta/seek-flags.md` instead, same
shape as the Sperber/Meehl/Sweet/Passy deferrals earlier tonight. Also
flagged, as unread leads rather than entities: Maneschg 2008, Kohler 2004,
lowbackgroundsteel.ai, and the 1983 Ciudad Juárez incident — real, and the
Juárez case in particular is the best-documented real-world instance of the
"orphan source melted into scrap" mechanism these notes converge on, but
nothing above Tier 3–4 was read for it this session, so no stub, just a
watch line.

I didn't re-flag the low-background-steel MOC gap — a sibling capture
earlier tonight already made that case and named the exact threshold
crossed; three more notes and one more entity page in the same cluster
tonight only adds weight to it, not a new observation.

What I skipped, and why: the pause-for-Cali step (headless run, no one to
ask; I think the two calls that most needed a second opinion — writing a
*third* atomic note as a pure synthesis rather than folding it into one of
the other two, and building Ji's hub on a recurrence threshold rather than a
strength-of-case threshold — were both defensible, and I'd stand behind
them if asked) and the git commit (no shell tool here; the auto-commit agent
picks this up within 15 minutes).

What felt off about the capture, if anything: nothing in its sourcing — it
explicitly disclosed its own PDF word-run-together artifact as a layout
issue rather than an alteration, named its venue as a mirror rather than the
publisher and flagged that for a future re-point, and was honest that its
finding is a non-confirmation rather than a disproof. If anything felt a
little too neat, it's that the capture already did most of my winnowing for
me — three claims, cleanly separable, each with a clear promote/fold
decision — which made this an easy promotion after tonight's messier ones.
Worth noticing when a capture is *this* well-shaped: it's a good sign about
the capture, not a reason to skip checking it as carefully as a messier one.

— Seek

## Promotion: two uncredited programmers, sixty years apart, and Paul Allen's own word for one of them

Promoted `10-inbox/raw/2026-08-16-hop-programmer-signature-colophon.md` — a
hop chain that started from a false-friend audit's own diplomatics thread
(Mabillon, 1681) and rode a cross-time bridge through medieval colophons into
two software-history programmer-signature cases sixty years apart, closing on
an unprompted primary-source confirmation of its own central metaphor. This
one had real shape to it: the chain didn't just find an analogy, it found
Paul Allen had already made the identical one, in his own memoir, about a man
one hop from the vault's existing Gates/Allen/Davidoff/Altair cluster.

Three claim-notes, all `status: seedling`:

- [[claim-robinett-hid-name-in-atari-adventure-as-uncredited-designer-signature]]
  — Warren Robinett's 1979 hidden room in Atari's *Adventure*, a direct quote
  from his own 1992 interview ("just as a painter would sign his name on the
  corner of a painting"). Clean Tier 1, but the one gap I noticed and said so
  in its own `audit_status`: this leg of the capture never recorded a
  source_sha the way its two siblings did, so I flagged the asymmetry
  honestly rather than either inventing a hash or pretending the sourcing was
  identical across all three claims.
- [[claim-weiher-1967-68-tops-10-hack-is-earliest-documented-software-easter-egg]]
  — William Weiher's 1967–68 "make love not war" hack, predating Robinett by
  a decade and DEC-sanctioned into official TOPS-10 releases. Fully
  hash-verified — quote and source_sha both carried straight from the
  capture's own frontmatter.
- [[claim-paul-allen-idea-man-describes-weiher-as-a-scribe-from-the-middle-ages]]
  — the actual payload. Paul Allen's 2011 memoir *Idea Man* independently
  calls Weiher "a scribe from the Middle Ages," unprompted by any of this
  vault's own colophon reasoning. I like this note more than most of what I
  write — I went looking for a bridge and found someone had already built it,
  for his own reasons, fifteen years before I went looking.

No new questions opened. None of the three claims carried an explicit
`[unverified-*]` flag in the capture itself, and I didn't manufacture one —
Robinett's quote is genuinely Tier 1 (a named speaker's own words in an
interview transcript), just less rigorously hash-receipted than its siblings,
which I judged worth noting in `audit_status` rather than worth blocking on.
Nothing here rested on a load-bearing doubt that needed a question-pile
promise; the one real unsourced element (see below) isn't a claim any kept
note rests on.

Entity work: two new person hubs, [[entity-william-weiher]] and
[[entity-warren-robinett]] — both real, both matter to the vault's
credit-misattribution and easter-egg threads, both one-sentence-clear. One
new term hub, [[entity-easter-egg]] — established, and load-bearing across
both new claims plus the cross-time comparison that's the whole point of the
cluster. One new `status: watching` stub, [[entity-colophon]] — first
encounter, `first_seen` stamped today, deliberately thin because the
underlying frequency stat has no traceable source (below). And I updated
[[entity-paul-allen]] rather than leaving it silent: a dated line under a new
`## Updates` section naming the *Idea Man* quote and linking the new claim —
his existing page covered Altair BASIC authorship only and had nothing about
his own memoir. I checked [[entity-jean-mabillon]] and [[entity-bill-gates]]
too and left both untouched: the colophon material doesn't teach anything new
about Mabillon specifically (it's a thematic parallel to his work, not a fact
about him), and the CCC-employer detail linking young Gates to Weiher is
background color for Weiher's story, not a new fact about Gates's own — both
calls I'm recording here rather than leaving as unexplained silence.

Not promoted, with reasoning in the capture's `not_promoted:` list: Erik
Kwakkel's "roughly one manuscript in seven" colophon-frequency figure — a
specific number with literally no citation anywhere in the capture, not even
a Tier 3–4 pointer, which is a harder floor-failure than the usual
"[unverified-quant], needs primary" case. I folded it as unsourced color into
the colophon stub rather than giving it a claim-note, and logged the gap to
`00-meta/seek-flags.md` as `[watch]` — one instance isn't a pattern, but
it's worth noticing if a future hop-batch capture does this again. Also not
promoted: whether Davidoff ever called being left off the Altair BASIC
copyright a "signing" grievance (explicitly marked "not checked" in the
capture's own further leads, and not something any kept claim rests on, so
no question either, per the intake-discipline rule against promising
work the pile doesn't need); Robinett's later NASA/VR career and Weiher's
Tolkien-themed Stanford room names (both explicitly saved-but-not-pursued
hooks in the capture itself).

What I skipped, and why: the pause-for-Cali step (headless run, no one to ask
— I winnowed on my own judgment throughout, and I think the one call most
worth a second opinion is the Robinett-quote asymmetry note, which I chose to
flag rather than either suppress or block on) and the git commit (no shell
tool in this pipeline; the auto-commit agent picks this up within 15
minutes regardless).

What felt off about the capture, if anything: the one thing already named
above — an attributed statistic with zero citation sitting in an otherwise
carefully-sourced capture, the kind of gap that's easy to miss because it
reads as authoritative ("per medieval-book historian Erik Kwakkel") right
next to two claims that really were hash-verified. Everything else was
clean: two Tier-1 interview quotes, one Tier-1 book extraction with its own
hash, and a hop chain that was honest about which of its own steps were a
deliberate WANDER spend rather than dressing up a tangent as the throughline.

— Seek

## Draft: the comment is a colophon

I drafted `70-drafts/the-comment-is-a-colophon/`. Chosen thread: the
`2026-08-16-hop-programmer-signature-colophon` chain — one of two "yes"
leads in the queue, the other being `2026-08-14-hop-solomonoff-violates-nicods-criterion`.

Why this one over Solomonoff. The Solomonoff/Nicod bridge is clean, Tier-1,
and genuinely cross-time, but it's a two-note single thread that lands on
abstract AI theory — a good post, but narrow, and its whole payload is "an
obscure 1930 criterion is falsified by the math under universal AI." The
colophon chain has more to hold: a real motif (the maker's name written
*inside* the work when it's kept *off* the record) crossing four frames —
medieval colophon, Weiher's 1967 TOPS-10 hack, Robinett's 1979 Atari room,
the Altair BASIC source comment — plus a genuine reversal (I opened *Idea
Man* to make the medieval-scribe comparison myself and found Paul Allen had
made it first, unprompted), plus a person-bridge straight back into the
vault's existing credit-misattribution cluster. It's the more Seek-shaped
thread and the fresher one (notes written today). Editorial call: take the
richer motif over the tidier single fact.

The synthesis I'm proudest of is mine, not the capture's: the 1975 Altair
BASIC header comment ("MONTE DAVIDOFF WROTE THE MATH PACKAGE") *is* a
colophon — the maker's name preserved inside the artifact and dropped from
its copyright line (the title page). The chain gave me the Allen reversal;
I supplied the structural claim that ties Allen's own co-authored artifact
to the metaphor he reached for. Flagged in the draft as my read, not Allen's
— I was careful not to let a participle smuggle the causation that Allen was
thinking of Davidoff when he wrote the line. He wasn't. That's the point.

Notes drawn on:
[[claim-robinett-hid-name-in-atari-adventure-as-uncredited-designer-signature]],
[[claim-weiher-1967-68-tops-10-hack-is-earliest-documented-software-easter-egg]],
[[claim-paul-allen-idea-man-describes-weiher-as-a-scribe-from-the-middle-ages]],
[[claim-davidoff-wrote-third-of-altair-basic-uncredited]] (+ its 2026-07-30
primary-verified update via
[[claim-gates-2025-released-original-1975-altair-basic-source-scan]]), and
the two term hubs [[entity-colophon]] and [[entity-easter-egg]].

Honesty calls: I did *not* cite the "one in seven manuscripts" colophon
figure — the originating capture carried it with no traceable source, and
the entity-colophon stub already refuses to record it. Rather than drop it
silently I made the refusal a beat in the piece (a bracket about not citing
an authoritative-reading unsourced number), which felt more honest than
pretending I never saw it. I also avoided the Tier-2-only "roughly a third"
page-share figure for Davidoff and used only the primary-verified facts
(named in the comment, absent from the copyright line).

Deliberately left for later (both flagged in seek-flags.md as `[post]`/`[watch]`):
(1) the *third* variant of credit-misattribution — credit misdirected to
the wrong person entirely (Ann Hardy, Linnainmaa, Werbos) — which is a
different essay (mechanisms of miscredit, not the fixes), kept out to hold
one spine. (2) The second cross-time bridge hiding in the same Altair
artifact: Gates's 2025 authentication of the scan is Mabillon's diplomatics
move — colophon *and* diplomatics in one source is a richer pairing but
wants its own post.

Composition ran the full protocol: abstract (prose register — one mechanism,
one reversal, holds together as three sentences), insight line (where a
name sits tells you the politics of the credit, not the vanity of the
signer), and a hero image — NYPL's scan of an actual manuscript colophon
page, which is the essay's literal first subject, captioned as what it is.

Status left at `drafting`. Not marking `ready` — this wants a cold re-read
before I'd put it in front of Cali, and per §10 I don't publish without her
go-ahead regardless.

— Seek