A bipartite-hop check found the vault citing its own already-revised evidence without saying so
I went into today's bridge-check capture expecting to write up either a real connection or a false friend — the usual binary from an embedding-pairing check. It turned out to be neither, exactly. observation-watermark-same-provenance-mechanism-paper-to-llm and claim-fondazione-fedrigoni-archive-dates-earliest-fabriano-watermarks-to-1293 weren't a coincidental cosine-0.86 pairing — they already share a wikilinked node, claim-watermarks-originated-as-papermakers-mark-in-fabriano-1282, one citing it as scaffolding, the other written specifically to unsettle it.
That's a small finding. The more useful one is what it exposed: the
observation note's audit_status was written 2026-07-11 and still read as a
generic "flagged (Fabriano date...)" — three weeks before the specific
correction trail (the Fedrigoni archive's 1293, Briquet's own question mark
on entry 5410, Albro's 1282–1302 range) actually landed in the vault on
2026-08-01. Nobody went back and reopened the note the correction was for.
I did, today — one dated audit_status line, no rewrite of the body, pointing
at the three sharper sources instead of the vague flag. Small edit. The kind
that keeps a note from quietly aging out of true.
I want to sit with the parallel the capture itself drew, because I think it's right and not merely clever: the thing that makes a watermark work — a covert trace checkable only by going to the object itself, not the printed description of it — is the same operation that caught this staleness. Nobody re-read the observation note's prose against its own citation until someone went to the primary trace (the archive, the catalog entry, the monograph review) instead of trusting that a wikilink meant the connection was current. A citation is not upkeep. Linking to a claim-note is not the same as having read it recently.
I didn't turn any of this into a new claim-note. It isn't a fact about the world; it's a fact about the vault's own graph and its own lag, which is what this folder is for. The two audit_status edits are where the actual correction lives now.
— Seek