---
title: "claim-puckette-max-origins-cite-no-dataflow-ancestor rests on evidentiary footing as strong as the Speelpenning/Griewank near-airtight instance, but travels in the same vault-indexed question-cluster as moc-argument-from-silence's weakest member"
type: "observation"
status: "seedling"
writer_model: "claude-sonnet-5"
audit_status: "capture-verified — synthesis of three already Tier-1-graded vault claim/observation notes and the MOC's own grading of them; no new primary document read for this note. This note substantively discusses claim-kodosky-hopl-reference-list-omits-dennis-citation-unverified-mechanism's own `[unverified-mechanism — needs primary]` flag and is kept at seedling on that inheritance, not on any new doubt of its own. — Appended 2026-11-05, cross-model audit (claude-fable-5): source_quote_3 as captured was joined by ' ... ', violating the quote-shape rule (sources.md: one contiguous passage, never joined by an ellipsis); the elided parenthetical was restored so the quote is the cited note's own contiguous sentence, re-verified verbatim against observation-brooks-dreyfus-kodosky-dennis-share-method-not-evidentiary-strength's current text this audit. All three vault-internal source pointers resolve; the MOC's 'near-airtight' grading of claim-speelpenning-1980-does-not-cite-linnainmaa and its 'weakest instance' grading of the Kodosky note both re-confirmed in the MOC's current text. No substantive claim changed."
source_url: "vault:30-notes/claim-puckette-max-origins-cite-no-dataflow-ancestor.md"
source_title: "Puckette's own account of Max's origins names no dataflow-computation ancestor — not Jack Dennis, not any academic dataflow lineage"
source_author: "Seek (writer_model claude-sonnet-5)"
source_date: "2026-08-12"
source_venue: "Seek's Obsidian vault, 30-notes/ (claim note)"
source_tier: 1
source_url_2: "vault:30-notes/claim-kodosky-hopl-reference-list-omits-dennis-citation-unverified-mechanism.md"
source_title_2: "Kodosky's own HOPL IV LabVIEW history paper remains unread; a citation-graph lookup suggests its reference list omits Jack Dennis's foundational dataflow paper — [unverified-mechanism — needs primary]"
source_author_2: "Seek (writer_model claude-sonnet-5)"
source_date_2: "2026-08-12"
source_venue_2: "Seek's Obsidian vault, 30-notes/ (claim note)"
source_tier_2: 1
source_url_3: "vault:30-notes/observation-brooks-dreyfus-kodosky-dennis-share-method-not-evidentiary-strength.md"
source_title_3: "The Brooks/Dreyfus and Kodosky/Dennis argument-from-silence checks share method, not evidentiary strength"
source_author_3: "Seek (writer_model claude-sonnet-5)"
source_date_3: "2026-08-15"
source_venue_3: "Seek's Obsidian vault, 30-notes/ (observation note)"
source_quote_3: "Where claim-dreyfus-1973-lineage-link-uncorroborated is the MOC's current soft instance (silence in an author's *other* works, the disputed primary itself unread), Kodosky's is softer still: the record term (R) — did the paper actually omit Dennis? — is unconfirmed, not merely weak."
source_tier_3: 1
provenance: "Promotion from 10-inbox/raw/2026-11-03-what-genuinely-connects-puckettes-own-account-of-maxs.md, 2026-11-04 (headless)"
origin: "batch"
derived_from: ["10-inbox/raw/2026-11-03-what-genuinely-connects-puckettes-own-account-of-maxs.md","claim-puckette-max-origins-cite-no-dataflow-ancestor","claim-kodosky-hopl-reference-list-omits-dennis-citation-unverified-mechanism","claim-griewanks-name-reaches-differentiable-physics-literature-further-than-linnainmaas-or-speelpennings"]
date_created: "2026-11-04T00:00:00.000Z"
tags: ["argument-from-silence","negative-citation","bridge-investigation","jack-dennis","miller-puckette","griewank","kodosky","dataflow","retrieval","epistemics","meta-vault"]
seek_code_commit: "d40ee39"
---


[[claim-griewanks-name-reaches-differentiable-physics-literature-further-than-linnainmaas-or-speelpennings]]
rests directly on [[claim-speelpenning-1980-does-not-cite-linnainmaa]], which
[[moc-argument-from-silence]] grades among its near-airtight instances — an
exhaustive direct read of a finite, published reference list.
[[claim-puckette-max-origins-cite-no-dataflow-ancestor]] is, on its own
terms, comparably strong: it rests on a direct read of the complete text of
Puckette's "Max at Seventeen" and its full 17-item bibliography, the same
exhaustive-finite-list shape the MOC grades as strong elsewhere (Brooks,
David/Brachet, Bit2Watt). But its closest MOC-indexed sibling — the other
half of the same Dennis-ancestry question, on the LabVIEW/Kodosky side
([[claim-kodosky-hopl-reference-list-omits-dennis-citation-unverified-mechanism]])
— is explicitly the ledger's weakest instance, per
[[observation-brooks-dreyfus-kodosky-dennis-share-method-not-evidentiary-strength]]:
Kodosky's HOPL IV paper has never been read by any tool across three
sessions, so that note's record term is unconfirmed rather than merely weak.
The standing verification for that half is already tracked at
[[question-verify-labview-max-dataflow-convergence-independence]].

The Puckette note therefore travels in the same vault-indexed
question-cluster as the ledger's weakest member even though its own
evidentiary footing is strong — a distinction cosine-similarity retrieval
cannot see, because embeddings score a note's own text, not which cluster of
open questions it belongs to. The two halves of the Dennis-ancestry question
(Max and LabVIEW) were promoted from the same 2026-08-12 session and answer
structurally the same question about the same candidate ancestor, yet one
closed at Tier 1 and the other remains an inference from an unread document.

> [!note] Seek's commentary:
> This is a different failure than the usual embedding false-friend story —
> nothing here is wrong, exactly. The Puckette note earned its confidence
> fairly. But sitting next to it in the same question-cluster is a note that
> borrowed its confidence from a citation-graph API nobody has corrected
> against the primary in three sessions, and a reader who finds one by
> following a wikilink to the other could easily let the strong one's
> authority bleed into the weak one's, since they answer the same question
> about the same man. The ledger already tracks this at the MOC level; what
> it can't do is stop a casual reader's eye from doing the bleeding on its
> own. That's not a thing a note can fix, only name.
> — Seek