◀ THE FOLD0ROOT.AI // WORLD II · RESPAWN · THE RESURRECT◆ .dlw.fold
THE FOLD / RESPAWN / THE RESURRECT / THE SHARED TERMINATOR

THE SHARED TERMINATOR

two loops, one CONTINUE
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
FORTRAN 77 permits two DO loops to end on the same labelled statement. Two openers, one closer, and it is entirely legal. A pushdown check pops once, finds nothing illegal, and leaves a phantom frame on the stack — then a discharge step tidies the leftover away and reports clean. The check is not wrong at any single step; it simply cannot see the shape.

LIT verified live. The nested shared terminator gives 2 opens, 1 close, 0 illegal closers and 1 unclosed frame — a clean report over a wrong state. Two nested chambers in the suit give 3 opens, 3 closes and a depth of 0 at the end, because every chamber carries its own closer and there is no label to share.
2 HOW IT WAS WEAVED · AI + HUMAN
David (human) found the case that broke his veto and wrote both halves down: the FORTRAN shape with its one-frame drift, and the conclusion — “the fix for a parser that cannot see an ambiguity is not always a smarter parser. sometimes it is a grammar that cannot express the ambiguity.” The suit is that grammar; his suite passes 15/15, twice.

AVAN (AI) should record one difference honestly. David reports max nesting 1 for two nested chambers; the bracket model here measures a max nesting of 3, because it counts literal delimiters rather than chamber frames. The figures that carry the claim — 3 opens, 3 closes, depth back to 0 — agree exactly. The nesting number depends on which representation you count, and this page counts brackets, so it reports its own.
3 ONE DIMENSION
The stack, walking a shared terminator.
4 TWO DIMENSIONS · INTERACTIVE
Nest more loops on one label and watch the drift grow.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: frames opened, and the one that never closes.
AVAN’s addition (the inverse-companion): the forward reading is “the shared terminator is a defect the veto cannot see.” The inverse is that FORTRAN’s designers were not being careless — sharing a terminator saved a line on a punched card, and on hardware where a program was a physical stack of cards that was a real economy. Read backwards, the ambiguity is a fossil of a constraint that no longer exists, and the reason it survives is that the language kept its promise of compatibility; every parser since has had to see a shape that was rational in 1977 and is merely dangerous now.
LIT the nested shared terminator gives 2 opens, 1 close, 0 illegal closers and 1 unclosed frame - a clean report over a wrong state; while two nested chambers in the suit give 3 opens, 3 closes and a depth of 0 at the end, because every chamber carries its own closer and there is no label to share

FIG David found the case that broke his veto and wrote both halves down: the FORTRAN shape with its one-frame drift, and the conclusion - 'the fix for a parser that cannot see an ambiguity is not always a smarter parser. sometimes it is a grammar that cannot express the ambiguity.' AVAN records one difference honestly: David reports MAX NESTING 1 for two nested chambers, while the bracket model here measures 3, because it counts literal delimiters rather than chamber frames. The figures that carry the claim - 3 opens, 3 closes, depth back to 0 - agree exactly. The nesting number depends on which representation you count, and this page counts brackets, so it reports its own.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of THE RESURRECT · David Lee Wise (ROOT0), with AVAN