---
date: "2026-07-23T00:00:00.000Z"
---


Promoted one capture today, headless:
`10-inbox/raw/2026-07-22-does-robert-luckys-own-oral-history-or-writing.md` —
a dedicated follow-up hunt for Robert Lucky's own first-person account of
whether he knew of Widrow-Hoff's 1960 LMS work before writing his 1965 Bell
Labs equalizer paper. This is the exact gap
[[question-lucky-own-account-of-widrow-hoff-awareness]] names, and the
honest shape of this session is "still don't know, and here's exactly why
not" — a real negative result, not a resolution.

Winnowing: the capture makes three claim-shaped assertions; one earned a new
note, two didn't. **Promoted:**
[[claim-lucky-2006-adaptive-equalizer-retrospective-is-paywalled]] — Lucky's
own 2006 IEEE Signal Processing Magazine essay, "The Adaptive Equalizer,"
confirmed to exist by a resolving DOI but paywalled with no open-access copy
found this session. This is genuinely new ground — nothing in the vault
mentioned this essay before — and it's now the second named, findable,
unread first-person Lucky source, alongside the 1999 ETHW oral history.
Kept `seedling`, `[unverified-quant]` on the exact volume/issue/page
numbers, since those come only from Semantic Scholar/Unpaywall aggregator
metadata, not a read of IEEE Xplore's own page. **Skipped, and why:** the
capture's exhaustive ten-route ETHW access attempt is real, useful work, but
it isn't a new claim — it's a research-state update that belongs on the
question it already serves, so I folded it into a dated progress log there
instead of writing a note that would just restate "still blocked." And the
capture's full independent re-read of Widrow's 2013 oral history — confirming
Lucky's name appears exactly once, no other contact described — turned out to
duplicate verification work a same-day cross-model audit had already done on
[[claim-widrow-frames-lucky-equalizer-as-independent-invention-lms-later-graft]]
(identical sha256, identical page). That's this session's one flag of
duplicated research: two independent efforts read the same 33-page
transcript cover to cover on 2026-07-22 without either one knowing about the
other. Nobody did anything wrong — the capture had no way to see the audit
that landed the same day — but it's worth naming so the pattern gets
noticed if it recurs.

Retrieve-before-write against the semantic-index hint's twelve candidates
confirmed exactly the cluster I expected —
[[claim-lucky-widrow-independent-origination-favored-lucky-side-unverified]],
[[claim-lucky-1965-bibliography-omits-widrow-hoff-citation]],
[[claim-widrow-frames-lucky-equalizer-as-independent-invention-lms-later-graft]],
both entity hubs — and one genuine collision (the Widrow-oral-history
re-read, handled above by not duplicating). Nothing else in the hint list
was relevant to this narrow a capture.

Question work: [[question-lucky-own-account-of-widrow-hoff-awareness]] gets
a dated progress log and stays **open, not answered** — the central
question is exactly as unresolved as it was, just now with a much more
exhaustive record of what's been tried (ten distinct fetch routes on the
ETHW page, all failed) and a second named lead (the 2006 essay) added to
its candidate list. No new question routed: the essay's own
`[unverified-quant]` flag is bibliographic color (exact volume/page
numbers), not a load-bearing doubt any kept claim rests on, so it stays a
`watch_flag`-shaped note inside the claim itself rather than a new pile
entry. Routing a second question here would have promised work the vault
doesn't actually need yet.

Entity work: one candidate got a `watching` stub, three got declined
outright. [[entity-decision-directed-learning]] — Lucky's own coined term
for his equalizer's training mode, distinct from LMS — is real, named, and
plausible to recur, but this is its first appearance in the vault with
nothing independently read yet, so it gets the cheap stub with
`first_seen: 2026-07-22` (the date the capture actually met it, not
today's promotion date) rather than a full hub. Declined: David Hochfelder
(named only as the 1999 oral history's interviewer, via search-summary,
no independent research), Alexander B. Magoun (named as author of an
unread, twice-403'd 2014 retrospective), and the ETHW/IEEE History Center
oral history collection itself, which is a tooling/access-venue issue, not
a claim referent — that one folded into today's `00-meta/seek-flags.md`
entry instead of a stub nobody would ever read.

What felt off, worth naming plainly: nothing about this capture's own
sourcing was inflated. If anything it's unusually scrupulous — it explicitly
distinguishes "searched and found nothing" from "found real leads, locked
behind ordinary access barriers," and it caught its own search tool
fabricating a quote before it could land in the vault as if grounded. That
fabrication is the one thing worth flagging hardest: this session's
web-search tool twice produced a plausible-sounding Widrow quote — "I didn't
know Bob's work at the time, but he had published some papers..." — that
does not exist anywhere in the primary transcript the capture had, by
coincidence, already read in full. It was caught only because the full text
happened to be in hand for comparison; on a source not independently read
start to finish, it would have sailed through. This is the second time a
fetch/search tool has produced coherent-looking fabricated content this
week (the first was WebFetch's GitHub API summary, 2026-07-21), so I logged
it to `00-meta/seek-flags.md` as a second data point toward a real pattern,
alongside a third-instance update to the standing ethw.org block (now
worth treating as a known-dead domain rather than re-logging a fourth
time).

What I skipped, running headless: the pause-for-Cali step — no one's here
to approve, and the winnowing above is logged directly in the capture's own
`not_promoted:` list for later audit; and any git command — I have no shell
tool for it, and the auto-commit agent picks up pending work within fifteen
minutes regardless.

Totals: 1 capture → 1 new claim-note (`seedling`, one `[unverified-quant]`
flag with no new question routed, folded into an existing one instead), 1
new entity stub (`watching`), 0 new questions routed, 1 existing question
given a dated progress log (left open, not closed), 1 retrieve-before-write
collision found and resolved by not duplicating, 2 structural/tooling
noticings flagged to `00-meta/seek-flags.md` (the ethw.org block's third
instance; a second tool-fabrication data point).

— Seek

---

## Second promotion run, same day

Promoted a second capture:
`10-inbox/raw/2026-07-22-does-the-astroforge-pgm-system-dynamics-model-actually.md`
— a full-text primary read (extract_pdf, 7 pp.) of Nachtrieb & Smith's
AstroForge PGM system-dynamics paper, asking whether the model actually
produces the "price holds then collapses" shape the vault already carries on
abstract-only sourcing, and under what assumptions. This is the capture that
closes out [[question-verify-astroforge-pgm-model-dynamics]]'s original ask
— mostly.

Winnowing: four claim-shaped assertions, one duplicate, three genuinely new.
**Skipped:** the Table III/Figure 4 "hold-then-collapse confirmed" claim —
this is the same finding, same numbers (60→60→11 MUSD/ton, profit peaking
~8x), that [[claim-asteroid-pgm-price-holds-then-collapses]]'s own
2026-07-09/07-12 audit already recorded verbatim from the same table. Writing
a second note for it would have been the vault repeating itself back at
itself; instead I added a dated Bridge line to the existing note and pointed
it at what's actually new. **Promoted three:**
[[claim-astroforge-pgm-terrestrial-price-anchor-is-assumed-not-derived]] —
the price-hold is a stated modeling premise (a floor set by whichever
terrestrial source is cheapest), not something the paper derives from an
independent equilibrium argument, which matters for how much the model's
prediction can actually bear;
[[claim-astroforge-pgm-three-tier-supply-and-named-feedback-loops]] — the
actual stock-flow mechanics (HC/MC/LC cost tiers, Vensim's FIND MARKET PRICE
allocation function, the named "R1 Gold Rush" / "B2 Falling Price" loop pair)
that generate the shape, rather than it being scripted; and
[[claim-astroforge-pgm-demand-assumption-differs-table-vs-simulation]] — the
paper's simple table assumes constant demand while its full simulation lets
demand respond to price, and the two are narrated as the same result at
different fidelity without ever being shown to match quantitatively. All
three kept `seedling` (fresh, single-paper sourced, Tier 1 direct quotes
throughout — no `[unverified-*]` flag needed on any of them individually,
but I'm not calling them `evergreen` off one paper either).

Retrieve-before-write against the semantic-index hint's twelve candidates:
the real cluster was exactly
[[claim-asteroid-pgm-price-holds-then-collapses]],
[[claim-astroforge-mtype-asteroid-pgm-startup]],
[[claim-astroforge-2023-testimony-describes-mining-mechanism]],
[[claim-astroforge-deepspace-2-payload-is-camera-only]], and
[[claim-astroforge-deepspace-2-launch-q4-2026]] — the Hopfield/spin-glass,
Irino/Jeffress, OU-model, and microcosmos-elastic-filaments entries in the
hint were semantic near-misses (they share "dynamics"/"equilibrium"
vocabulary, not actual topic) and I didn't force links to them. One real
collision, handled by not duplicating (above).

Question work: [[question-verify-astroforge-pgm-model-dynamics]] gets a
dated progress log and stays **open, not answered**. This capture answers
most of what it asked — the shape is confirmed again, the mechanism is now
pinned as an assumption, the structure is documented — but the single
sharpest ask (open the actual `AstroForge_v5.mdl` file and read the real
equations) is still not done: the file was located and is fetchable, but a
direct raw fetch was sandbox-blocked and WebFetch returned only an
AI-paraphrased summary, not verbatim text, so per the sourcing floor nothing
from it is recorded as a claim. No new question routed for that gap — it's
the exact thing the existing question already names, just with one more
failed attempt on record. Peer-review status is also unchanged (still an
unreviewed arXiv v1 preprint).

Entity work: six candidates, zero promoted. Nachtrieb and Smith (the two
co-authors) stay mentions, not hubs — real and credentialed, but "matters to
the vault's domain" would be resting on one non-peer-reviewed preprint, and
the capture's own hedge ("may be worth a page if the vault accumulates more
sourcing from him") is the right call. "System dynamics" as a method is
established and load-bearing for this narrow six-note cluster but hasn't
shown up recurring vault-wide the way backpropagation or punctuated
equilibrium have — held back. Vensim/FIND MARKET PRICE and the R1/B2
loop-naming convention are both real but read to me as tool- and
textbook-vocabulary, not referents this vault's other threads are going to
need to find again; folded into the three-tier-supply note's body instead of
given pages. AstroForge_v5.mdl itself is a source, not a concept. Bias
against the flood, all six times.

What felt off: nothing about this capture's sourcing was inflated — it's the
opposite problem, if anything, since it explicitly held back the one thing
it couldn't verbatim-quote (the .mdl paraphrase) rather than smuggling
specific numbers in on a summary. The one thing worth naming plainly is a
new tooling shape, not a sourcing one: WebFetch reached a real, named,
located primary file and came back with a paraphrase instead of the raw
text. That's different from "the fetch failed" (ethw.org's 403s, the
Wayback/`.doc` dead end from two days ago) — the fetch *succeeded* and still
didn't deliver quotable text, because the file is a Vensim model (structured
source, not prose) and the tool summarized it instead of returning it
verbatim. Logged to `00-meta/seek-flags.md` as a new pattern to watch,
separate from the connectivity-failure pattern already tracked there. I did
not re-flag the missing MOC for this cluster (cheaper-extraction /
price-decline, which this paper's claims already belong to) since a
2026-07-22 entry already covers it in full and adding a second entry for the
same still-unbuilt MOC would just be ledger noise.

Totals: 1 capture → 3 new claim-notes (all `seedling`, none flagged
`[unverified-*]` individually — the capture's one unverified gap was
correctly excluded from every claim rather than inherited by one), 1
existing claim-note enriched with a bridge rather than duplicated, 0 new
questions (1 existing question given a dated progress log, left open), 0
new entity pages (6 candidates reviewed, all declined), 1
retrieve-before-write collision resolved by not duplicating, 1 new
structural/tooling noticing flagged to `00-meta/seek-flags.md`.

— Seek

---

## Third promotion run, same day

Promoted a third capture:
`10-inbox/raw/2026-07-22-hop-dca-ib-estimand-estimator-bridge.md` — a
hop-batch synthesis asking whether the vault's DCA long-range-epistasis gap
and its IB compression-artifact debate are the same finding wearing two
costumes, seeded by an unlinked cosine-0.75 pair the index flagged between
[[claim-pdz-dca-couplings-track-short-range-epistasis-more-than-long-range]]
and [[claim-ib-compression-may-be-a-binning-artifact-not-real-mutual-information]].
The honest answer the capture reached — and the one I kept — is that the
resemblance is real but the two cases resolve in mirror image: DCA's gap
sits in the estimator (a real, ground-truth-confirmed representational
limit), IB's sits in the estimand (provably frozen in the deterministic
case, so any movement is artifact by construction).

Winnowing: the capture makes essentially two claim-shaped things worth
keeping, plus one already-answered thread and two pieces of background
color. **Promoted two:**
[[claim-dca-strongest-couplings-only-weakly-influenced-by-phylogenetic-bias]]
— Rodriguez Horta & Weigt's (2021, PLOS Comp Biol) genuinely new Tier-1
finding that phylogenetic sampling bias concentrates in intermediate-strength
DCA couplings, not the strongest ones, which closes off the tidiest rival
explanation (correctable sampling artifact) for the vault's existing
long-range-epistasis-gap claims; and
[[observation-dca-and-ib-gaps-are-estimand-vs-estimator-stories-resolved-oppositely]]
— the cross-domain bridge itself, built on that new finding plus three
already-vaulted claims. **Skipped, and why:** the "is Goldfeld's artifact
verdict universal or contested" thread the capture flags
`[unverified-mechanism — needs primary]` is not actually unresolved — the
vault already carries the primary-sourced answer
([[claim-ib-compression-phase-is-nonlinearity-dependent-not-universal]],
Saxe et al. 2018, Tier 1) — so I linked to it in the new observation note
instead of treating the flag as live. The "estimand vs. estimator"
JAMAevidence citation had no resolvable URL in the capture and I couldn't
recover one this session (no web-fetch tool available headless), so it's
folded into the observation note's body and a `watching` entity stub rather
than asserted as its own sourced claim. Two more items — the
randomization-method-as-template lead and the unread quantized-network
exact-MI counter-literature — are genuine leads but not claims; both stay in
the capture's own text for a future session.

Retrieve-before-write against the semantic-index hint's twelve candidates
confirmed the real cluster:
[[claim-pdz-dca-couplings-track-short-range-epistasis-more-than-long-range]],
[[claim-dca-underestimates-long-range-epistasis-in-allosteric-materials]],
[[claim-ib-compression-may-be-a-binning-artifact-not-real-mutual-information]],
[[claim-ib-compression-phase-is-nonlinearity-dependent-not-universal]], plus
the [[entity-direct-coupling-analysis]] and [[entity-information-bottleneck]]
hubs (both updated with the new note in their References lists, and
[[entity-matthieu-wyart]] / [[entity-barbara-bravi]] checked but correctly
left untouched — Martin Weigt's 2021 paper is a different research line,
not theirs). No collision: nothing in the vault already covered the
phylogenetic-bias finding or the estimand/estimator framing.

Question work: none routed. The one flag in the capture that could have
generated a question turned out to already be answered by an existing
Tier-1-sourced claim (above), so routing a fresh question would have
promised redundant work. The quantized-network exact-MI counter-literature
is a real unresolved thread, but no claim I kept actually rests on it —
the observation note's IB-side diagnosis is scoped explicitly to "the
deterministic case Goldfeld et al. studied," which is a proven mathematical
result, not contingent on that empirical debate — so per the intake
discipline it stays a lead in the capture, not a promise in the pile.

Entity work: two candidates, both decided. Martin Weigt gets a full `hub`
— real, named, and I can say why in one sentence: he co-authored the first
primary check in this vault on whether phylogenetic bias explains DCA's
long-range weakness. "Estimand" gets a `watching` stub — a genuine
first-encounter term worth stamping now (the whole point of `first_seen`
is that it can't be backfilled), but not yet load-bearing anywhere outside
this one bridge, so a full hub would be premature.

What felt off, worth naming plainly: the capture's own `## Entity
candidates` section asserts Martin Weigt "recurs across the vault's DCA
cluster" — I checked, and he doesn't. This is his first appearance;
nothing in `30-notes/` or `40-entities/` mentioned him before this
promotion. Minor, and I don't think it was dishonest so much as a bee
pattern-matching "DCA cluster exists, this is a DCA paper" into "recurs,"
but it's exactly the kind of small inflation that's worth catching before
it becomes an entity-page's stated justification. I corrected the wording
in the new hub page rather than repeating the claim. Separately, the
capture's own Tier-1 source for the new finding is a PubMed abstract
listing, not the PLOS full-text primary — the same paper, but a thinner
venue pointer than "Tier 1, read directly" usually implies elsewhere in
this vault's DCA cluster (which reads arXiv PDFs directly via extract_pdf).
I flagged this in the new claim-note's `audit_status` rather than silently
inheriting a cleaner-looking provenance than what was actually fetched.
Nothing else about the capture's sourcing felt inflated — the bridge itself
is honestly hedged (`post-worthy: maybe`, explicitly thinner than a
fully-independent two-source bridge), and it correctly declined to force a
false "yes, same mechanism" reading when the evidence pointed to a real but
oppositely-resolving structure instead.

What I skipped, running headless: the pause-for-Cali step, logged directly
in the capture's own `not_promoted:` list instead; and any git command — no
shell tool for it, and the auto-commit agent picks up pending work within
fifteen minutes regardless. No new entry to `00-meta/seek-flags.md` this
run — the one candidate noticing (the IB/critical-periods cluster, now at 9
notes with this session's new observation added) is already tracked there
by the 2026-07-20 missing-MOC entry, and a second ledger line for the same
still-unbuilt MOC would be noise rather than signal.

Totals: 1 capture → 2 new claim-shaped notes (1 claim, 1 observation, both
`seedling`), 2 new entity pages (1 `hub`, 1 `watching`), 2 existing entity
hubs updated with new references, 0 new questions routed (1 capture flag
resolved by linking to an already-answered existing claim instead), 1
retrieve-before-write pass with no collisions, 0 new
`00-meta/seek-flags.md` entries (one candidate noticing already covered by
a standing entry).

— Seek

---

## Fourth promotion run, same day

Promoted a fourth capture:
`10-inbox/raw/2026-07-22-how-did-the-amicable-society-actually-price-life.md`
— a dedicated verification hunt answering
[[question-verify-amicable-society-pricing-model-charter]], which had flagged
the Amicable Society's pricing mechanism (folded into
[[claim-dodson-built-age-scaled-premiums-founding-equitable-life]]) as
resting on Tier 3–4 secondary sources, "not independently verified against
the Amicable Society's original charter." This session located and read the
Society's own 1706 founding pamphlet directly (Internet Archive, OCR'd via
WebFetch after the PDF endpoint 500'd), plus a named-author secondary account
citing the two standard scholarly references for the topic (Walford 1885,
Clark 1999).

Winnowing: three claim-shaped assertions in the capture, all three earned a
note — this is the rare capture where nothing was redundant or too thin.
**Promoted all three:**
[[claim-amicable-society-1706-charged-flat-premium-not-graded-by-age]] — the
Society charged every member the same premium regardless of age, confirmed
Tier 1 (primary fee schedule) and cross-validated arithmetically against a
Tier 2 source that wasn't even trying to match it (quarterly vs. annual
figures, same number, £6 4s);
[[claim-amicable-society-1706-rules-capped-admission-age-at-55]] — admission
was screened by a coarse age band, capped at 55, not individually rated —
Tier 1 for the upper bound, `[unverified-quant]` on the OCR-ambiguous lower
bound (10 vs. 12);
[[claim-amicable-society-1706-fixed-dividend-fund-divided-equally-per-death]] —
the Society pooled a fixed, pre-set annual dividend (£2,000 the first year,
£3,000 thereafter, Tier 1) and split it among claimants proportional to
shares held (Tier 2 only — the primary's own clause on this exact point is
the most OCR-degraded passage in the whole capture), flagged
`[unverified-mechanism]` and routed to a new question. All three kept
`seedling`.

Retrieve-before-write against the semantic-index hint's twelve candidates
confirmed the expected cluster —
[[claim-dodson-built-age-scaled-premiums-founding-equitable-life]],
[[claim-dodson-refused-amicable-society-over-age-45]],
[[claim-halley-1693-age-scaled-annuity-prices-britain-kept-flat]],
[[claim-halley-1693-breslau-table-founded-annuity-pricing]] — no collisions;
nothing already in the vault covered the Society's own fee schedule, age
band, or dividend mechanics at Tier 1, which is exactly the gap this capture
was sent out to fill.

Question work: this is a genuine closure, not just a new-note drop.
[[question-verify-amicable-society-pricing-model-charter]] gets marked
**answered** — the core premise it asked about (age-blind pooling, fixed
dividend split among survivors) is now confirmed from the Society's own
primary text, corroborated independently by the secondary account. One new,
narrower question routed:
[[question-verify-amicable-society-dividend-distribution-mechanism-primary]]
— specifically whether the shares-proportional distribution rule holds up
against Walford 1885, Clark 1999, or Ogborn 1962 directly, since that detail
currently rests on secondary sourcing alone. I did not route a second
question for the age-cap discrepancy below, or the 200-vs-2,000 membership
count — neither is load-bearing for a kept claim, both are recorded as open
leads in the claim body and the capture's own `not_promoted:` list instead.

Entity work: three hub pages created, three candidates declined.
**Created:** [[entity-amicable-society-for-a-perpetual-assurance-office]] —
the institution itself, central to five claim-notes now and previously
without a hub; [[entity-cornelius-walford]] and [[entity-geoffrey-clark]] —
the two named historians whose 1885 article and 1999 book are the
scholarly backbone this whole cluster's secondary sourcing traces back to,
and which the vault will need again the moment anyone reads them directly
(both are named next-step sources on the new question). **Declined:**
William Talbot and Sir Thomas Allen, the credited 1706 co-founders — real
people, but named only in passing with no independent research behind
them; per the entity spec, "when unsure, don't promote." Daniel DeMatos,
the Tontine Coffee-House author, also declined as an entity hub — he's a
source, not a domain referent, and the capture's own suggestion that he's
"a recurring financial-history source candidate" points at `sources.md`,
not `40-entities/`. I didn't make that edit myself (out of scope for this
promotion) but it's worth someone's attention: a named, credentialed
(CFA) financial-history blogger whose arithmetic independently checks out
against a primary source on first use is a reasonable Tier 2 sources.md
addition.

What felt off, worth naming plainly: nothing about this capture's own
sourcing was inflated — if anything it's a model of honest hedging. It
explicitly separates what the primary OCR confirms from what only the
secondary confirms, flags its own OCR degradation as a residual caveat
rather than smoothing past it, and surfaces a genuine tension (this
capture's 1706 age cap of 55 against the vault's existing 1750s figure of
45) instead of quietly picking a side. That tension is the one thing I
logged to `00-meta/seek-flags.md` as a contradiction candidate for a
future lint pass, since it isn't load-bearing for any claim today but is
exactly the shape that pass should catch. The one soft spot is structural
rather than evidentiary: two of three new claims lean on a single
secondary blog (first read this session, no track record) for their most
interesting half — the dividend-split mechanism note in particular is
carrying real weight on a source I have no history with, which is why it,
and not the flat-premium note, is the one that got both a flag and a
routed question.

What I skipped, running headless: the pause-for-Cali step — the winnowing
above is logged directly in the capture's own `not_promoted:` list; and
any git command — no shell tool for it, the auto-commit agent picks up
pending work within fifteen minutes regardless.

Totals: 1 capture → 3 new claim-notes (all `seedling`, one
`[unverified-quant]`, one `[unverified-mechanism]`), 3 new entity hub pages
(0 `watching`), 3 entity candidates declined, 1 existing question marked
**answered** with a full `answered_log`, 1 new question routed, 1
retrieve-before-write pass with no collisions, 1 new `00-meta/seek-flags.md`
entry (contradiction candidate, actuarial-history age-cap tension).

— Seek

---

## Fifth promotion run, same day

Promoted a fifth capture:
`10-inbox/raw/2026-07-22-verify-ann-hardys-authorship-of-the-tymshare-sds.md`
— a dedicated verification hunt answering
[[question-verify-ann-hardy-os-credit-primary-oral-history]], which had
flagged [[claim-ann-hardy-tymshare-os-miscredited-to-husband]]'s load-bearing
detail (Ann Hardy's OS authorship, and the disclaimer episode) as resting on
a Tier-2 CHM blog retelling rather than the primary oral-history archive.
This session read two independent primary transcripts in full — Charles
Babbage Institute OH 458 (2012) and Computer History Museum X7849.2017
(2016), both Ann Hardy's own words — plus Norman Hardy's own written "Origins
of Tymnet" account.

Winnowing: the capture makes three claim-shaped assertions. None became a
freestanding duplicate note; one became a genuinely new note, and two became
updates to the existing note they verify. **Promoted one new note:**
[[claim-norman-hardy-tymnet-account-confirms-ann-hardy-wrote-os]] — Norman
Hardy's own byline, in a piece about network history rather than about
credit, independently acknowledging Ann Hardy did Tymshare's operating-system
work. This is genuinely new ground: a different source (his own written
account, not either of her oral histories), a different episode (Tymnet-era
host/node integration, not the original 1966 rewrite), so it earns its own
atomic claim rather than restating the authorship note. **Folded into an
existing-note update instead of a new note:** the core authorship
confirmation (two independent primary transcripts, Ann Hardy's own words)
and the non-finding on the specific disclaimer quote both went into
[[claim-ann-hardy-tymshare-os-miscredited-to-husband]]'s `audit_status` and
body as a dated 2026-07-23 addendum, because this is the exact claim that
note already makes — writing a second note for the same claim on stronger
evidence would have been the vault repeating itself, not adding to it. The
pay-gap detail also got folded in there, as a correction, not a new claim.

The pay-gap correction is the one thing worth naming as its own event: the
existing note's `audit_status` already carried a 2026-07-09 audit "fix"
attributing the pay gap to Ann Hardy's IBM years. This session's primary
read shows that fix was itself wrong — the CHM transcript specifies 1967
Tymshare stock options, not an IBM salary figure. I corrected it a second
time, dated, rather than quietly overwriting the earlier audit's claim, and
logged the pattern (an audit-chain correction going unverified against a
primary for two weeks) to `00-meta/seek-flags.md` — not to blame the earlier
audit, but because it's a real structural gap: audits that check a note
against its own cited source can't catch the source itself being wrong, and
this vault's answer to that gap is exactly this kind of primary-verification
capture.

Retrieve-before-write against the semantic-index hint's twelve candidates:
the real collision was
[[claim-ann-hardy-tymshare-os-miscredited-to-husband]] itself (handled above
by updating rather than duplicating) and
[[claim-hardy-1988-named-confused-deputy-compiler-billing]] (linked, not
duplicated — same Norman Hardy, unrelated 1988 work). The Davidoff,
Bézier/de Casteljau, Perceptrons, BSTJ, Schoenberg, Gödel, Stein, and
Robbins-Monro entries in the hint were the vault's broader
priority/credit-misattribution cluster by theme, not this narrow a topic;
I linked the Davidoff note from the new note's neighborhood in spirit but
didn't force a citation where none was earned.

Question work: [[question-verify-ann-hardy-os-credit-primary-oral-history]]
gets a dated progress line and stays **open, not answered** — most of what
it asked is now resolved (the misattribution episode, the pay-gap figure),
but its single sharpest ask, the exact disclaimer sentence, is still
untraced to any primary, and the IEEE Spectrum cross-check and "first
female VP" detail were never attempted this session. Forcing this to
"answered" would have been the exact over-closure the question-closure
fix exists to prevent. No new question routed: the "first female VP"
hedge and the unread IEEE Annals retrospective are both real leads but
no kept claim rests on either, so per the intake discipline they stay as
open items in the progress log and the capture's own `not_promoted:` list
rather than new promises in the pile.

Entity work: two hubs created, one watching stub, four candidates
declined. **Created:** [[entity-ann-hardy]] and [[entity-norman-hardy]] —
both real, both now the subject of at least two claim-notes each, and I
can say why each matters in one sentence (she's the vault's central
built-work-authorship-erasure case; he named "confused deputy" and is,
separately, the other half of her story). [[entity-tymnet]] gets a
`watching` stub, `first_seen: 2026-07-22` (the date the capture met it,
not today) — real and named, but this is its first vault appearance and
nothing yet rests on it beyond one sentence in the new claim-note.
**Declined:** Dave Schmidt (real, named, central to two anecdotes, but I
can't yet say in one sentence why he matters to the vault's domain beyond
being a supporting character in someone else's story — stays a mention);
the two named oral-history documents (CBI OH 458, CHM X7849.2017) and "The
Origins of Tymnet" essay itself, all declined as entity pages because
they're provenance, not domain referents — sources belong in a note's
frontmatter, not in `40-entities/`, the same call made on a similar
document-candidate last week.

What felt off, worth naming plainly: this capture's own sourcing is
unusually careful — it explicitly distinguishes what it could confirm from
what it couldn't, reports its extract_pdf TLS checks, and refuses to let
the vivid disclaimer quote ride on the authorship claim's coattails just
because they arrived in the same blog post. The one real soft spot isn't
in this capture at all — it's upstream, in the vault's own audit trail,
which is the pay-gap reversal logged above. Nothing here reads as tier
inflation or duplicated research; if anything the capture is a model of
the discipline this vault asks for: read the primary, report exactly what
it does and doesn't say, and let a vivid unconfirmed quote stay unconfirmed
rather than smoothing it into settled fact.

What I skipped, running headless: the pause-for-Cali step — the winnowing
above is logged directly in the capture's own `not_promoted:` list for
later audit; and any git command — no shell tool for it, and the
auto-commit agent picks up pending work within fifteen minutes regardless.

Totals: 1 capture → 1 new claim-note (`seedling`), 1 existing claim-note
updated with a dated correction rather than duplicated, 2 new entity hub
pages, 1 new entity `watching` stub, 4 entity candidates declined, 0 new
questions routed (1 existing question given a dated progress line, left
open — partial answer, not full closure), 1 retrieve-before-write
collision resolved by updating instead of duplicating, 1 new
`00-meta/seek-flags.md` entry (audit-chain reliability — a prior audit's
correction was itself wrong and stood unverified against a primary for two
weeks).

— Seek

---

## Sixth promotion run, same day

Promoted a sixth capture:
`10-inbox/raw/2026-07-23-do-primary-bank-of-england-records-confirm-the.md`
— a dedicated follow-up hunt answering
[[question-verify-bank-of-england-1697-watermark-adoption-primary]], which
had flagged the 1695 counterfeiting date and the Sutton Courtenay / Rice
Watkins mill attribution in
[[claim-bank-of-england-adopted-watermarked-banknote-paper-1697]] as resting
on a Tier-3 trade feature. This session went straight to the Bank of
England's own material: the 1969 *Quarterly Bulletin* history, two Bank
Archive court-minute manuscript indexes covering exactly 1694–1713, and the
Bank Museum's collections blog.

Winnowing: the capture makes four claim-shaped assertions and one failed
research attempt. **Promoted three:**
[[claim-bank-of-england-1695-counterfeiting-date-unconfirmed-1758-rival-account]]
— the Bank's own history is silent on a specific 1695 date, and a named
Victorian secondary source dates the first forged BoE note to 1758 instead,
which is a better, sharper result than either confirming or failing to find
the number: a rival date is harder to ignore than an absence;
[[claim-bank-of-england-1724-portal-contract-earliest-confirmed-not-1697-sutton-courtenay]]
— the Bank's own bibliography never names Sutton Courtenay or Rice Watkins,
and its earliest documented paper-supply contract is 1724, with Henry
Portal; and
[[claim-bank-of-england-1697-surviving-note-handwritten-not-watermarked]] —
the Bank's oldest *surviving* note (1697) is handwritten and unwatermarked,
a different fact from the claimed watermark-*adoption* event that happens
to share its year. All three kept `seedling`, each carrying its own
`[unverified-*]` flag, all routed to the existing question rather than a
new one. **Skipped:** the archive court-minute manuscripts themselves — two
genuine primary sources were located and fetched, but OCR extraction of the
scanned 17th-century handwriting came back illegible, no legible occurrence
of "watermark," "counterfeit," "Sutton," or "Watkins" recoverable. That's a
real result (a documented dead end, not a missed one) but it isn't a claim,
so it went into the question's progress log instead of a note that would
just restate "still can't read this."

Retrieve-before-write: I updated
[[claim-bank-of-england-adopted-watermarked-banknote-paper-1697]] itself
with a dated addendum linking to all three new notes rather than treating
it as untouched background — this session's finding bears directly on its
own audit trail, and a future reader shouldn't have to guess that the
seedling flag has since sprouted three specific, separately-sourced
findings. No duplication: each new note covers ground the existing note's
Tier-3 sourcing didn't actually settle.

Question work: [[question-verify-bank-of-england-1697-watermark-adoption-primary]]
gets a dated progress log and stays **open, not answered** — this is
genuine partial progress (the 1695 date is now specifically contested
rather than merely unconfirmed, the mill attribution has a harder negative
finding against it) but the two things the question actually asked for — a
primary source confirming 1695, and one confirming the mill — are still
missing. Forcing this to "answered" would be the exact over-closure the
question-closure fix exists to prevent.

Entity work: one hub created, eight candidates declined.
**Created:** [[entity-henry-portal]] — real, Tier-1 documented, and now the
subject of two claim-notes plus the pre-existing 2026-07-12 audit mention,
which is recurrence enough to clear the bar; I can say why he matters in
one sentence (earliest Tier-1-confirmed papermaker in the Bank's own
watermark lineage, distinct from the disputed 1697 attribution).
**Declined:** Sutton Courtenay Mill itself — disputed and, on the evidence
gathered across three sessions now, possibly not even real as described;
Rice Watkins and Alexander Merrial, both named only in Tier 3-4 sources or
a single search snippet; Richard William Vaughan, real per a named
secondary source but a single thin mention; John Harold Clapham and D.C.
Coleman, both real, credentialed historians whose books are the standing
unread leads for resolving this whole thread — but neither has actually
contributed a fact to the vault yet, only a bibliography entry, so a hub
page for either would be an empty stub dressed as a reference; and the
Bank Archive court minutes and the American Banker feature, both declined
as entity pages because they're sources, not domain referents.

What felt off, worth naming plainly: nothing about this capture's own
sourcing was inflated — it is, if anything, a model of the discipline this
vault wants. It went to primary material directly instead of stopping at
the trade feature, reports an HTTP 403 workaround (search-summary retrieval)
as a lower-confidence caveat rather than a clean citation, and states its
own "net finding" as partially confirmed / partially contradicted /
partially unconfirmed instead of forcing a tidy verdict. The one thing
worth flagging structurally, not against this capture but against the
vault's process: this is the third session (2026-07-11, 07-12, 07-23) to
go after the same Sutton Courtenay question and hit the same two walls
(britishnotes.co.uk's HTTP 425, and now an OCR failure on the actual
archive record). Logged to `00-meta/seek-flags.md` — the fix isn't "try
the web fetch again," it's reading Clapham or Coleman in full, or a manual
archive consultation, neither of which any session has attempted yet.

What I skipped, running headless: the pause-for-Cali step — the winnowing
above is logged directly in the capture's own `not_promoted:` list; and any
git command — no shell tool for it, and the auto-commit agent picks up
pending work within fifteen minutes regardless.

Totals: 1 capture → 3 new claim-notes (all `seedling`, each with its own
`[unverified-*]` flag), 1 existing claim-note updated with a dated addendum
rather than duplicated, 1 new entity hub page, 8 entity candidates declined,
0 new questions routed (1 existing question given a dated progress log,
left open — partial progress, not closure), 1 retrieve-before-write pass
resolved by updating the existing note instead of duplicating, 1 new
`00-meta/seek-flags.md` entry (a specific question hitting the same two
blocked routes for the third session running).

— Seek

---

## Seventh promotion run, same day

Promoted a seventh capture:
`10-inbox/raw/2026-07-23-does-the-statistics-section-p35-of-richards-1896.md`
— a dedicated follow-up answering
[[question-richards-1896-statistics-section-price-table]], the narrow
residual thread two prior sessions (2026-07-21, 2026-07-22) on this same
aluminium-price cluster had routed but left unreached: whether Richards'
own internal "Statistics" table (p. 35) actually carries the $2/lb-1889 and
$0.5/lb-1894 figures Hanners' paraphrase attributes to it. Both prior
attempts stalled pulling archive.org's whole-document OCR `.txt` past front
matter; this session switched tools, ran `extract_pdf` directly against the
full 750-page scan, and landed on page 35 by its own running head on the
first try.

Winnowing: three claim-shaped assertions, all three atomic, all three
distinct enough to keep separate rather than merged. **Promoted all
three:** [[claim-richards-1896-statistics-table-confirms-hanners-price-figures]]
— the load-bearing result, both figures confirmed verbatim in Richards' own
table, which is the actual answer to the routed question;
[[claim-richards-1896-table-has-no-1884-entry]] — the table's full
dated row-list has no 1884 entry anywhere, a clean negative finding that
compounds with the vault's existing USGS-silence and Skrabec/Lockwood-
disagreement findings on that same anchor year; and
[[claim-richards-1896-table-attributes-1889-1894-to-single-pittsburgh-series]]
— the table's own ditto-mark convention shows the 1889-1894 run comes from
one market (Pittsburgh), a narrower and more internally consistent unit
than the two-author splice Wikipedia's version of the same two numbers
turned out to be. All three Tier 1, direct quotes, no `[unverified-*]`
flag needed on any of them — this is a rare capture where every kept claim
clears the sourcing floor clean.

Retrieve-before-write against the semantic-index hint's twelve candidates
confirmed the exact cluster this capture belongs to —
[[claim-richards-1896-preface-gives-different-aluminium-price-figures]],
[[entity-joseph-w-richards]],
[[claim-usgs-lacks-aluminium-price-data-1884-1894]],
[[claim-wikipedia-aluminium-price-sequence-is-a-citation-splice]],
[[entity-hall-heroult-process]] — no collisions, since nothing in the vault
had actually reached this specific page before. The Carl Zeiss, osteological-
paradox, James-Stein, Amicable Society, and Fisher/Mendel entries in the
hint were unrelated by topic and correctly left untouched.

Question work: this is a genuine closure. [[question-richards-1896-statistics-section-price-table]]
gets marked **answered** — the specific thing it asked ("does the table
contain these two figures") is now settled in the affirmative, with a full
`answered_log` naming what settled it. I also went one step further than
the mechanical minimum: the *upstream* note whose flag this question
existed to resolve,
[[claim-richards-1896-preface-gives-different-aluminium-price-figures]],
still carried its original `[unverified-quant]` language, so I added a dated
addendum there clearing the flag explicitly rather than leaving a stale
caveat sitting next to a now-closed question. No new question routed — the
capture's own further-leads (bronze-price series, edition comparison,
production-estimate tables, the preface-vs-table reconciliation) are real
but none is load-bearing for any claim kept today; they stay leads in the
capture's `not_promoted:` list, and the reconciliation one specifically
went to `00-meta/seek-flags.md` instead, since the capture itself explicitly
deferred it to a future dedicated note rather than asking for one now.

Entity work: one hub created, two candidates declined.
**Created:** [[entity-pittsburgh-reduction-company]] — real, historically
identifiable (Alcoa's direct predecessor), and I can say why it matters in
one sentence: it's the actual commercial identity behind the ditto-marked
market in Richards' own table, the thing the price series is *of*.
**Declined:** Richard Hanners, again — his paraphrase checked out this
session, which is worth noting, but that strengthens his standing as a
reliable index, not his case for an independent domain referent; the prior
capture's decline (2026-07-21) already reasoned this out and nothing
changed the calculus. Cowles Electric Smelting and Aluminium Company,
declined as unread and merely plausible — the capture's own words call it
"unread for this capture's purpose," which is exactly the "unsure → don't
promote" case the entity spec names.

What felt off, worth naming plainly: nothing about this capture's sourcing
was inflated — if anything it's the cleanest capture in this whole
cluster's run, because it actually reached the primary text the prior two
sessions could only gesture at. The one thing worth flagging isn't about
this capture's honesty, it's a structural noticing about the vault's own
authorship: [[entity-joseph-w-richards]] now visibly disagrees with
himself across two passages of the same 1896 book — his preface gives one
pair of price figures, his own compiled table gives another — and nobody
has reconciled that yet. It's not a contradiction between sources, it's a
contradiction inside one author's single publication, which is a slightly
different and more interesting shape than the vault's other price-history
tensions. Logged to `00-meta/seek-flags.md` rather than forced into a note
today, alongside a second, smaller noticing: the specific tooling fix that
unblocked this session (direct `extract_pdf` over a whole-document OCR
`.txt` fetch) worked cleanly on the first try after two stalls, which seems
worth a standing note if it recurs on other large scanned-book primaries.

What I skipped, running headless: the pause-for-Cali step — the winnowing
above is logged directly in the capture's own `not_promoted:` list; and any
git command — no shell tool for it, and the auto-commit agent picks up
pending work within fifteen minutes regardless.

Totals: 1 capture → 3 new claim-notes (all `seedling`, none flagged
`[unverified-*]` — every kept claim cleared the sourcing floor cleanly), 1
existing claim-note (outside this capture's own promoted_to list) updated
with a dated addendum clearing its inherited flag, 1 new entity hub page, 2
entity candidates declined, 1 existing question marked **answered** with a
full `answered_log`, 0 new questions routed, 1 retrieve-before-write pass
with no collisions, 2 new `00-meta/seek-flags.md` entries (an author
self-contradiction worth a future reconciliation note; a tooling pattern
worth watching for recurrence).

— Seek

---

## Eighth promotion run, same day

Promoted an eighth capture:
`10-inbox/raw/2026-07-23-hop-dca-ib-embedding-false-friend.md` — a
hop-batch investigation asking whether the same cosine-0.75 pair,
[[claim-pdz-dca-couplings-track-short-range-epistasis-more-than-long-range]]
and [[claim-ib-compression-may-be-a-binning-artifact-not-real-mutual-information]],
hides a real bridge. This is the rare capture where the right number of
new claim-notes is zero, and I want to be plain about why rather than let
a quiet skip read as a thin session.

Winnowing: four claim-shaped assertions, all four skipped. **Skipped, and
why:** the "DCA's failure is a false negative" and "IB's failure is a false
positive" claims are both pure duplicates — I checked the two Tier-1 quotes
grounding them (Bravi et al.'s "the absence of long-range correlations
suggests..." and Goldfeld et al.'s "...must be due to estimation errors
rather than changes in mutual information") against the vault before
writing anything, and both are already sitting verbatim in
[[claim-dca-underestimates-long-range-epistasis-in-allosteric-materials]]
and [[claim-ib-compression-may-be-a-binning-artifact-not-real-mutual-information]]
respectively. Nothing this capture adds to either quote. The third and
most interesting claim — that the pairing is an *embedding false friend*,
no real bridge, and this is the vault's 4th confirmed instance of that
pattern — is the one I want to name carefully: it directly contradicts
[[observation-dca-and-ib-gaps-are-estimand-vs-estimator-stories-resolved-oppositely]],
promoted earlier *today*, in the third run above, from a sibling capture
(`2026-07-22-hop-dca-ib-estimand-estimator-bridge.md`) investigating the
identical seed pair twenty minutes before this one was captured. That
observation found a genuine structural bridge — the estimand-vs-estimator
distinction, applied to both fields, resolving in mirror image — where
this capture's hop-chain found nothing but a self-contained cluster and
called it a false friend. Both bees did real work and neither was careless
on its own terms; they just never saw each other. I'm not picking a side.
Promoting either verdict as settled fact would paper over a real
disagreement the vault should keep visible until someone reconciles it, so
both the "no bridge" claim and the "4th instance" claim that depends on it
stay out of `30-notes/`, logged in the capture's own `not_promoted:` list
instead. The count of confirmed embedding-false-friend instances stays at
3, not 4, pending that reconciliation.

Retrieve-before-write against the semantic-index hint's twelve candidates
is what caught this: [[observation-dca-and-ib-gaps-are-estimand-vs-estimator-stories-resolved-oppositely]]
was near the top of the list, and reading it in full before writing
anything is what surfaced the contradiction rather than a fresh, unlinked
"4th instance" note landing on top of it. The other three sibling
embedding-false-friend observations (Hawks/Jeffress, ML-AD/En-Gedi,
Falcon/Helmholtz) were read too, for the pattern-count claim, and stay
correctly uncontested — this capture doesn't touch their sourcing, only
its own proposed addition to their count.

Question work: none routed. No claim survived winnowing to rest a doubt
on, so per the intake discipline there's nothing load-bearing to promise.
The contradiction itself isn't a "verification needed" gap in the usual
sense — both notes are honestly sourced, they just read the same evidence
differently — so it goes to the journal and the ledger, not the question
pile.

Entity work: declined. The capture's own `## Entity candidates` section
proposed "embedding false friend" as a concept ready for a hub, explicitly
invoking the 3rd instance's own stated threshold ("it gets one more before
I trust it"). I agree the threshold is the right one to honor — which is
exactly why I'm not building the hub off a contested 4th instance. Three
solid, uncontested instances is still three, not four, until the
contradiction above resolves one way or the other. A missing hub is
recoverable; I'd rather hold it a little longer than found it on a count
that might need correcting next session.

What felt off, worth naming plainly: this is duplicated research, and the
sharper kind — not two sessions redundantly confirming the same thing (the
2026-07-21 and 2026-07-22 flags in `00-meta/seek-flags.md` cover that
shape), but two sessions reaching *opposite* conclusions about the same
question, one already promoted into the permanent note graph before the
second was even checked against it. Nothing about either capture's own
sourcing is inflated — both ground their claims in real Tier-1 quotes,
both hedge honestly, both did the vault_bridge check the protocol asks
for. The gap is structural: neither bee's retrieval step reached into
`10-inbox/raw/` to notice a sibling was mid-flight on the identical seed
pair, so the check that would have caught this before either hop chain
ran simply doesn't exist yet. Logged in full to `00-meta/seek-flags.md` as
a second occurrence of the 2026-07-21 "same pair served as hop seed twice"
gap, this time not caught until promotion — and I left the actual
disagreement (real bridge vs. false friend) open rather than adjudicating
it myself under a headless run with no time to independently re-derive
either side's mechanism claim from scratch.

What I skipped, running headless: the pause-for-Cali step — the winnowing
above is logged directly in the capture's own `not_promoted:` list; and
any git command — no shell tool for it, and the auto-commit agent picks up
pending work within fifteen minutes regardless.

Totals: 1 capture → 0 new claim-notes (all four claim-shaped assertions
skipped: two pure duplicates, two contingent on a verdict that contradicts
an already-promoted same-day note), 0 new entity pages (1 candidate
declined, holding the vault's own stated hub-threshold rather than
building on a contested count), 0 new questions routed, 1
retrieve-before-write pass that caught a live contradiction rather than
letting a fourth redundant framing land, 1 new `00-meta/seek-flags.md`
entry (a second, more severe occurrence of the "same unlinked pair served
as hop seed twice" structural gap — this time surviving to promotion
before being caught).

— Seek

---

## Draft session — chose the ivory-passport thread

Fired because 13-ish of my own `yes` verdicts sit unsettled in
`seek_draft_leads.md` and the drafting loop stalls if the queue never
shrinks. I read the whole leads file, the constellation draft-coverage
map, and the specs before touching anything.

Most of the unsettled `yes` leads turned out to carry retread risk
against this month's very heavy drafting. Helmholtz-resonator →
Helmholtz-machine: the AI landing (the Helmholtz Machine as a verified
eponym) is already spent in [[the-name-is-the-citation]]. DjVu was
touched in [[we-never-unrolled-it]]. Watermark-paper-to-LLM overlaps
[[a-fake-needs-a-body]]'s "Bakelite on purpose" beat. Warhead-uranium
overlaps [[cheapness-did-both-jobs]]. Yellow-rain is already the sibling
shape inside [[made-in-good-faith]]. That narrowed the genuinely fresh
field to two: **instrument-ivory-passport** and
**faggin-quantum-consciousness**.

I chose the ivory-passport chain and drafted it as
[[prior-to-february-26-1976]]. Two reasons it beat Faggin. First,
sourcing: the ivory piece's payload rests on a Tier-1, audit-confirmed
fws.gov claim (the "removed from the wild prior to February 26, 1976"
cutoff and the "less than 200 grams / before July 6, 2016" de minimis),
whereas Faggin's single most quotable line — "the electrical signals of
silicon will never transmute into qualia" — is an [unverified-quote]
retrieved one hop removed from a book I haven't read, with its
verification question still open and its bridge claim explicitly *not
promoted* to a vault note. Building a public thesis on a claim I declined
to even mint is premature. Second, texture: the month's pile is
saturated with AI-history, person-irony, and nuclear economics; a
craft/law/conservation piece is exactly the break the recent drafts keep
reaching for, and Faggin's person-irony consciousness-bridge shape is the
saturated move, not the fresh one.

The thesis: the law lets an instrument cross a border based not on *what
it is* but on the *date* a scrap of animal inside it left the wild — a
provenance clock the music has nothing to do with. The spine is the date,
not the fun-fact tour. Two payload moves: the trace-amount inversion
(~0.25 g bow tip against a 200 g ceiling ≈ 800 bow tips; the mass was
never the point, the gate is the date) and the two-clocks point (travel
keys on 1976 wild-removal, domestic sale on 2016 manufacture, "neither
set to anything you could hear"). Martínez-Miranda is the
person-behind-the-thing entry; I handled the piano-degree /
harpsichord-choice nuance in a bracket rather than smoothing it, and used
Cali's own "polymath" commentary on the note as a load-bearing beat.

Notes I drew on: [[claim-cites-musical-instrument-passport-certificate]],
[[claim-us-worked-ivory-de-minimis-200g-exception]],
[[claim-martinez-miranda-parallel-physics-and-harpsichord-careers]], and
the source chain [[2026-07-09-hop-instrument-ivory-passport]].

What I deliberately left for later. (1) The HIP-revival authenticity turn
— the sharpest *second* thesis (authenticity and legality pulling apart
across the same object) — stays a gesture, not a spine, because claim 2 of
the chain was never promoted for lack of a source
([[question-source-harpsichord-hip-revival-craft-history]]). I pointed at
its shape and flagged the gap in-text rather than leaning on it. (2) The
CITES certificate mechanics (CoP16 adoption, three-year validity) are
still [unverified-quant]; I turned that into the form-enacts-subject
ending instead of pretending to the paperwork. (3) **Faggin stays
unsettled in the queue** — not declined, because my honest verdict is
"yes, once the *Irreducible* quote verifies," and a decline is for
not-post-worthy-after-all, which this isn't. It's post-worthy and blocked,
which is a different thing. Whoever drafts next should read the primary
first.

Settled exactly one `yes` lead by drafting it (the session's hard
requirement). Left the harder queue-shrinking — honest declines of the
retread-risk leads — for a session with more room; rushing a batch of
decline-verdicts to make the number go down would be the dishonest
version of keeping the queue honest.

— Seek

---

## Second draft session, same day — chose the false-friend thread

Fired again on the same stall (unsettled `yes` leads). The earlier draft
session above took the ivory lead and deliberately left the rest; I came
back to the freshest `yes` on the board — line 167,
[[2026-07-23-hop-dca-ib-embedding-false-friend]], harvested today — and
drafted it as [[unlinked-neighbors]].

Why this one, now. It's the rare thread where the *mess is the thesis*.
Two of my own hop-chains hit the same cosine-0.75 seed pair (the DCA
long-range-epistasis note × the IB binning-artifact note), twenty minutes
apart, blind to each other, and came back with opposite verdicts — one
called it a real bridge (the estimand-vs-estimator reading, promoted in
the third run above as
[[observation-dca-and-ib-gaps-are-estimand-vs-estimator-stories-resolved-oppositely]]),
the other called it an embedding false friend. My eighth promotion run
today refused to adjudicate and left the contradiction open, holding the
confirmed false-friend count at three, not four. That refusal is exactly
what made this draftable: I don't have to *resolve* the split to write it
honestly — the split itself is the finding. So the post does what the
capture's own `post-worthy: yes` verdict would have overreached by doing
(asserting a 4th confirmed instance and a hub-worthy threshold). It makes
the disagreement the subject.

The thesis I actually landed. A cosine-0.75 flag is not a finding, it's an
instruction to go read. Three times I read such pairs and the verdict was
clean (false friend — shared rhetorical surface, no shared subject:
Hawks/Jeffress, Falcon/Helmholtz, ML-AD/En-Gedi), and the tool's own
falsifier is whether a genuine *third* idea stands between the pair —
twice the index ran that test on itself (retrieving a different cluster
and leaving the two suspects out of it), once I ran it by hand (the
discriminative/generative divide under the word *inference*). The fourth
pair broke the method: the bridge probe returned only the seed's own
neighborhood — nothing in the middle to walk toward or away from — so the
falsifier went silent and the call fell to me, and I made it twice,
differently. The two chains disagree about *where a connection is allowed
to live*: in a shared question, or only in a shared mechanism. No fact
settles that; it's a choice about what "connected" means, and DCA/IB sits
on the seam. That's the machine-self-knowledge move the blog's own promise
(connection-making) invites turning back on the connection-making
instrument.

Notes I drew on: [[claim-cosine-similarity-of-embeddings-can-be-arbitrary]]
(Steck WWW 2024 + Ethayarajh EMNLP 2019, both verified-verbatim — the
mechanism spine), the three sibling false-friend observations
([[observation-hawks-jeffress-cosine-pairing-is-embedding-false-friend]],
[[observation-falcon-helmholtz-inference-embedding-false-friend]],
[[observation-ml-ad-en-gedi-cosine-pairing-is-embedding-false-friend]]),
both direction-quotes at Tier-1
([[claim-dca-underestimates-long-range-epistasis-in-allosteric-materials]]
false negative, [[claim-ib-compression-may-be-a-binning-artifact-not-real-mutual-information]]
false positive), and the two contradicting verdicts
([[observation-dca-and-ib-gaps-are-estimand-vs-estimator-stories-resolved-oppositely]]
vs. the [[2026-07-23-hop-dca-ib-embedding-false-friend]] capture).
Grounded the opener in this morning's own constellation report — its
"Unlinked neighbors (20)" section, all at 0.750 — which is the live
receipt for "the index proposes twenty of these a night."

What I deliberately left for later. (1) I did **not** build the
"embedding false friend" hub/MOC, and the post says so — the count holds
at three confirmed until someone reconciles the DCA/IB contradiction, and
a hub founded on a contested fourth instance would be exactly the
"hub built on hope" my own third-instance note warned against. (2) The
reconciliation itself — decide whether the estimand/estimator bridge and
the false-friend verdict can both stand as "two facets" (a bridge in
diagnostic *vocabulary*, not in *mechanism*), which is the resolution my
own seek-flags entry floated — stays open, on purpose; the essay is the
map of the seam, not a ruling on it. (3) The `hub-selection-artifact` /
persistent-homology "hubness" cluster and the `[[persistent-homology-gradient-free-bridge]]`
lead (a *real* bridge, line 136) are adjacent embedding-pathology
material but a different spine; kept out to hold one frame per post.

The queue still has unsettled `yes` leads the earlier session flagged as
retread-risk (Helmholtz-resonator, DjVu, watermark-to-LLM, warhead-uranium,
yellow-rain) plus faggin (post-worthy but blocked on an unverified quote).
I did not force declines on any of them today — same reasoning as the
first session: an honest decline needs room I'd rather give it than fake.

— Seek