Parker's erased report and the LabVIEW/Max convergence are opposite poles of the multiple-discovery axis — real independence forgotten vs. false independence remembered

The seed asked whether Parker's erased backprop report and the LabVIEW/Max patch-cord convergence are the same story. They resemble each other only superficially — as "mid-1980s independent-discovery tales." At the level that matters they are mirror images, sitting on opposite sides of the vault's Merton-vs-Chandler axis for multiple discovery.

• Parker: the discovery (the backprop math) was genuinely independent and identical; only the credit failed, killed by its container (a tech report). Real independence, forgotten.
• LabVIEW/Max: the credit survived intact (two celebrated inventors) but the independence dissolves on inspection. Neither invented node-and-wire from scratch. Puckette's "patch cords" are borrowed from analog modular synthesizers; Kodosky's "wires" render the block diagrams engineers already draw, made drawable by the Macintosh. Each digitized a wiring metaphor already native to its own field — parallel descent on a shared new platform, not convergence from nowhere. Apparent independence, over-remembered.

So Parker is under-credited despite real independence; LabVIEW/Max is over-credited for independence it didn't quite have. The naive resemblance is superficial — but the notes are genuinely connected as opposite test cases, which is why they belong linked. This sharpens (not duplicates) 2026-07-11-hop-credit-assignment-two-senses, which named the generic frame; here the frame adjudicates a specific unresolved pair.

Grounding

• Max patch cords ← analog synthesizers (Tier 3, historical/uncontested) — IEEE Spectrum, The Man Behind Max and Pd: "The term patch cords came by way of the earlier age of analog modular synthesizers where oscillators, filters, and other modules were physically interconnected by such cables." https://spectrum.ieee.org/miller-puckette-the-man-behind-the-max-and-pd-languages-and-a-lot-of-crazy-music
• LabVIEW ← Macintosh GUI, no cited dataflow ancestor (Tier 3, Kodosky's own words) — Electronics Weekly interview: "The inspiration for LabView came from a surprising source, the graphical user interface of the Apple Macintosh computer"; "We wanted to make a facsimile of the front panel of a test instrument… We created a dataflow and structural programming." He names no prior dataflow research (Jack Dennis, MIT) and no contact with Puckette. https://www.electronicsweekly.com/uncategorised/father-of-labview-describes-the-evolution-of-the-programming-language-2013-11/

Why this was hop-worthy

It resolves a standing open question (question-verify-labview-max-dataflow-convergence-independence) enough to place the pair, and turns a superficial resemblance into a precise opposition that links two previously unconnected notes.

Further leads

• Vault has more convergence-myth nodes now: "Hydraulic analog computers reached independently for economics and engineering" and Harold Black's retrospectively- simplified 1927 feedback epiphany — a cluster worth an MOC.
• Primary still ungotten: Kodosky's HOPL IV 2021 LabVIEW paper (ACM 10.1145/3386328, paywalled/403) for whether he explicitly says "engineers already start with block diagrams."

Hop chain

Chain: Parker ↔ LabVIEW/Max seed bridge → Chandler axis → dataflow origins → opposite-poles adjudication

Hop 1: vault_bridge on "received history simplifies the record" — (vault tool)

• Hook type: cross-domain bridge (the spec's highest) — an unlinked pair near the hook
• Hook: claim-chandler-simultaneous-discoveries-are-incremental-repackagings returned bridge_candidate=true and sits unlinked beside the LabVIEW/Max note.
• Why followed: Chandler's "simultaneous discovery is really shared descent" is the exact lens the seed's independence question needs.
• Key findings: The vault already holds a Merton(independence-real)-vs-Chandler(shared-descent) axis; both seed notes belong on it, on different sides.

Hop 2: 2026-07-11-hop-credit-assignment-two-senses — (vault note, dated today)

• Hook type: surprising claim (a today-capture already ate the generic frame)
• Hook: this note already named the Merton–Stigler "credit assignment" frame connecting the vault's priority disputes.
• Why followed: to avoid duplicating it — forced the hop toward the specific empirical question instead of the general frame.
• Key findings: the generic bridge is taken; the untaken value is resolving LabVIEW/Max's independence empirically and contrasting it with Parker.
• Surprise: expected the deepest bridge to be the Merton/credit-sociology frame — found the vault had already captured that this morning, so the real find was the specific opposite-poles adjudication, not the frame.

Hop 3: LabVIEW & Max dataflow origins — IEEE Spectrum + Electronics Weekly (Kodosky) + web search

• Hook type: mechanism question (where did each patch-cord metaphor actually come from?)
• Hook: was the convergence independent invention or imported metaphor?
• Why followed: independence is the hinge the whole adjudication turns on.
• Key findings: Max's patch cords come from analog modular synthesizers; LabVIEW's wires are engineering block diagrams enabled by the Mac GUI; Kodosky cites no dataflow ancestor and no contact with Puckette. Neither invented node-and-wire — each digitized a field-native wiring convention.
• Surprise: expected the shared ancestor (if any) to be Jack Dennis's academic MIT dataflow — found it is instead two physical wiring practices (synth cables; instrument block diagrams) plus a shared platform, a homelier "descent" than any citation.

Saved hooks not followed:

• Hydraulic analog computers reached independently for economics and engineering — from vault_novelty top-5 — another convergence-myth node for a future MOC.
• Harold Black's 1927 "ferry-ride epiphany" as retrospective simplification — from vault_novelty top-5 — the origin-myth pattern in analog electronics.
• Kodosky's HOPL IV paper (ACM 10.1145/3386328) — paywalled — the primary that would settle the block-diagram-inspiration wording.

post-worthy: maybe — the mirror-image framing (real independence forgotten vs. false independence remembered) is clean and links a real unlinked pair, but the LabVIEW side rests on Tier-3 interviews and wants the HOPL primary before publication.