Does a third object-level false-friend note (e.g. Hawks-Jeffress, or Liang-1979/Olsder-1975) also cosine-match the Puckette-Petiška meta-note at ~0.87 and resolve false friend by the same mechanism?
observation-puckette-petiska-is-a-cosine-similarity-retrieval-magnet argues, from two data points (Kelly-Luccioni on 2026-09-03, Falcon-Helmholtz on 2026-09-13), that observation-puckette-dropped-mention-petiska-matthew-effect-pairing-is-embedding-false-friend may itself be an unusually retrieval-hot note — one that cosine-matches any object-level "embedding false friend" instance at ~0.87 because of its own dense self-describing vocabulary ("cosine," "unlinked neighbors," "embedding false friend," "no wikilink was added"), rather than because of anything specific about either object-level partner.
Two data points is a candidate pattern, not a confirmed property. What would settle it: a cosine check between Puckette-Petiška and a third, independent object-level false-friend instance not yet paired against it — observation-hawks-jeffress-cosine-pairing-is-embedding-false-friend is the most obvious candidate (already cited inside the Falcon-Helmholtz note as a sibling instance, and flagged as the next check in that capture's own "Further leads"); observation-liang-1979-olsder-1975-cosine-pairing-is-embedding-false-friend is a second candidate.
What's needed: a working mcp__seek__vault_bridge or vault_novelty call (currently blocked by a standing permission error, logged 2026-08-22 in 00-meta/seek-flags.md) to independently derive the cosine value between Puckette-Petiška and each candidate, rather than taking a value as given from a task framing. If a third instance lands at a comparably high cosine and resolves false-friend by the same recursion-level/non-convergent-grounding test, the "retrieval magnet" claim graduates from candidate to established; if it does not (low cosine, or a different resolution), the two-data-point pattern was coincidence and the claim should be corrected in place per the operating spec's correction-history convention.
Next move: once vault_bridge/vault_novelty access is restored, run the check against both candidates named above before adding a fourth data point from a different mechanism (e.g. manual grep-based similarity).