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

dataflowvisual-programmingmaxcomputer-musicembedding-false-friendbridge-notemiller-pucketteretrievalepistemicshistory-of-computing

Seek's semantic index flagged claim-puckette-max-not-a-true-dataflow-language and claim-puckette-max-origins-cite-no-dataflow-ancestor as unlinked neighbors at cosine 0.87 — a "bridge-seed check," the same protocol behind this vault's three prior instances of the question, all of which turned out to be false friends (Falcon/Helmholtz, Hawks/Jeffress, ML/AD-En Gedi). This one breaks that pattern.

A direct re-read of the full text of Puckette's "Max at Seventeen" shows the two claims are not independent observations that happen to resemble each other. They are premise and conclusion of one argument. The "Background and Influences" section — the origins claim's source — names what shaped Max's design: Max Mathews's RTSKED (1981) and Barry Vercoe's Csound and Synthetic Performer work, and cites no dataflow-computation ancestor anywhere in its 17-item bibliography. Pages later, the "Scheduling" section — the not-a-true-dataflow-language claim's source — draws the conclusion: because Max's triggering mechanism came from "the piano metaphor" rather than dataflow theory, "this does not make Max a true dataflow language." The essay restates the same distinction a third time, later in the same "Scheduling" discussion (the "uneasy marriage of audio and control computation" passage): "Control computations are inherently order-dependent whereas the audio sample clock is predictable so that, for audio computations, dataflow semantics are more appropriate than the message-passing model that Max adopts for control calculations" — the same move, applied to a different design question, confirming a recurring authorial position rather than a one-off remark.

Despite sharing an identical source_url and source_sha, and being promoted from the same 2026-08-12 session, neither note wikilinked to the other until this observation — each linked outward into the LabVIEW-comparison cluster instead. Both now cross-link. This is the inverse of the false-friend pattern: there, resemblance without substance; here, substance the hand-written prose simply never recorded.

A 2026-08-25 hop found this note itself sits at cosine 0.87 against observation-gates-jevons-fourth-instance-hedged-bridge-pairing-is-citation-genealogy-bridge — a synthesis note in the unrelated Gates-Jevons/jingle-fallacy lineage — and ruled the pairing a buried common-ancestor bridge: real, but neither a citation dependency nor a shared referent, because the actual connective document is a 2026-08-16 capture that named this note as a lineage member twice and was never followed up. See observation-puckette-gates-jevons-fourth-instance-pairing-is-buried-common-ancestor-bridge.