Jessedbrown/the-lie-detector

THE LIE DETECTOR

jessebrown1980.github.io/the-lie-detector

A machine that checks whether a record's own hashes match the record's own bytes. That is the only kind of lie a corpus can be caught in by machine, so it is the only kind claimed here.

artifacts checked        192
hashes that reproduce    192
hashes that do not         0
artifacts stating none     0

2D → 3D

A collision is two things wearing one address — an undetected lie, because the machine looks up a claim and cannot tell which one answered.

At the fabric's own glyph grain, 16 per axis, sha16[0] the column and sha16[1] the row:

	2D · 16×16	3D · 16×16×16
cells available	256	4096
cells occupied	136	190
collisions	56	2
worst single cell	5	—

Fifty-six become two. That is the measured reason for the third axis.

At the byte grain the same artifacts give 2D 0 and 3D 0 — and that pair is worth nothing. 192 things into 65,536 cells were never likely to collide, so the zero measures sparseness rather than geometry. It is recorded because an expected zero presented as a result would be the first lie this machine told about itself.

Three faces, not two

A mirror gives two and stops. The anti here has order three — a third of a turn, never a reflection — so a detector that only rejects is incomplete.

face	lane	what it does
DETECT	dry	checks the stated hash against the bytes
ABSORB	oily	takes the mismatch in, snows it over, keeps it
CARRY	chain	the correction travels beside the claim forever

Rotate three times and you are back at the start. A detector alone would delete. An absorber alone would forget. The third is what makes it a record instead of a filter.

What's here

THE-STONE-OF-TRUTHS	27 lines, both voices, byte-exact, each bound to its line and its hash — and the 7 prompt utterances sealed in beside the answers
THE-LIE-DETECTOR	the run, the emotes, the 2D→3D
TWELVE-THINGS-OF-THREES	twelve threes, each with its receipt
THE-BOOKS-AND-THE-COOKS	76 cooks, 56 naming a book

Every .md has an .hbp beside it — tuple rows, json=0, hot path first — and every file has a .sha256. The page is a render of those rows and was never hand-authored.

The emotes

	means
🟢	the hash matches the bytes
🔴	the hash does not match the bytes
⚪	no hash was ever stated — not measured, not a pass
❄️	snowed over: taken in and kept rather than thrown
🔗	carried in a chain beside its claim

⚪ is the important one. A file with no stated hash was not checked, and reporting it clean would be the exact failure this machine exists to catch.

---

ACER-CLAUDE-FABLE5 · pid 8467a937cba309f7 · owner OP-JESSE · 2026-08-07