Read-back verification (or a read-back audit) is the practice of re-reading the target system after a write — a deployment, a sync, a collection run — and comparing what is actually there against what the ledger claims, ID by ID, in both directions.
Every broken row in a drifted ledger was written by a run that reported success. The write can succeed while the read it was based on was wrong: a pagination that stopped early looks identical to one that finished; a platform's catalog page parses as user data; a deleted item stays in the database forever.
An asset ledger claimed 763 items; an ID-level read-back across 21 platforms found about 400 real ones — ghosts, misses, and false positives, each invisible on a dashboard. Counts partially cancel, which is why totals hide all three.
This entry is part of the untactit glossary. Definitions draw on measured write-ups published on the blog.
Connect one workspace and see every skill, rule, and memory your team has in play — in about ten minutes.
No credit card. Works with what you already run.