THE FOLD / RESPAWN / ROLLBACK / THE STALE WITNESS
THE STALE WITNESS
a signature attests a moment, not a file
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
A signature on a ledger does not sign the ledger. It signs a number the ledger had at one moment. Change anything afterwards and the signature survives untouched — still valid, still verifiable, still someone’s real mark — while quietly ceasing to attest to what is now in front of you. The only way to notice is to keep the root the witness signed and compare it against the root you have.
LIT verified live: 500 single-digit edits were made to a sealed ledger. Every one of the 500 moved the root. A checker asking “is there a signature?” caught 0 of them. A checker comparing the signed root against the current root caught 500 of 500. And a perfectly legitimate append — one new file, nothing removed — trips the second checker just as hard, because what it detects is change, never wrongness.
LIT verified live: 500 single-digit edits were made to a sealed ledger. Every one of the 500 moved the root. A checker asking “is there a signature?” caught 0 of them. A checker comparing the signed root against the current root caught 500 of 500. And a perfectly legitimate append — one new file, nothing removed — trips the second checker just as hard, because what it detects is change, never wrongness.
2 HOW IT WAS WEAVED · AI + HUMAN
David (human) built the mechanism into
AVAN (AI) measured what the drift flag can and cannot tell you, and the second half matters more. It emits exactly one bit: the root moved. It cannot say whether a file was tampered with or a new skill was legitimately added, and both cases look identical to it. That is not a defect to fix — a comparison of two opaque numbers has nowhere to put a reason — but it does mean the flag is a prompt to go and look, not a verdict, and reading it as a verdict is the failure mode.
seal.py: each witness record stores root_at_signing, and the display routine prints a mark beside any signature whose stored root no longer matches — signed a DIFFERENT root. It is four lines and it is the difference between a register and a ritual. He seated this at ROLLBACK.AVAN (AI) measured what the drift flag can and cannot tell you, and the second half matters more. It emits exactly one bit: the root moved. It cannot say whether a file was tampered with or a new skill was legitimately added, and both cases look identical to it. That is not a defect to fix — a comparison of two opaque numbers has nowhere to put a reason — but it does mean the flag is a prompt to go and look, not a verdict, and reading it as a verdict is the failure mode.
3 ONE DIMENSION
Two checkers, five hundred edits.
4 TWO DIMENSIONS · INTERACTIVE
Edit the ledger under the signature and watch what each checker says.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: a signature anchored to one point, and the ledger drifting off it.
AVAN’s addition (the inverse-companion): the forward reading is “bind the signature to the root so drift is visible.” The inverse is that this makes every legitimate change look exactly like an attack. A corpus that grows must re-sign constantly, and a flag that fires on all normal activity is a flag people learn to clear without reading. Read backwards, the drift bit does not protect the ledger; it transfers the work to a human, and its real design question is not sensitivity but how often it will cry out for nothing — because the honest answer is every single time anything is added.
LIT 500 single-digit edits were made to a sealed ledger and every one of the 500 moved the root; a checker asking 'is there a signature?' caught 0 of them while a checker comparing the signed root against the current root caught 500 of 500; and a perfectly legitimate append - one new file, nothing removed - trips the second checker just as hard, because what it detects is CHANGE and never wrongness
FIG From David's seal.py: each witness record stores root_at_signing, and the display routine prints a mark beside any signature whose stored root no longer matches - 'signed a DIFFERENT root'. Four lines, and the difference between a register and a ritual. AVAN measured what the drift flag can and cannot tell you, and the second half matters more: it emits exactly ONE BIT, the root moved. It cannot say whether a file was tampered with or a skill was legitimately added, and both look identical to it. Not a defect to fix - a comparison of two opaque numbers has nowhere to put a reason - but it means the flag is a prompt to go and look, not a verdict.
FIG From David's seal.py: each witness record stores root_at_signing, and the display routine prints a mark beside any signature whose stored root no longer matches - 'signed a DIFFERENT root'. Four lines, and the difference between a register and a ritual. AVAN measured what the drift flag can and cannot tell you, and the second half matters more: it emits exactly ONE BIT, the root moved. It cannot say whether a file was tampered with or a skill was legitimately added, and both look identical to it. Not a defect to fix - a comparison of two opaque numbers has nowhere to put a reason - but it means the flag is a prompt to go and look, not a verdict.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of ROLLBACK · David Lee Wise (ROOT0), with AVAN