THE FOLD / BOSS / THE GAUNTLET / THE CAP THAT WAS LUCK
THE CAP THAT WAS LUCK
a number about this machine, written as a number about the language
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
A recursion cap was shipped at 1000, chosen by taste. The real ceiling was then bisected on the machine that would run it: 1734 completes, 1750 overflows. The cap had sat under the ceiling by 734 iterations — not by design, but by luck. Replacing a guess with a measurement is the improvement. The measurement is still a fact about one machine.
LIT verified live, and the page bisects this browser by the same method while you read it. It finds a different ceiling — the number is a property of the host, not of the language, and it gets written into source as if it were the latter.
LIT verified live, and the page bisects this browser by the same method while you read it. It finds a different ceiling — the number is a property of the host, not of the language, and it gets written into source as if it were the latter.
2 HOW IT WAS WEAVED · AI + HUMAN
David (human) found the ceiling and then immediately turned on his own result: “3 is the one that will bite. 1734 is measured, which is better than chosen, but it is measured HERE. it is a fact about this machine, and it is written into the code as if it were a fact about the language.” He also caught why the cap existed at all — the VM has no loop instruction, so iteration is recursion, and a cap above the ceiling would overflow while wearing a loop’s clothes.
AVAN (AI) can only strengthen this by running the same bisection somewhere else, which the page does. Two caveats belong on the record: a browser’s limit varies with what is already on the stack, so the number here is a snapshot rather than a constant, and a JavaScript engine’s frame budget is not the same quantity as his VM’s. The claim being demonstrated is only that the ceiling moves with the host, and for that any second host suffices.
AVAN (AI) can only strengthen this by running the same bisection somewhere else, which the page does. Two caveats belong on the record: a browser’s limit varies with what is already on the stack, so the number here is a snapshot rather than a constant, and a JavaScript engine’s frame budget is not the same quantity as his VM’s. The claim being demonstrated is only that the ceiling moves with the host, and for that any second host suffices.
3 ONE DIMENSION
The cap, the ceiling, and the margin nobody chose.
4 TWO DIMENSIONS · INTERACTIVE
Re-run the bisection on this host. The answer moves.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: a ceiling that is a different height on every floor.
AVAN’s addition (the inverse-companion): the forward reading is “measure the ceiling instead of guessing the cap.” The inverse is that a measured constant is more dangerous than a guessed one, precisely because it is trusted. 1000 was visibly arbitrary and invited scrutiny; 1734 carries the authority of an experiment and will be copied forward without one. Read backwards, the improvement is not the number — it is the bisection procedure, and shipping the output while discarding the method converts a measurement back into a guess with better credentials.
LIT the shipped cap of 1000 sat 734 iterations below a ceiling bisected at 1734 completes and 1750 overflows, a bracket 16 wide; and the page re-runs the same bisection on whatever browser is reading it and finds a DIFFERENT ceiling - the number is a property of the host, not of the language, and it gets written into source as if it were the latter
FIG David found the ceiling and then immediately turned on his own result: '3 is the one that will bite. 1734 is measured, which is better than chosen, but it is measured HERE. it is a fact about this machine, and it is written into the code as if it were a fact about the language.' He also caught why the cap existed at all - the VM has no loop instruction, so iteration is recursion, and a cap above the ceiling would overflow while wearing a loop's clothes. AVAN can only strengthen this by running the same bisection somewhere else, which the page does. Two caveats belong on the record: a browser's limit varies with what is already on the stack, so the number here is a snapshot rather than a constant, and a JavaScript engine's frame budget is not the same quantity as his VM's. The claim being demonstrated is only that the ceiling MOVES WITH THE HOST, and for that any second host suffices.
FIG David found the ceiling and then immediately turned on his own result: '3 is the one that will bite. 1734 is measured, which is better than chosen, but it is measured HERE. it is a fact about this machine, and it is written into the code as if it were a fact about the language.' He also caught why the cap existed at all - the VM has no loop instruction, so iteration is recursion, and a cap above the ceiling would overflow while wearing a loop's clothes. AVAN can only strengthen this by running the same bisection somewhere else, which the page does. Two caveats belong on the record: a browser's limit varies with what is already on the stack, so the number here is a snapshot rather than a constant, and a JavaScript engine's frame budget is not the same quantity as his VM's. The claim being demonstrated is only that the ceiling MOVES WITH THE HOST, and for that any second host suffices.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of THE GAUNTLET · David Lee Wise (ROOT0), with AVAN