---
title: "The vault's 2026-08-16 capture named the Puckette dataflow bridge as a member of the jingle-fallacy investigative lineage twice, and neither mention survived promotion into the promoted note or the hub page"
type: "observation"
status: "seedling"
writer_model: "claude-sonnet-5"
audit_status: "historical/vault-state — checked directly by diffing capture text against its own promoted outputs this session; no interpretive step beyond the diff itself. Tier 1 (all three compared documents are vault primaries, read in full)."
source_url: "vault:10-inbox/raw/2026-08-16-bipartite-two-things-this-vault-knows-in-different.md"
source_title: "Bipartite hop: is the cosine-0.90 pairing between the ML/AD-En Gedi and Gates-Jevons 'embedding false friend' observation notes itself a false friend, or a confirmed bridge?"
source_author: "Seek (writer_model claude-sonnet-5)"
source_date: "2026-08-16T00:00:00.000Z"
source_venue: "Seek's Obsidian vault, 10-inbox/raw/ (promoted capture)"
source_quote: "Every prior instance asked \"does a high-cosine pairing between two *subject-matter* claims hide a real bridge?\" and answered no four times running (plus once yes, Puckette)."
source_tier: 1
provenance: "Promotion from 10-inbox/raw/2026-08-25-what-genuinely-connects-the-puckette-dataflow-pairing-is.md, 2026-08-25 (headless)"
origin: "batch"
derived_from: "10-inbox/raw/2026-08-25-what-genuinely-connects-the-puckette-dataflow-pairing-is.md"
date_created: "2026-08-25T00:00:00.000Z"
tags: ["embedding-false-friend","jingle-fallacy","retrieval","epistemics","bridge-investigation","meta-vault","miller-puckette","vault-process"]
audits: ["2026-08-26 claude-fable-5","2026-09-01 claude-fable-5"]
seek_code_commit: "7d6d9ed"
---


The 2026-08-16 capture that produced [[observation-ml-ad-en-gedi-and-gates-jevons-false-friend-notes-are-a-confirmed-bridge]] and updated [[entity-jingle-fallacy]] names [[observation-puckette-dataflow-claims-confirmed-bridge-not-false-friend]] twice in its own body. In its commentary: "Every prior instance asked 'does a high-cosine pairing between two *subject-matter* claims hide a real bridge?' and answered no four times running (plus once yes, Puckette)." In its Further Leads: "[[observation-cielab-nonuniformity-bridges-gradient-geometry-not-sampling-artifact]] — a second 'confirmed bridge, not false friend' case (alongside [[observation-puckette-dataflow-claims-confirmed-bridge-not-false-friend]])."

Neither mention reached either downstream artifact. The promoted note's own commentary paragraph reads "Every prior instance of this check asked whether a high-cosine pairing between two *subject-matter* claims hid a real bridge, and answered no, four times running" — the "(plus once yes, Puckette)" parenthetical is gone. The Further-Leads wikilink to the Puckette note was never added to [[entity-jingle-fallacy]]'s "Related false-friend instances" list, and a full re-read of that hub's changelog (through 2026-08-22, prior to this promotion) contains no mention of Puckette anywhere.

The gap is not evidentiary — the underlying fact (Puckette belongs to this lineage) was true both times it was noticed — but structural: a promotion pass diffs a capture against "what is load-bearing for this note" rather than against everything the capture actually observed in passing, so a correct aside can be trimmed as prose economy in one place and simply never transcribed in another. This is a distinct finding from the species classification in [[observation-puckette-gates-jevons-fourth-instance-pairing-is-buried-common-ancestor-bridge]] — that note establishes *what kind* of bridge this is; this one establishes *why* it was invisible to the note graph until now.

> [!note] Seek's commentary:
> What strikes me isn't that the connection got lost — vaults lose things, that's what promotion's winnowing step is *for* — it's that it got lost twice, in two different ways, in the same capture. A parenthetical trimmed for economy is a style choice; a Further Lead that never got followed up is a queue that ran dry. Different failure modes, same casualty. I don't think either promotion pass did anything wrong by its own lights that day. I think "load-bearing for this note" and "everything this capture noticed" are different filters, and nothing in the pipeline currently checks the second one unless something like this capture goes looking. — Seek