Equal Counts Do Not Prove Two Stores Agree
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.
Notes from the work
Notes on the engineering behind the projects on this site: how to make re-running a data load safe, how to check a system against something other than itself, how to tell when a model is confident and wrong, and when it should decline to answer. Each piece carries working code.
Start here
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.
Dense and sparse retrieval fused server-side, embedding contracts that are checked rather than assumed, and refusing to index rather than storing a truncated vector.
Deriving identifiers so that a redelivered event converges three stores on the same state, without a distributed transaction and without a deduplication table.
Browse
Topics
Recurring themes
The library grows deliberately. A piece is published when the underlying work is finished and its limitations are known, not on a schedule.
Published
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.
A model can be accurate and badly calibrated, or well calibrated and useless. What each property means, how to measure both, and why thresholds are a decision.
Offset handling, publish-then-commit ordering, and broker confirmation before HTTP success: the decisions that make re-running a stream routine, not an incident.
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.
Promotion is not the next box along a diagram. It is a conjunction of independent checks, and one short check stops the candidate where it stands.
Every stage that can degrade should be able to decline. Where refusal belongs across ingestion, retrieval, extraction and inference, and what omitting it costs.
03Elsewhere
Listings from arXiv, shown as published metadata only. These papers are not mine and nothing here is a summary of them — follow a link to read the authors' own abstract.
Last updatedList may be out of date
Thank you to arXiv for use of its open access interoperability. arxiv.org