docs(fulgora): implementation plan for Voronoi primitive + elevation preview (#27) - #158
Merged
Merged
Conversation
…preview (#27) Twelve tasks off the merged spec. Tasks 2-6 are the reverse-engineering ladder, one task per rung, and they deliberately carry NO fitted constants - those are the measurements. Each instead names its candidate set, its discriminators, its falsification criterion and its disassembly backstop, plus a vacuity guard that must fail when the answer is deliberately broken. Task 5's guard is the one that matters most: forcing the search range back to the pre-2.1.7 3x3 must fail a fixture case, and if it does not, the probe positions are in the wrong place and need regenerating before the task can be called done. Tasks 7-9 transcribe the chain, with Task 9 naming the four nodes that look central but are unreachable, and the two that look deferred but are not. Task 10 checks the land/ocean argmax against the game's own get_tile and reports offending coordinates rather than a bare count.
This was referenced Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Twelve-task implementation plan off the spec merged in #157. Docs only.
Plan:
docs/superpowers/plans/2026-08-05-fulgora-voronoi-elevation-v1.mdShape
buildVoronoiExpressionoracle probe buildercell_idhash, point offsets, search range)makeVoronoiwith the shared per-cell point cacheget_tileWhy Tasks 2-5 contain no fitted constants
They are the measurements. Writing a speculative hash or normalisation divisor
into the plan would produce exactly the failure the spec exists to prevent - a
port and a fixture agreeing with each other while both disagree with the game.
Each RE task instead specifies the probe code, the capture command, the gating
test, the candidate set to try, the discriminators between candidates, the
falsification criterion, and the disassembly backstop if fitting stalls.
Vacuity guards
Every RE task carries one - a deliberately wrong variant that must break the
test. Task 5's is the sharpest: forcing the search range back to the pre-2.1.7
3x3 must fail a fixture case, and if it does not, the probe positions are not in
the corners where the two behaviours differ and need regenerating before the
task counts as done. A guard that cannot see the regression it exists to catch
is worse than none.
Open questions now have owners
175 - slider_to_linear(...)neednot be integral) -> Task 7 Step 2. If the game disagrees with the test, the
implementation changes, not the expectation.
distance_typemove points? -> Task 4 Step 2. Load-bearing: Task 6'sshared point cache depends on it, and a refutation changes Task 6's interface.
|scrap_medium + dunes| ~ 0thin spot -> Task 10 Step 5.Execution
Subagent-driven, with a hard rule that any of Tasks 2-5 returning "fitted,
mostly" is rejected rather than merged.
🤖 Generated with Claude Code
https://claude.ai/code/session_01QZvNS2H4cbaZk46ybA7hbj