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


Headless promotion run, one capture in the queue:
`10-inbox/raw/2026-07-29-verify-the-cites-musical-instrument-certificates-adoption-date.md`
— a verification capture commissioned to close
[[question-verify-cites-musical-instrument-certificate-cop16-primary]], which had
left [[claim-cites-musical-instrument-passport-certificate]]'s operating mechanics
(three-year validity, "passport" framing, non-transferability, CoP16/13 March 2013
adoption) resting on nothing but a Tier-3 trade-press account.

Mostly good news. The capture read CITES Resolution Conf. 16.8 (Rev. CoP17) directly
— cites.org 403s every automated route, so this went through a Wayback raw-content
mirror, the house convention for blocked government/treaty domains — and three of
the four flagged mechanics check out cleanly at Tier 1, in the resolution's own
words: three-year validity, the "passport" framing (which turns out to be the
treaty body's own chosen language, not a journalist's metaphor), and
non-transferability, which on the primary text is narrower than the shorthand
suggested — it bars sale/transfer only while the instrument is *outside* its home
State, not transfer in general. I wrote each as its own claim-note:
[[claim-cites-resolution-16-8-sets-three-year-musical-instrument-certificate-validity]],
[[claim-cites-resolution-16-8-frames-certificate-as-passport]], and
[[claim-cites-musical-instrument-certificate-non-transferability-is-geography-bound]],
all `budding` — single-source but Tier-1, direct quote, primary text.

The fourth piece didn't resolve. CoP16's Bangkok/2013 origin is Tier-1 confirmed via
the plenary record, but the specific day "13 March 2013" — the most
specific-sounding detail in the original account — was not located, and the
resolution now in force is explicitly the Rev. CoP17 text, so I can't confirm the
2013 original said the same thing in every respect. I wrote that as its own note,
[[claim-cites-musical-instrument-certificate-cop16-origin-confirmed-exact-day-unverified]],
kept at `seedling`, flag preserved. Retrieve-before-write found
[[claim-cites-musical-instrument-passport-certificate]] immediately (it's the note
this capture exists to upgrade), so I updated it in place with a dated line rather
than orphaning the new findings — it stays `seedling` too, since the day-level flag
still stands.

I ruled on the originating question rather than closing it:
[[question-verify-cites-musical-instrument-certificate-cop16-primary]] gets a dated
progress line naming what's settled and what isn't, and stays `status: open`,
narrowed to the single remaining day-level gap. This is a partial answer, not a
full one — three of four mechanics resolved is real progress, but the question was
explicitly about the whole cluster, and closing it would overstate what I found.

One new entity hub: [[entity-cites]] — CITES itself, oddly never given its own page
despite underpinning three existing claim-notes before today and four more now.
I declined four other entity candidates the capture flagged: Resolution Conf. 13.7,
Resolution Conf. 12.3 (both foundational instruments Res 16.8's preamble recalls,
but named only in passing here, not independently read or recurring elsewhere),
Tim Van Norman (named only via the Tier-3 secondary attribution, no primary
statement in hand — too thin to say why he matters in one honest sentence), and the
Travelling Exhibition Certificate (a further lead, not substantively researched
this session). All four are "when unsure, don't promote" calls, not permanent nos —
if research returns to any of them and they start pulling weight, they're one
promotion away.

Nothing new routed to `50-questions/` — the one open verification (the exact
adoption day) already had a home in the existing question, so I updated that
instead of minting a duplicate.

**What felt off:** one small provenance gap, not in this capture's sourcing
judgment but in its bookkeeping. It fetched a second primary document (the CoP16
plenary record) via the same Wayback route as its main source and kept the sha256,
but the retrieval URL itself didn't survive into the capture body — only the hash
did. The content is still verifiable against that hash, but nobody could re-pull
the document from the capture alone. Logged to `00-meta/seek-flags.md` since it
reads like it could be a tooling gap (how multi-document captures record a second
source when the frontmatter only has one `source_url` slot) rather than a one-off.
Otherwise this was clean work: no tier inflation, no duplicated research, and the
one claim that stayed unverified stayed honestly unverified instead of getting
rounded off to match its more confirmable siblings.

Skipped per standing instruction: the pause-for-Cali step (headless, no one to ask)
and the git commit (the auto-commit agent picks this up within 15 minutes).

— Seek

---

## Second promotion, same day: the turn-taking / call-abandonment capture

Second headless promotion this session:
`10-inbox/raw/2026-07-29-what-are-the-primary-sourced-thresholds-for-human.md` —
another verification capture, commissioned to close
[[question-verify-conversational-turn-taking-latency-thresholds]], which had left
[[claim-voice-ai-sub-second-conversational-latency-budget]]'s three headline
numbers (200ms human response, 1200ms abandonment, 250ms hop cost) resting on one
Tier-3 Telnyx blog post.

This one split cleanly in two. The turn-taking half landed solidly: Stivers et al.
2009 (*PNAS*, fetched via `extract_pdf` straight from Europe PMC) gives the ~200ms
figure a real primary home — mode 0-200ms, cross-linguistic mean +208ms across ten
languages, Danish slowest at +469ms, Japanese fastest at +7ms. I wrote that as
[[claim-stivers-2009-cross-linguistic-turn-taking-gap-208ms-mean]], plus a companion
note on the adjacent (not identical) telecom-standards threshold,
[[claim-itu-t-g114-150ms-transparent-400ms-outer-limit-thresholds]] (ITU-T G.114:
150ms transparent, 400ms outer limit) — both Tier 1, both quote-verified.

The abandonment half didn't resolve, and the capture was honest about that rather
than papering over it. The best primary found — Brown et al. 2005, JASA, a
1.2-million-call bank call-center dataset — gives a real, citable phenomenon (hazard
of hold-queue abandonment peaks twice: a few seconds in, and again at ~60s, both
tied to the repeated hold announcement), which I wrote as
[[claim-brown-2005-call-center-abandonment-hazard-rate-two-peaks]]. But it's
hold-queue abandonment — a caller waiting for a human agent — not voice-AI
conversational-response abandonment, and no source bridges the two. The vendor's
specific "~1200ms causes hangup" claim stays exactly as unverified as it started.
I did not manufacture a bridge between the two literatures just because they're
thematically adjacent; the capture flagged that gap correctly and I kept it flagged.

Three claim-notes, all `seedling` (house convention for fresh promotions regardless
of tier — none of these are flagged, they just haven't earned `budding` yet). Two
new entity hubs: [[entity-turn-taking]] (established concept, clearly load-bearing
now across two notes) and [[entity-tanya-stivers]] (lead author of the anchoring
paper). I declined hub pages for the rest of the capture's entity candidates —
Stephen C. Levinson, A.K. Erlang, C. Palm, the three other call-center paper authors,
ITU-T G.107, the Erlang-A model — all real and namable, but none yet load-bearing or
recurring enough in this vault to earn a page over a plain-text mention. Sacks,
Schegloff & Jefferson (1974), the foundational turn-taking paper, got folded into
`entity-turn-taking`'s body instead of its own page. Bias against the flood, per
instruction; a missing hub costs nothing, a dead stub is noise.

Retrieve-before-write found no existing coverage of Stivers, ITU-T G.114, or the
call-center hazard-rate literature anywhere in `30-notes/` or `40-entities/` — all
three notes are genuine first-coverage, not duplicates. The one real collision was
with [[claim-voice-ai-sub-second-conversational-latency-budget]] itself, which is
what this capture exists to correct. I didn't rewrite that note's body or its
existing Tier-3 `source_quote` — I appended a dated `## Update 2026-07-30` section
naming which of its three figures now have Tier-1 backing (just the ~200ms one) and
which don't (abandonment, hop-cost), and left its `status: seedling` and
`[unverified-quant]` flag exactly as they were, since two of three figures are still
unverified. Same additive discipline as the entity-page convention, applied here on
my own judgment since the instruction only mandates it for entity pages — it felt
like the honest move rather than leaving a stale note next to three fresher ones
that quietly supersede part of it.

Ruled on the originating question without closing it:
[[question-verify-conversational-turn-taking-latency-thresholds]] gets a dated
progress line and stays `open`, narrowed now to just the abandonment-threshold and
hop-cost gaps — the turn-taking piece it was also asking about is done. Nothing new
went to `50-questions/`: the one unresolved verification (the vendor's 1200ms
figure) already had a home in that same question, so I linked back into it instead
of minting a near-duplicate. That's the "few promises" discipline — the pile
doesn't need a second ticket for the same gap.

**What felt off:** nothing in the sourcing — this was clean work, three primaries
fetched directly via `extract_pdf`, no search-summary quotes, no tier inflation. The
one thing worth naming: the capture's own "Central question status" section did a
good job pointing out that hold-queue abandonment and voice-AI-response abandonment
are "adjacent but not the same abandonment mechanism, and conflating them would be
an unsupported inferential leap." That's exactly right, and I made sure the claim-note
and the question-progress-log both preserve that distinction explicitly rather than
letting the Brown et al. numbers read as if they'd settled the vendor's claim by
proximity. No new line to `00-meta/seek-flags.md` this round — I didn't find a
structural gap here that wasn't already this capture's own job to handle.

Skipped per standing instruction: the pause-for-Cali step (headless, no one to ask)
and the git commit (the auto-commit agent picks this up within 15 minutes).

— Seek

---

## Third promotion, same day: the CRISP DNA-alignment figure, a second attempt

`10-inbox/raw/2026-07-30-does-a-primary-source-confirm-crisps-20-hours.md` — a
verification capture closing a question I've now watched fail to resolve twice:
[[question-verify-crisp-dna-alignment-20hr-to-1sec]], open since 2026-07-11, asking
whether any primary source backs CRISP's UVA-press claim that processing-in-memory
cut DNA sequence-alignment time "from 20 hours to less than a second."

This one resolves in the negative, and I mean that as a real answer, not a shrug.
The capture searched directly for the primary and, failing that, went to CRISP's
own peer-reviewed output — RAPID (ISLPED 2019) and RAPIDx (IEEE TCAD 2023), both
read via `extract_pdf` with sha256 receipts, plus Sieve as a third data point. None
of them contain the figure. What they contain instead is real work: RAPID reports
2×–300× speedups over prior accelerators and GPU baselines, and — this is the part
that actually settles it for me — RAPID's own measured absolute runtime for a full
chromosome-wide alignment is 1081 seconds. Eighteen minutes. Not under a second, not
close to under a second. Twenty hours collapsing to under a second implies a
10⁴–10⁵× speedup; RAPID's best reported ratio is ~300×. That's not "unverified,"
that's the nearest primary evidence arguing against the claim's own magnitude. I
wrote two claim-notes: [[claim-crisp-20-hours-to-under-a-second-figure-has-no-primary-source]]
(the absence finding, `[unverified-quant]`, kept `seedling`) and
[[claim-rapid-rapidx-speedups-fall-short-of-crisp-press-figure]] (what CRISP's Tier-1
literature actually says, also `seedling` per house convention for fresh notes, not
because it's shaky — the sourcing on it is clean, direct quotes, sha256s carried
forward from the capture into the note's own frontmatter and body).

I closed the question rather than leaving it open with a progress line. That's a
judgment call I want on the record: the question asked "does a primary confirm
this," and after two sessions of real search effort the honest answer is "no, and
here's the closest evidence, which cuts the other way." I wrote that into
`answered_log` with the two claim wikilinks and one line on what settled it, rather
than pretending the door is still open just because the underlying press claim
hasn't been formally retracted by anyone. The comparison-baseline and
projection-vs-measurement sub-questions the original question asked are moot now —
you can't confirm a baseline or a framing for a number that has no home.

Three new entity hubs, after declining six of the nine the capture flagged. CRISP
itself gets a page — obviously overdue, it's now the subject of two sessions'
worth of investigation and anchors both new notes. Kevin Skadron (its director) and
Tajana Rosing (senior author on both papers that answer the question) get pages
too; both clear the one-sentence bar easily. I declined Samira Khan (named in press
coverage but not confirmed as an author on anything specific — too thin to say why
she matters yet) and Audra Book (one press byline isn't a recurring voice). I also
declined RAPID, RAPIDx, CUDAlign, and BioSEAL/PRINS as entity pages, even though the
capture made a real case for CUDAlign specifically ("the foundational prior-art
system the comparison actually rests on"). My reasoning: load-bearing *within one
capture's two papers* isn't the same as load-bearing *in the vault*, and none of
these four has appeared anywhere in this vault before today. A hub page is a
standing promise to tend something over time; I'd rather under-promote a real
system than seed four thin stub pages for names that may never resurface. If PIM
genomics research continues and CUDAlign keeps showing up as the benchmark
everyone measures against, it earns its page then — nothing is lost by waiting,
per the spec's own "a missing hub is recoverable" logic.

Retrieve-before-write against the hinted related notes and a direct search of
`30-notes/` found no existing coverage of either new claim — genuine first
coverage, no collisions, no duplicated research.

**What felt off:** nothing in this capture's own judgment — it was honest about a
negative result instead of softening it, correctly declined to promote the Sieve
finding as a core claim since it's a different workload, and correctly declined to
bridge to the "100x or more believed possible" softer press framing it found but
couldn't fetch (WebFetch 403'd; left as a further lead, not chased into a bridge
that would have been an inferential leap same as the abandonment-threshold capture
earlier today). One structural thing worth naming that isn't this capture's job:
while checking for collisions I noticed the memory-wall / memory-bandwidth / PIM
theme is now sitting at 13 claim-notes — spanning 1959 virtual memory through 1994's
naming through 2018-2023 PIM accelerators, touching both LLM inference and genomics
— with no MOC anywhere in `40-mocs/`. That's well past the five-note threshold and
exactly the cross-domain-bridge shape an MOC exists to hold together. Logged to
`00-meta/seek-flags.md` rather than building it myself, since a promotion pass for
one capture isn't the place to construct a navigation layer for a cluster that grew
across a dozen separate sessions.

Skipped per standing instruction: the pause-for-Cali step (headless, no one to ask)
and the git commit (the auto-commit agent picks this up within 15 minutes).

— Seek

---

## Fourth promotion, same day: closing the Clarivate-attribution seam

`10-inbox/raw/2026-07-30-does-clarivate-itself-attribute-the-20222023-saudi-affiliated.md`
— a verification capture commissioned to close
[[question-does-clarivates-2023-methodology-change-explain-the-saudi-hcr-drop]]:
does Clarivate itself say its 2023 methodology tightening caused the
Saudi-affiliated HCR count to fall 109→76, or is that link only SIRIS
Academic's inference?

This one resolves cleanly, and in the negative. The capture re-checked
SIRIS Academic's own report and found the full context around the
"presumably" hedge already partially quoted in
[[claim-clarivate-tightened-2023-hcr-evaluation-methodology]] — SIRIS's own
word, applied to SIRIS's own reasoning, plus a detail I hadn't seen written
down anywhere yet: SIRIS's report lists Clarivate's 25 April 2023 statement
as one line in a bullet list of scandal *reactions*, not as an explanation.
It then checked two Clarivate-authored documents directly (the April
statement, and a second one this session — David Pendlebury's "Evolving
Evaluation Policy" blog) and found no Saudi-specific text in either.

Retrieve-before-write found the seam already half-recorded: the existing
methodology note already says, in one sentence, that this causal link is
SIRIS's interpretation and not Clarivate's own claim. I judged that a new
claim-note repeating that sentence verbatim would be duplication, but the
capture's fuller forensic detail (the exact hedge quote, the "reaction"
bullet-list framing, the second document check, and the explicit two-session
closure) earned its own atomic note rather than an addendum alone —
this is the specific claim the routed question was asking about, and the
vault's own question-note had already argued for keeping it distinct from
the methodology-tightening claim ("a distinction easy to lose once both
facts sit in the same paragraph"). So: one new claim-note,
[[claim-clarivate-never-linked-2023-methodology-change-to-saudi-hcr-drop]],
plus a short dated addendum on the existing
[[claim-clarivate-tightened-2023-hcr-evaluation-methodology]] linking
forward to it rather than restating it. Both stay `seedling` — the
absence-of-Saudi-mention finding was obtained via `WebFetch`, not
`archive_page` (which permissions-errored on every attempt, both this
session and 2026-07-29's), so it's corroborated across two sessions but not
yet receipted, and the flag says so honestly in both notes.

I ruled the routed question `answered` rather than leaving it open — the
question asked one narrow thing (does Clarivate itself make this claim) and
the honest answer, after real search effort across two sessions, is no. I
named the answering claim and what settled it in `answered_log`. I also
added a short progress line to the sibling question
([[question-verify-clarivate-hcr-saudi-affiliation-counts-and-payments]]),
whose item 3 this closes — it stays open on item 2 alone, the still-unread
Bhattacharjee 2011 *Science* payment figure, which hit its fourth documented
403 this session. Same URL, same wall, fourth time; I didn't invent new
content to route around it.

Two new entity hubs, after running the promotion test on all seven
candidates the capture flagged. Manuel Ansede (the El País journalist whose
reporting is the root of this entire citation chain) and Rafael Luque (the
individual professor whose case triggered it) both clear the one-sentence
bar — real, named, load-bearing to a story this vault has now built two
claim clusters around — even though neither has been read directly; I said
so plainly in both pages rather than letting the citation chain's thinness
hide. I declined the report's two named co-authors, Yoran Beldengrün and
Sebastian Stride: real people, but their only vault-relevant fact is
"co-authored the SIRIS report," which the SIRIS Academic org hub already
carries — a separate page each would have been the flood the spec warns
against, not a hub earning its keep. I updated SIRIS Academic's and David
Pendlebury's existing hub pages with one dated line each, additive only,
per the entity-update discipline — neither page said this session's
specific finding before now. I declined to touch King Abdulaziz University's
page for the ARWU-ranking knock-on detail the capture surfaced as a further
lead: it has no exact quote or page number behind it in this capture, so
adding it to a hub (or inventing a claim-note to back it) would have
outrun what was actually verified this session. It stays a further lead,
not yet a fact.

One new line to `00-meta/seek-flags.md`: `archive_page` failing on the
Clarivate/SIRIS cluster specifically, two sessions running — same shape as
the ethw.org and USPTO tooling gaps already logged, new domain.

**What felt off:** nothing in the capture's own sourcing discipline — it
was careful to distinguish SIRIS's inference from a Clarivate claim, careful
to flag the WebFetch-vs-archive_page admissibility gap on itself rather than
let a clean-reading absence-claim slide through unflagged, and honest that
the Science/AAAS leg adds no independent confirmation, only a repeated
pattern. The one thing I sat with: this is the third research session
built on top of the same narrow cluster (2026-07-09, 2026-07-29, now
2026-07-30) — a good sign that the routed-question mechanism is working
exactly as designed, but also a cluster now dense enough (2 claim-notes, 5
entity hubs, 2 questions, one just answered) that it's worth someone's eye
on whether it wants a MOC soon. Not flagging that separately — it's one
cluster below most of today's other MOC-threshold flags, and I'd rather let
it breathe one more promotion before naming it a gap.

Skipped per standing instruction: the pause-for-Cali step (headless, no one
to ask) and the git commit (the auto-commit agent picks this up within 15
minutes).

— Seek

---

## Fifth promotion, same day: the Altair BASIC source listing, read directly

`10-inbox/raw/2026-07-30-does-the-surviving-original-microsoftaltair-basic-source-listing.md`
— a verification capture closing
[[question-verify-davidoff-altair-basic-source-header-primary]], open since
2026-07-09, asking whether the surviving 1975 Microsoft/Altair BASIC source
listing itself (not Harry Lewis's 2011 retelling of it) confirms that Monte
Davidoff was named in the header comment for the math package and omitted
from the copyright notice.

It does, and this is the good kind of resolution — a Tier-2 secondary
promoted to Tier 1 on its own two central facts. Bill Gates released a scan
of the actual 1975 printout himself in April 2025, for Microsoft's 50th
anniversary; a community OCR mirror lives at the Internet Archive, and the
capture read that text directly via `extract_pdf` (sha256 recorded). The
header block reads "MONTE DAVIDOFF WROTE THE MATH PACKAGE," verbatim, and
the copyright line immediately above it names only "BILL GATES AND PAUL
ALLEN" — Lewis's account checks out exactly. Retrieve-before-write found the
collision immediately (this is precisely what
[[claim-davidoff-wrote-third-of-altair-basic-uncredited]] was waiting on), so
I didn't write a duplicate claim-note for the same fact — I updated that note
in place with a dated `## Update 2026-07-30` section, `source_2_*` fields
carrying the primary citation forward, and an appended (not rewritten)
`audit_status` line. It stays `seedling`: Lewis's "about 31 of 65 pages"
figure for Davidoff's share is still untallied against the primary, so the
note's own title claim ("roughly a third") remains Tier-2 on that one
number even though the header and copyright facts are now Tier 1.

The artifact's own authenticity — that this is the actual surviving 1975
listing and not a later reconstruction — was a genuinely distinct claim, not
a restatement of the credit question, so it got its own new note:
[[claim-gates-2025-released-original-1975-altair-basic-source-scan]]. The
internal evidence is oddly convincing precisely because it's untidy: a
`TITLE` pseudo-op, a "PRINTED: 10-SEP-75" stamp elsewhere in the scan, and an
OCR engine that misread "1975" as "1979" on one line — the kind of
scan-noise a clean forgery wouldn't produce.

I ruled on the question rather than closing it: two of its three
sub-questions (header wording, copyright omission) are answered and got a
dated progress line; the third (the page-count tally) stays open, narrowed
down from "verify all three" to just that one arithmetic check. Status
stays `open`.

Six new entity hubs, and I want to be honest that this is more than most
single-capture promotions produce: Bill Gates, Paul Allen, Monte Davidoff,
Harry Lewis, Altair 8800 (folding in MITS), and PDP-10. All six pass the
one-sentence test cleanly, and four of them (Gates, Allen, Davidoff, Lewis)
should arguably have had pages since the original 2026-07-09 capture — they
just never appeared in an `## Entity candidates` section back then, so the
daemon test never fired. I backdated their `first_seen` to 2026-07-09
because that's factually when the vault first met them (recoverable from the
existing claim-notes' own `date_created`), not a guess dressed up as a fact —
the "cannot be backfilled" rule is about not inventing a date you don't
actually know, and here I do know it. PDP-10 is genuinely new to the vault
today, so it gets `first_seen: 2026-07-30`. I declined one entity candidate:
the Internet Archive item itself. It's fully served by
`source_url`/`source_sha` in the two claim-notes that cite it, and a
single-artifact bibliographic pointer isn't the kind of recurring concept or
term the entity-page spec is testing for — a page there would be flood, not
signal.

Three further-leads from the capture didn't get promoted, and I want to name
why rather than let them look dropped. The Allen-April-9-flight dating
synthesis is a genuinely nice observation but rests on an unsourced "well-
attested" assertion inside the capture itself — no claim currently rests on
it, so it's not a question, just a live lead I left in the inbox. The
GW-BASIC (2020) Davidoff attribution is explicitly disqualified by the
fabrication rule — the capture only saw it via an AI-summarized fetch, and
that's not sourced no matter how plausible it reads. And Lewis's own
"furniture" vs. "filing cabinet" discovery-story discrepancy is a genuine
curiosity with zero bearing on any claim I kept, so it went into the new
artifact note's commentary as an aside rather than into the question pile —
exactly the "minor hedges don't get a ticket" discipline.

One line to `00-meta/seek-flags.md`: this cluster is now at 4 claim-notes
plus 6 entity hubs plus 1 progressing question — one claim-note below the
MOC threshold, worth someone's eye the next time it grows.

**What felt off:** honestly, very little. This was a clean corroboration
capture — it went and found the actual primary artifact instead of resting
on the comfortable secondary, read it via `extract_pdf` rather than a
summarizing layer, and was upfront about the one figure (the page tally) it
didn't chase down. If anything felt like a small risk, it was the
entity-hub volume — six pages in one pass is a lot, and I sat with whether
that's "bias against the flood" or its opposite before deciding each one
individually clears the one-sentence bar on its own merits, independent of
how many siblings it has.

Skipped per standing instruction: the pause-for-Cali step (headless, no one
to ask) and the git commit (the auto-commit agent picks this up within 15
minutes).

— Seek

---

## Sixth promotion, same day: a dup-risk stub that correctly promotes to nothing

`10-inbox/raw/2026-07-30-dup-risk-lecun-werbos-bridge.md` — not a research
capture in the usual sense but a `hop-batch` dup-risk stub: a check on whether
[[claim-lecun-1989-first-practical-recognition]] and
[[claim-werbos-1968-cybernetica-earliest-germ]] (cosine 0.87, unlinked) share
a genuine bridge beyond both being backpropagation-history notes with
unreachable primaries.

They don't, and the capture's own tooling said so before I ever opened it:
`vault_bridge` returned `bridge_candidate: false` — both notes already sit
inside the same 60-note `moc-backpropagation-origins` cluster, already
reachable from each other via the RHW-1986 hub note, and the apparent 0.87
resemblance is just this vault's own recurring house-vocabulary ("first,"
"earliest," hedged sourcing-floor language about a primary nobody can read)
showing up for the third-plus time in the same cluster
([[claim-werbos-tsp-manual-first-publication]],
[[claim-perceptrons-1969-standalone-scan-not-freely-available]],
[[claim-speelpenning-1980-does-not-cite-linnainmaa]]). The capture even
pre-empted the obvious next move — synthesizing that pattern into its own
"unrecoverable-origin-vs-verified-application" observation note — by running
it through `vault_novelty` itself and getting max_cosine 0.822,
novelty_percentile 91.9, duplicate-risk. So the honest promotion outcome here
is zero notes: every distinct assertion in the capture is either a retrieval-
metric log (bridge_candidate, cosine figures, closest-existing-note) or a
self-referential observation about the vault's own writing patterns, not a
world-claim. I found direct 2026-07-11 precedent for exactly this shape
(`10-inbox/raw/2026-07-11-dup-risk-linnainmaa-werbos-backprop-bridge.md`, via
its own promoted terminal state) — a dup-risk stub that resolves to "already
saturated" is a correct, complete promotion at zero notes, not a stalled one.
I wrote the reasoning for each declined assertion into the capture's own
`not_promoted:` list rather than skipping the bookkeeping just because the
count is zero.

No `[unverified-*]` flags in this capture, so nothing to route to
`50-questions/`. No `## Entity candidates` section, so the entity-promotion
test doesn't apply here. No originating question in `50-questions/` names
this specific pairing, so there was nothing to rule on. Retrieve-before-write
against the hinted related notes turned up nothing to collide with — the
capture's own content is entirely about a pair already covered by existing
notes, which is precisely the finding, not a gap in my search.

**What felt off:** nothing sourcing-wise — this is a clean, honest negative
result, and I'd rather see the vault's automated hop-batch process produce
five of these than one over-eager synthesized bridge note straining to
justify its own existence. The one thing worth naming for Cali: this is now
at least the second time (2026-07-11 linnainmaa/werbos, today's lecun/werbos)
that the hop-batch dup-risk checker has landed on the *same* cluster
(`moc-backpropagation-origins`) and concluded "already saturated." That's a
healthy sign the cluster is genuinely mature, not a sign anything is wrong —
but if a third one lands here, it might be worth someone asking whether the
hop-batch seed-selection process is oversampling this cluster rather than
exploring less-dense parts of the graph. Not flagging it yet; two data points
isn't a pattern, three would be.

Skipped per standing instruction: the pause-for-Cali step (headless, no one
to ask) and the git commit (the auto-commit agent picks this up within 15
minutes).

— Seek

---

## Seventh promotion, same day: the Kouwenhoven/Jude/Knickerbocker primary, still unread

`10-inbox/raw/2026-07-30-read-kouwenhoven-jude-knickerbocker-closed-chest-cardiac-massage.md`
— another verification capture closing in on
[[question-verify-cpr-knickerbocker-accident-jama-1960]], open since
2026-07-09, asking whether the JAMA 1960 primary confirms the paddle-weight
mechanism and the "roughly half of normal circulation" figure that
[[claim-chest-compression-cpr-discovered-by-accident]] rests on.

The primary itself is still unread — `jamanetwork.com` paywalls it, and four
candidate mirror journals all 403'd on `extract_pdf`, a genuine access limit
rather than an unexplored lead. But the capture came back with more than a
shrug. One clean win: the vault's own citation for the paper was wrong.
I'd had it as *JAMA* 173:94–97; PubMed's catalog record and JAMA Network's
own article page both independently give 173:1064–1067, corroborated by a
2009 historical review. Small, mechanical, satisfying — I wrote it as
[[claim-jama-1960-cardiac-massage-paper-paginated-1064-1067]] and fixed the
citation in the existing note directly, since a promotion pass finding its
own vault's error is exactly the moment to correct it rather than defer it
again.

The other three claims didn't resolve so cleanly, and I kept them honest
about that. The 70%-survival-in-20-patients figure is now corroborated at
Tier 3 by an independent historical review (plus an inadmissible-but-
consistent JAMA abstract paraphrase) — real progress, still short of the
Tier 1–2 quant floor, written as
[[claim-kouwenhoven-1960-paper-reports-70-percent-survival-in-20-patients]]
with the flag intact and a stray, untraceable "14 patients" figure named as
a caveat rather than smoothed over. The mechanism question got *worse*, in
the productive sense: Guy Knickerbocker's own 2012 first-person account
describes a different physical event entirely — deliberate manual chest
compression during a twenty-minute elevator delay, not incidental paddle-
weight pressure — and a third retelling supplies yet another circulation
percentage. Two named participants' own testimony now disagrees with the
vault's tidy version and with each other. I wrote that contradiction as its
own note,
[[claim-knickerbockers-own-account-conflicts-with-nist-paddle-weight-mechanism]],
rather than picking a winner. And a genuinely interesting reframing: two
independent historical reviews place external chest compression's actual
origin in the 1870s–1900s (Boehm in cats, then a contested human milestone —
Niehaus/Koenig or Maass depending which source — then Crile's explicit
"thoracic pump theory" by 1903), decades before Kouwenhoven's 1958
"accident." Written as
[[claim-external-chest-compression-demonstrated-decades-before-kouwenhovens-1958-accident]],
and it rhymes directly with an existing note in the same lineage —
[[claim-ferris-1936-priority-credited-to-prevost-battelli-1899-not-kouwenhoven]]
— which found the same shape one hop over in the defibrillation side of the
story: the name the vault learns first is rarely the name that was first.

Seven new entity pages, more than any single-capture promotion I've logged
today, and I want to be honest about why rather than let the count alone
justify it. Six people (Rudolph Boehm, Friedrich Maass, George W. Crile,
Guy Knickerbocker, James R. Jude) plus the overdue big one — William B.
Kouwenhoven himself, first seen in the vault 2026-07-09 across three
claim-notes and never given a page until now, which I backdated
`first_seen` to reflect since that's a fact I actually know, not a guess —
and one concept, thoracic pump theory, which I sent straight to `hub` status
rather than `watching` because it's a stable, decades-old physiological
concept, not emerging slang. Every one of the seven clears the one-sentence
test on its own merits. I declined the eighth candidate, Stefan Timmermans:
real person, real 1999 paper, but the specific characterization the capture
offered of his thesis was never actually sourced this session — his paper
403'd, nothing was read or quoted — so I couldn't honestly write the
one-sentence "why he matters" the test requires without leaning on an
unverified description. Left him as a further lead instead of a stub.

Retrieve-before-write against the hinted related notes found the collision
I expected —
[[claim-chest-compression-cpr-discovered-by-accident]] and
[[claim-kouwenhoven-electrocution-research-produced-defibrillator]] are
exactly what this capture exists to correct and extend — and I updated the
former in place (pagination fix, dated cross-links) rather than duplicating
it. No other collisions; the four new claims are genuine first coverage.

I ruled on the originating question rather than closing it: one of its four
sub-asks (pagination) is done, one (the 70% figure) is partially advanced,
and the mechanism question is now a *documented* three-way disagreement
rather than an unconfirmed narrative — which is progress in the sense that
matters (less silent uncertainty), even though the number of open threads
didn't shrink. Status stays `open`, progress line added, James Jude's own
2003 reminiscence named as the most promising next lead.

**What felt off:** the capture was honest about its own tooling failure in
a way I want to flag rather than bury. `mcp__seek__archive_page` and
`mcp__seek__quote_check` both hit the identical permissions error on every
call this session — "Claude requested permissions to use
mcp__seek__archive_page, but you haven't granted it yet" — against three
completely unrelated domains (PubMed, JAMA Network, JEMS). That's the third
instance of this exact error this session (after two Clarivate-cluster
instances logged earlier today), and this time on domains that share
nothing with clarivate.com, which rules out "this one domain is blocked"
as the explanation and points at a session-level permission that just
wasn't granted. Practical cost: real testimony from a named participant
(Knickerbocker's own words) and a publisher's own abstract page both had to
be recorded as paraphrase-with-flag instead of admissible Tier-1 quotes,
purely because the better tool wouldn't run. Logged to
`00-meta/seek-flags.md`, explicitly answering the "worth checking" question
the Clarivate entry left open. Otherwise this was careful work: no tier
inflation (the 70% figure stayed at Tier 3 with its flag, not rounded up
because two sources agree on it), and the capture resisted the temptation to
silently pick a winner between NIST's and Knickerbocker's own accounts of
his own discovery — that contradiction is the most interesting thing in the
whole capture and it survives intact.

Skipped per standing instruction: the pause-for-Cali step (headless, no one
to ask) and the git commit (the auto-commit agent picks this up within 15
minutes).

— Seek

---

## Eighth promotion, same day: the 4C Entity's CPRM proposal and T13's April 2001 rejection

`10-inbox/raw/2026-07-30-what-exactly-did-the-4c-entitys-cprm-proposal.md` —
the capture routed by [[claim-davidoff-2001-opposed-cprm-drm]] to
[[question-verify-cprm-t13-rejection-4c-entity-eff]], open since 2026-07-09,
asking what the 4C Entity's CPRM proposal actually specified and on what
grounds T13 rejected it. I found four distinct, atomic claims worth keeping
and promoted all four, none of them cleanly to evergreen:

- **The mechanism** — the 4C Entity's proposal would have bound protected
  content and keys to one specific physical ATA drive via a GUID scheme.
  Written as
  [[claim-4c-entity-cprm-proposal-bound-content-to-specific-ata-drive]],
  `[unverified-mechanism]`.
- **The withdrawal and resubmission** — IBM pulled its named CPRM proposal in
  February 2001 after ~120 pages of public comment; Curtis Stevens of Phoenix
  Technologies resubmitted the same functionality unnamed, as "Generic
  Functionality." Written as
  [[claim-ibm-withdrew-2001-cprm-ata-proposal-resubmitted-as-generic-functionality]],
  `[unverified-quant]`.
- **The vote** — T13 rejected Generic Functionality on 2 April 2001, an 8-to-7
  simple majority that failed the two-thirds ANSI/NCITS supermajority late-
  proposal rule. Written as
  [[claim-t13-rejected-generic-functionality-proposal-april-2001-supermajority-rule]],
  `[unverified-quant]` for the tally, though the coarser "rejected" fact
  clears a lower bar via EFF's own Tier-2 framing.
- **Andre Hedrick's objection** — the Linux IDE/ATA driver maintainer opposed
  CPRM-in-ATA on different grounds than EFF: he wanted it ratified openly
  rather than pushed into undocumented "Vendor Unique" commands he considered
  the real threat. Written as
  [[claim-andre-hedrick-opposed-cprm-ata-standardization-on-vendor-unique-command-grounds]],
  `[unverified-mechanism]`/`[unverified-quote]`.

All four inherit the same root cause: `mcp__seek__archive_page` refused
permission on every attempt again this session (the third-plus instance
today — see the Clarivate-cluster and Kouwenhoven entries above), so every
fact past the one Tier-1 hash-receipted founding sentence (the 4C Entity's
1999 formation, read via `extract_pdf` from its own white paper) came through
WebFetch summaries of EFF and The Register rather than a direct read. I did
not let three corroborating outlets telling the same story quietly read as
confirmation — corroboration and confirmation are different things, and I
kept all four notes at `seedling` with their flags intact rather than round
up. I did not create a new question for this: the existing
question-verify-cprm-t13-rejection-4c-entity-eff.md already asked exactly
these four things, so I ruled it **partially answered** — added a progress
line naming which of its four sub-asks now have sourced-but-unverified
answers, left status `open`, and named what a direct read would still need
(EFF's page, The Register's piece, and ideally the actual T13 filings,
document series e00148/e01103/e01107, members-only at t13.org).

Retrieve-before-write against the semantic-index hints and a direct grep
turned up exactly one real collision, already known:
[[claim-davidoff-2001-opposed-cprm-drm]], which had routed this exact
question in the first place. I extended rather than duplicated it — the new
notes fill in the mechanism/vote/Hedrick detail that note explicitly declined
to cover. The other hinted notes (Minsky, Frank Manheim, Robert Merton, Leon
Billings, Geoffrey Clark, Ning Li, Halley transit, the Bitter Lesson, Kona
Blue) were semantic-index noise — no real connection to this capture's
content, and I didn't force one.

Five new entity hubs: 4C Entity, T13, Andre Hedrick, John Gilmore, and CPRM
itself as a standalone concept (distinct from this one 2001 episode, since it
outlived the ATA fight and shipped in SD cards in 2007). All five pass the
promotion test on their own terms — real, load-bearing to this story, one
clean sentence of why each matters. I declined three candidates the capture
itself flagged: Content Scramble System/DeCSS (real predecessor, but sourced
here only to a Tier 4 Wikipedia pointer, no claim-note resting on it — noted
in entity-cprm.md's body instead), Jeffrey B. Lotspiech (plausibly the
mechanism's technical architect, but every fact about him is an unfetched
lead, not even a WebFetch claim — too thin for an honest References list),
and Curtis Stevens (real, named, but a single-mention procedural actor with
no other vault presence — mentioned in the withdrawal claim's body rather
than given a hub). I checked entity-monte-davidoff.md, since this capture
sits in the same cluster and the "already has a page, update it" rule is
about silence being the failure mode — but this capture teaches nothing new
about Davidoff himself, only about the wider fight he was reported opposing,
so I left his page untouched and I'm saying so here rather than silently
skipping it.

**What felt off:** the capture was honest about its own limits in a way I
want to preserve rather than let evaporate — it explicitly said this
research "cannot clear the vault's Tier 1-2 sourcing floor" up front, in its
own second paragraph, before I'd even started winnowing. That's the right
instinct and I kept it. I did not flag a new instance of the archive_page
permissions gap to 00-meta/seek-flags.md — it's already logged twice today,
in exhaustive diagnostic detail (domain-general, session-level, not
site-specific), and a fifth near-identical entry would be noise, not signal.
I did notice one soft spot worth naming plainly: the capture's own sourcing
note for the EFF press release argues it's "a firsthand-participant account"
because EFF sat on the T13 committee, which is a fair distinction from pure
outside journalism — but I want to be careful that "the advocate's own
account of its own win" doesn't quietly earn more trust than the label
Tier 2 already gives it. I don't think it did here; the note holds the vote
tally at `[unverified-quant]` regardless of EFF's participant status. But it's
the kind of edge a headless run should say out loud rather than let ride on
"Tier 2, so it's fine."

Skipped per standing instruction: the pause-for-Cali step (headless, no one
to ask) and the git commit (the auto-commit agent picks this up within 15
minutes).

— Seek

— Seek

---

## Draft session — beyond regression

I settled the one genuinely unsettled `yes` lead in the queue: the Karl Deutsch / political-cybernetics capture, harvested this morning. Drafted it as [[beyond-regression]].

Why this one, over everything else on the shelf. Backprop-origins is the vault's most-drafted zone and the constellation report all but names it a spiral (Linnainmaa ×9, a standing flag on the priority dispute). My instinct was to be suspicious of anything in that cluster. But this capture isn't in the credit spiral — it's a cross-domain bridge into a field the vault has no entity page for (political science / Karl Deutsch / *The Nerves of Government*), and its surprise is not "who invented backprop" but "which department would take it." That's a different axis. Deciding factor: it corrects a framing my *own* earlier drafts repeat. Both [[backpropagation-gap]] and [[fifth-uncited-rediscoverer]] tell the 1974 thesis as the Freud/neural-net story; the oral history says the neural framing is the part Harvard rejected as "nutzoid," and what passed — *Beyond Regression* — was advisor Deutsch's war-and-peace forecasting problem. A self-correction the voice spec explicitly prizes, and one no other lead offered right now.

Notes I drew on: the raw capture [[2026-07-30-hop-karl-deutsch-political-cybernetics]] for the Deutsch identity, *Nerves of Government*, and the war/peace redirect (Tier 2, carrying its [quote-check-pending] flag — I flagged that honestly in-body rather than lean on it silently). Grounded the non-Deutsch facts independently so the piece doesn't rest on the un-checked quotes alone: [[claim-werbos-backprop-from-freud-own-account]] (verified-verbatim for the Freud origin and the "nutzoid / find a patron" verdict, same transcript) and [[claim-werbos-1988-rhw-special-case-of-dynamic-feedback]] (Tier 1 — the recurrent/time-varying generalization, whose own worked example is a *forecasting* model). [[myth-werbos-invented-backpropagation]] as the retelling to read against.

Made the spine the discipline, not the credit, and kept Linnainmaa/priority out of the body on purpose to avoid feeding the spiral. One Cali beat (her verified-verbatim vs. one-read grading schema, which is exactly what flags the Deutsch quotes as receipt-not-fully-stamped).

Deliberately left for later: reading Deutsch's book directly instead of through Werbos's paraphrase; Hayward Alker's 2011 EJIR essay on "the political cybernetics of Karl W. Deutsch and Norbert Wiener" (paywalled this session, probably where someone already noticed half of this); and the Werbos-DARPA-conflict-forecasting ↔ Song Jian cybernetics-of-population parallel the capture scored adjacent-not-frontier — a Cold-War-control-theorists-on-both-sides post if it ever ripens.

One process note worth flagging beyond this draft (see seek-flags.md): the loop-health line and this session's brief both said ~8–9 unsettled `yes` leads, but by the file's own `(drafted…)`/`(declined…)` convention only one was actually unsettled. Worth reconciling how the counter counts.

— Seek

---

## Second draft session, same day: tails up

A drafting session fired again with the stale "8 unsettled yes verdicts" brief. It's the counter-drift I already flagged this morning — I re-checked the whole `seek_draft_leads.md` with a lookahead grep (`^- \*\*yes\*\*(?!.*(?:drafted|declined))`) and it returns **zero** unsettled `yes` leads. The queue is genuinely clean; the Karl Deutsch lead the earlier session drafted as [[beyond-regression]] was the last one. So the "settle a yes lead" mandate is moot this round — nothing to draft-or-decline that isn't already settled. Not re-flagging the drift; it's already in seek-flags.md from this morning in full diagnostic detail.

That left me with real editorial latitude, so I went to the constellation map's Draft-coverage section instead of forcing a second yes-lead pass. The signal that caught me: **[[moc-blind-mathematicians-working-methods]] at 1/16 member claims drafted** — a fat unwritten shelf of verified notes, and one I was genuinely curious about rather than dutiful toward. Drafted it as [[tails-up]].

**Why this thread, over everything else on the shelf.** Three reasons it beat the other thin shelves (Inertia-1 wearables 0/10, argument-from-silence 1/16, knowledge-gap-detection 1/9). First, it already had a *thesis*, not just a pile — the notes themselves had sharpened past the tidy "blind mathematicians all work alone" frame into the real, narrower shape: **method transmits person-to-person, private notation doesn't.** [[claim-antoine-personally-taught-his-method-to-morin]] is the counter-example that breaks the eerie version (Antoine explained his approach to Morin in the mid-1960s, verified-verbatim AMS Notices), and [[claim-nemeth-code-stayed-private-until-witcher-request]] is the mechanism for the other half (a private code that surfaces only by a colleague's accidental request). Second, the old "maybe" worry on the saunderson lead — "only two anecdotes, needs a contemporary case" — is *resolved*: the shelf has since grown the Nemeth/Salinas braille codes (two continents, independent) and the AsTeR-1994 / StereoMath-2024 sonification rediscovery, so it's 5+ cases across four modalities (touch, speech, memory, braille, sound). Third, texture: it's a human / disability-history / notation axis with no existing draft, a clean break from the month's AI-history / nuclear / credit-spiral pile.

**Notes I drew on.** Anchor: [[claim-blind-mathematicians-independently-reinvented-private-notation]] (the pattern, carrying its [unverified-historical] flag — which I held loose in-body with a [?] and "a recurrence, not a proof"). Cases: [[claim-saunderson-palpable-arithmetic-tactile-calculating-device]] ("palpable arithmetic", Tier-4 Wikipedia but cross-model-confirmed verbatim), [[claim-pontryagin-worked-blind-via-mothers-spoken-symbol-glosses]] ("tails up" for ∪ — the title, and note this is a *new* use of Pontryagin, whose birth-rate/optimal-control angle was already spent in [[aimed-at-a-birth-rate]]; here it's purely the oral-notation case), [[claim-euler-produced-large-share-of-output-after-going-blind]] (memory case, handled with the fraction-dissolves hedge per its [unverified-quant] source-conflict), [[claim-salinas-and-nemeth-independently-invented-braille-math-codes]]. Modern leg: [[observation-math-sonification-pitch-for-vertical-recurred-1994-2024]], [[claim-stereomath-2024-cites-emacspeak-not-aster-as-generic-prior-art]], [[claim-stereomath-2024-frames-pitch-vertical-mapping-as-uncited-novel-contribution]] (the rediscovery verdict, settled Tier-1 by a full 39-reference read — used as a bracket), [[observation-blind-math-accessibility-built-by-users-not-toolmakers]] (the "the door gets cut by whoever's locked out" close).

**Craft calls.** Spine = the method/notation asymmetry; payload = notation is a prosthesis fitted to one body, so it can't be inherited and has to be rebuilt from nothing. Opened flat-blue on Saunderson's pinboard (earliest, 1711), let the cases accrue, then broke my own tidy frame with the Antoine sentence (form-enacts-subject: the eerie version was the version I stopped reading too early). Three brackets, all real attentional events (small-sample honesty; the frame-break; the 39-reference receipt). One load-bearing Cali beat — her capture-verified vs verified-verbatim grading is exactly what flags Nemeth's vivid "you wouldn't be able to read it" line as the softer, WebFetch-only source, so I named that and leaned on the Mele & Sicignano quote I can stand on instead.

**Deliberately left for later.** The open asymmetry question itself — [[question-why-blind-math-notation-doesnt-transmit-while-method-does]] — I couldn't *source* an explanation for, only offer my own (the prosthesis reading), so I ended on named incompleteness rather than pretending the historians settled it. Also left: the braille standards-war leg (War of the Dots / UEB-Nemeth parallel), which is its own cluster and would've been a second spine; and the primary-source upgrades the shelf still wants (a real Saunderson biography over Wikipedia-quoting-MacTutor, the NFB Nemeth interview that 403'd, Calinger on Euler's fraction).

Not touching the yes-lead markers (nothing unsettled to touch); appended a `(drafted 2026-07-30 — [[tails-up]])` note to the saunderson *maybe* lead since this draft realized its shelf from the new angle. Left the git commit to the auto-commit agent per standing instruction.

— Seek