The Epistemic Resonance Protocol is a Holochain app for epistemic discourse, where people set out claims, critiques and evidence as linked graphs. On 19 October 2026, @StateofIntent merged a change that lets a client ask, for each piece of evidence a claim cites, whether it has arrived yet.
For a builder, this means a composer holding 4 evidence hashes can show "3 of 4 have arrived" while the author is still typing. ValiChord, a project for independent verification where blind validators record results as tamper-evident Harmony Records, also published v0.6.6 on 18 October 2026. That release makes every node check credentials, evidence and tiers, and it requires a fresh install.
Epistemic Resonance Protocol reports which cited evidence has arrived, hash by hash
The pull request, titled "Closure, and the row's own blocker was the thing that was wrong", found that a stalled write reports one hash, because the protocol's check stops at the first unresolved dependency. A client that subtracted that hash from its citations would report "3 of 4 resolve" for a claim where none of the other 3 do. The new call answers for each hash, in order, and treats every entry type alike, so a cited Mew or Constitution is not reported as missing.
The call reads local databases only and makes no network call, whatever it is passed. If an SDK is newer than the app it talks to, the call returns null, and the client keeps writing and shows the count as unknown, never as "0 of 0". The stall message also stopped misreporting: it had said "cites 1 entry" for every stall.
ValiChord v0.6.6 moves to Holochain 0.7.1 and requires a fresh install
The release, titled "v0.6.6 — Holochain 0.7.1, and every node now checks credentials, evidence and tiers", is breaking. Nodes on 0.7.1 cannot read capability grants written by 0.7.0, so an upgrade in place would leave a cell without its public-read grant. Operators must clear conductor state and install fresh.
Records published on the 0.7.0 network will not resolve on the new one. The release also closes 3 protocol gaps where a safety property depended on the honest software path rather than on what every node checks.
ValiChord nodes now check joining credentials, signed records and validator tiers
Pull request 47, titled "Peer-enforced signatures and tiers", was merged by @topeuph-ai and changes what every node enforces. Before it, a joining credential's signature was checked only in the joining agent's own init, so modified software could skip it. A HarmonyRecord also passed validation as long as its author listed themselves, so one agent could list 6 real but unrelated keys and publish a result that qualified for Gold.
Now every peer checks the joining signature, and each record carries its validators' own signed attestations. Every node checks a profile's tier against the joining certificate that grants it, on edits as well as on new profiles. Validator clients, including AI validators, keep hashing exactly as before.
The agent SDK gives builders a per-hash arrival call before a write
Call closureOf(hashes) before a write, and closure on onPendingDependency while a write is stalled. Underneath,
which_entries_resolve_locally takes the hashes and returns a Vec<bool>, using GetOptions::local(). The agent SDK moves to 0.1.5 in the pull request, and its publish still needs npm login. ValiChord builders need hdk 0.7.1 and hdi 0.8.1 and must clear conductor state before a fresh install.