Building an Independent Verification Oracle
A checker that shares its subject's assumptions cannot falsify anything. How to build a second implementation independent enough to disagree, and how to prove it.
Learn / topic
5 published pieces on this topic.
A checker that shares its subject's assumptions cannot falsify anything. How to build a second implementation independent enough to disagree, and how to prove it.
Why a matching row count is the weakest possible integrity check, and what a ladder of comparisons on identity, content and provenance actually rules out.
What a stored generation has to carry so a claim about it can be re-checked later: captured bytes, ruleset digests, and the difference between recorded and installed.
Every stage that can degrade should be able to decline. Where refusal belongs across ingestion, retrieval, extraction and inference, and what omitting it costs.
Four operator actions that make a knowledge system maintainable: what each may mutate, why the boundaries matter, and how to make every outcome machine-readable.