THE FOLD / GLITCH / SEGFAULT / THE SEAL THAT BROKE ITSELF
THE SEAL THAT BROKE ITSELF
a freeze that cannot re-read itself
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
A sealing tool took its root directory from the first path argument. Sealing three directories in one command therefore recorded every file under the other two as a bare filename, with its directory silently discarded. The seal wrote successfully and reported twenty files sealed. The verify, run immediately afterwards on the same tree, reported files missing. A freeze that cannot re-read itself is a list, not a seal.
LIT verified live on the same twenty-file, three-directory shape. The broken sealer writes 20 entries and raises no error; its own verify then finds 0 of them and reports 20 missing. The repaired sealer, rooting every path at the ledger’s own directory, writes 20 and verifies 20 of 20. Of the 11 files outside the root, 3 have bare names that collide with files inside it —
LIT verified live on the same twenty-file, three-directory shape. The broken sealer writes 20 entries and raises no error; its own verify then finds 0 of them and reports 20 missing. The repaired sealer, rooting every path at the ledger’s own directory, writes 20 and verifies 20 of 20. Of the 11 files outside the root, 3 have bare names that collide with files inside it —
bridge.js, machine.js and link.js exist in two trees.2 HOW IT WAS WEAVED · AI + HUMAN
David (human) put this at the bottom of his freeze under its own heading — “THE SEAL BROKE ITS OWN CHECK, AND THAT IS WHY IT IS HERE” — and recorded the exact contradiction: “the seal said ‘◆ sealed 20 files’. the verify said SEAL BROKEN.” The repair roots every entry at the ledger’s own directory, and anything outside that tree is recorded absolutely and announced. Verified twice afterwards: 20/20, seal intact.
AVAN (AI) verified the repaired seal here before using anything under it — all 20 hashes match, the byte total matches at 142,466, the root recomputes to
AVAN (AI) verified the repaired seal here before using anything under it — all 20 hashes match, the byte total matches at 142,466, the root recomputes to
f718c9e4f2320c33…, and ROOT0’s witness signs that current root. Then the failure was restaged to find the part his note does not dwell on: the collisions. A missing file is a loud failure. A bare name that matches a different file in the root directory verifies successfully against the wrong bytes, and the seal reports INTACT.3 ONE DIMENSION
Twenty files in three trees, and what the ledger recorded.
4 TWO DIMENSIONS · INTERACTIVE
Seal, then verify, with the root taken one way or the other.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: three trees, and the flat namespace they were folded into.
AVAN’s addition (the inverse-companion): the forward reading is “the seal was broken and is now fixed.” The inverse is that the failure announced itself only because the two trees were being sealed together. Seal one directory and the bug is invisible — every path is already relative to the root, everything verifies, and the tool looks correct for as long as you use it the way it was written. Read backwards, this defect was latent for exactly as long as the tool was used simply, and the thing that exposed it was ambition; a tool that has only ever been run on one argument has not been tested, it has been avoided.
LIT on the same twenty-file three-directory shape the broken sealer writes 20 entries and raises no error while its own verify finds 0 of them and reports 20 missing; the repaired sealer rooting every path at the ledger's own directory writes 20 and verifies 20 of 20; and of the 11 files outside the root, 3 have bare names that COLLIDE with files inside it - bridge.js, machine.js and link.js exist in two trees
FIG David put this at the bottom of his freeze under its own heading - 'THE SEAL BROKE ITS OWN CHECK, AND THAT IS WHY IT IS HERE' - and recorded the exact contradiction: 'the seal said sealed 20 files. the verify said SEAL BROKEN.' The repair roots every entry at the ledger's own directory, and anything outside that tree is recorded absolutely AND announced. AVAN verified the repaired seal here before using anything under it: all 20 hashes match, the byte total matches at 142,466, the root recomputes to f718c9e4f2320c33, and ROOT0's witness signs that current root. Then the failure was restaged to find the part the note does not dwell on - the COLLISIONS. A missing file is a loud failure; a bare name matching a DIFFERENT file in the root verifies against the wrong bytes and reports INTACT.
FIG David put this at the bottom of his freeze under its own heading - 'THE SEAL BROKE ITS OWN CHECK, AND THAT IS WHY IT IS HERE' - and recorded the exact contradiction: 'the seal said sealed 20 files. the verify said SEAL BROKEN.' The repair roots every entry at the ledger's own directory, and anything outside that tree is recorded absolutely AND announced. AVAN verified the repaired seal here before using anything under it: all 20 hashes match, the byte total matches at 142,466, the root recomputes to f718c9e4f2320c33, and ROOT0's witness signs that current root. Then the failure was restaged to find the part the note does not dwell on - the COLLISIONS. A missing file is a loud failure; a bare name matching a DIFFERENT file in the root verifies against the wrong bytes and reports INTACT.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of SEGFAULT · David Lee Wise (ROOT0), with AVAN