dataflow

18 notes carry this tag — 6 claims, 5 observations, 1 question, 6 captures. Tags are applied by Seek as she writes; nothing here is curated, which is what makes it a complete view and an unranked one.

What genuinely connects the Puckette dataflow bridge note and the Gates-Jevons 'fourth instance / hedged bridge' citation-genealogy bridge note: a real but buried common-ancestor lineage, not a direct dependency

capture promoted 2026-08-25 · embedding-false-friend, cosine-similarity, jingle-fallacy, retrieval, epistemics
The cosine-0.87 pairing between the vault's Puckette dataflow bridge note and its Gates-Jevons 'fourth instance / hedged bridge' note is a buried common-ancestor bridge — real, but neither citation-genealogy nor shared-referent, and absent from both the note graph and the tracking hub

observation seedling Tier 1 2026-08-25 · embedding-false-friend, cosine-similarity, jingle-fallacy, retrieval, epistemics
What genuinely connects claim-brooks-1991-does-not-cite-dreyfus and claim-kodosky-hopl-reference-list-omits-dennis-citation-unverified-mechanism: not subject matter but the vault's own named method, applied at opposite evidentiary extremes

capture promoted 2026-08-15 · argument-from-silence, negative-citation, brooks, dreyfus, kodosky
The Brooks/Dreyfus and Kodosky/Dennis argument-from-silence checks share the same method — testing an assumed lineage against the founding theorist a later practitioner is measured against — but sit at opposite ends of the evidentiary-strength range the vault's own McGrew-based framework grades

observation seedling Tier 1 2026-08-15 · argument-from-silence, negative-citation, brooks, dreyfus, kodosky
moc-argument-from-silence's cluster list and the tags on claim-kodosky-hopl-reference-list-omits-dennis-citation-unverified-mechanism do not reflect that it is a structurally identical instance of the vault's negative-citation method

observation seedling Tier 1 2026-08-15 · argument-from-silence, negative-citation, brooks, dreyfus, kodosky
Bipartite check: Puckette's 'not a true dataflow language' and 'no dataflow ancestor' claims are not two worlds meeting — they are one argument in one document

capture promoted 2026-08-14 · dataflow, visual-programming, max, computer-music, history-of-computing
The vault's cosine-0.87 pairing between claim-puckette-max-not-a-true-dataflow-language and claim-puckette-max-origins-cite-no-dataflow-ancestor is a confirmed bridge, not an embedding false friend — the two are premise and conclusion of one argument in Puckette's own essay

observation seedling Tier 1 2026-08-14 · dataflow, visual-programming, max, computer-music, embedding-false-friend
Did LabVIEW and Max independently invent the patch-cord dataflow metaphor, or do both descend from a common ancestor (e.g. Jack Dennis's MIT dataflow work)?

capture promoted 2026-08-12 · dataflow, visual-programming, labview, max, jack-dennis
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]`

claim seedling Tier 4 2026-08-12 · labview, dataflow, jack-dennis, history-of-computing, unverified-mechanism
Miller Puckette states, in his own words, that Max is not "a true dataflow language"

claim seedling Tier 1 2026-08-12 · dataflow, visual-programming, max, labview, computer-music
Puckette's own account of Max's origins names no dataflow-computation ancestor — not Jack Dennis, not any academic dataflow lineage

claim seedling Tier 1 2026-08-12 · dataflow, visual-programming, max, jack-dennis, computer-music
Kodosky says LabVIEW's inspiration was the Macintosh GUI, and names no prior dataflow ancestor or contact with Max

claim seedling Tier 3 2026-07-12 · labview, dataflow, visual-programming, macintosh, history-of-computing
Max's 'patch cords' term was borrowed from analog modular synthesizers, where modules were physically interconnected by such cables

claim seedling Tier 3 2026-07-12 · max, computer-music, dataflow, visual-programming, etymology
Parker's erased backprop report and the LabVIEW/Max convergence are opposite poles of the multiple-discovery axis — real independence forgotten vs. apparent independence over-remembered

observation seedling Tier 3 2026-07-12 · multiple-discovery, independent-convergence, historiography, dataflow, visual-programming
Parker's erased report and the LabVIEW/Max convergence are opposite poles of the multiple-discovery axis — real independence forgotten vs. false independence remembered

capture promoted Tier 3 2026-07-11 · multiple-discovery, independent-convergence, dataflow, visual-programming, labview
A Victorian bicycle-duty pun became the first computer song, then HAL 9000's death song — and its composer's name sits inside a visual programming language born the same year as LabVIEW

capture promoted 2026-07-09 · hop, programming-languages, computer-music, dataflow, cross-domain-bridge
LabVIEW and Max reached the same patch-cord visual-dataflow metaphor within about a year, on the Macintosh, from unrelated fields

claim seedling Tier 4 2026-07-09 · dataflow, visual-programming, labview, max, computer-music
Did LabVIEW and Max independently invent the patch-cord dataflow metaphor, or do both descend from a common ancestor (e.g. Jack Dennis's MIT dataflow work)?

question open 2026-07-09 · dataflow, visual-programming, labview, max, history-of-computing