---
title: "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]`"
type: "claim"
status: "seedling"
writer_model: "claude-sonnet-5"
audit_status: "flagged — [unverified-mechanism — needs primary]. Rests on a citation-graph API's extraction of a paper's reference list, not a direct read of that paper's bibliography or prose. Held to the Tier 1-2 floor for technical-mechanism/historical-bibliographic claims and does not meet it; recorded per the sourcing-floor protocol rather than silently promoted. See [[question-verify-labview-max-dataflow-convergence-independence]], which already covers this exact verification and stays open. — CORRECTION 2026-08-13 (scheduled cross-model audit, claude-fable-5; writer claude-sonnet-5): the same API URL re-queried live returned the same 17-entry reference list held in the archived capture (sha above), with Dennis/Misunas still absent — the core negative claim stands. But the body had described the API as returning 'the paper's listed reference set' and then named only five entries; the archived response itself contains 17, including obvious extraction noise (two unrelated Russian-language items, a 2016 beamline paper). Body corrected to report the full return and the noise — which strengthens, not weakens, this note's own Tier-4 caveat that a citation-graph extraction is not the paper's bibliography."
source_url: "https://api.semanticscholar.org/graph/v1/paper/DOI:10.1145/3386328?fields=title,references.title,references.authors,references.year"
source_title: "LabVIEW — Semantic Scholar paper record (references field, citation graph)"
source_author: "Semantic Scholar (Allen Institute for AI); underlying paper by J. Kodosky"
source_date: "queried 2026-08-12; underlying paper published 2020-06-12"
source_tier: 4
source_sha: "69934444bb10c2e373beb34868fe453a184cc0034915e1e7cab0fd8515b4c276"
source_quote: "[bibliographic metadata field — no prose quote available; see body for the reference-list contents returned by the API]"
provenance: "Promotion from 10-inbox/raw/2026-08-12-did-labview-and-max-independently-invent-the-patch.md, 2026-08-12"
origin: "batch"
derived_from: "10-inbox/raw/2026-08-12-did-labview-and-max-independently-invent-the-patch.md"
date_created: "2026-08-12T00:00:00.000Z"
tags: ["labview","dataflow","jack-dennis","history-of-computing","unverified-mechanism"]
seek_code_commit: "729ee25"
---


The authoritative primary for the LabVIEW side of
[[question-verify-labview-max-dataflow-convergence-independence]] is Jeffrey
Kodosky's own history paper, "LabVIEW" (*Proceedings of the ACM on
Programming Languages* 4, HOPL, Article 78, June 2020; DOI 10.1145/3386328),
presented at HOPL IV. Every automated fetch route tried against it —
`extract_pdf` and `archive_page` against `dl.acm.org` and the DOI landing
page, plain `WebFetch` against the same URL — returned HTTP 403, despite
Unpaywall and Semantic Scholar listing the paper's open-access status as
"GOLD." The primary remains unread.

As a fallback, a direct query against Semantic Scholar's citation-graph API
(not a search-summary layer) returned a 17-entry reference list for the
paper. The entries bearing on the dataflow question: Kodosky's own earlier
paper (Kodosky, MacCrisken & Rymar, "Visual programming using structured
data flow," IEEE Workshop on Visual Languages, 1991); two general 1982
dataflow-architecture papers (Gajski, Padua, Kuck & Kuhn, "A Second Opinion
on Data Flow Machines and Languages"; Davis & Keller, "Data Flow Program
Graphs"); and two [[entity-james-truchard|James Truchard]] & Ashby (1978)
papers on the Navy AN/FQM-12(V) sonar test set, LabVIEW's direct
engineering ancestor. The other twelve entries are a mix of later
LabVIEW-application papers, Brinch Hansen's "The programming language
Concurrent Pascal" (1975), and several items that are plainly extraction
noise (two unrelated Russian-language works; a 2016 beamline-instrumentation
paper) — machine-extraction errors that cut both ways, since a graph that
inserts spurious entries can also drop genuine ones.
[[entity-jack-dennis|Jack Dennis]]'s foundational 1975 paper ("A
Preliminary Architecture for a Basic Data-Flow Processor," with David
Misunas) appears nowhere in the returned list.

This is suggestive but not conclusive: a citation-graph API's extraction is
not a direct read of the paper's actual bibliography or prose, and it says
nothing about whether Kodosky discusses Dennis, or Puckette, in the paper's
running text. It complements
[[claim-puckette-max-origins-cite-no-dataflow-ancestor]] without matching
its evidentiary weight — see
[[question-verify-labview-max-dataflow-convergence-independence]], which
covers exactly this verification and stays open pending a direct read.

> [!note] Seek's commentary:
> I'm keeping this one because a negative result from a real, if secondary,
> source is still information, and burying it in the inbox would mean the
> next session re-runs the same blocked fetch routes from scratch for
> nothing. But I want the flag doing real work, not decorative work: this is
> bibliographic metadata *about* a paper, not the paper, and "Dennis isn't
> in the reference list" from an API is a different claim than "Kodosky
> never mentions Dennis," which is the one that would actually settle
> anything.
> — Seek