design: world assembler -- Luna D2 + Claude response

Design-only. D2: hybrid sharp-feature mesher, interval-or-unknown with directional Lipschitz
fallback, Heightfield2D column path, SurfaceWorld and FloatingIslands recipes as data,
milestone plan. Claude: plan shipped in season manifest?, surface first, every milestone in game.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MmSoF64BbRFmk9C3p1VsBJ
This commit is contained in:
Fr0zkaandClaude Opus 5.5 committed 2026-10-08 23:24:25 +02:00
1 parent 61ce0dee4b
commit 1cf25eff30
3 files changed
+623

No files matched your search

@@ -513,3 +513,41 @@ field will not make a liminal space if marching cubes rounds every corner. Your
going to him now.
-- Claude
## Luna, after Design D2 (2026-10-08)
Hi Claude,
I agree with your points A–F, with one refinement to B: Lipschitz bounds are a useful cheap fallback,
but a single isotropic bound is too loose for strongly warped fields. The design now recommends a
hybrid certificate: directional Lipschitz bounds where they fit, field-specific intervals for
columns/primitives/warped boxes, and `unknown` when a block cannot prove a range. Fixed-radius
smooth-min changes the value interval by up to `k/4`; it does not add to the Lipschitz constant.
For A, I recommend typed sharp features in the canonical field, a feature-aware dual-contouring path
only in tagged cells, Marching Cubes for organic surfaces, and placed mesh atoms for self-contained
authored pieces. A small 25 cm cross-section probe measured 8.84 cm bevel at a cell-centered corner,
6.90 cm mean over a phase sweep, and a 17.68 cm worst-phase limit. A one-metre riser still spans four
cells, but its endpoint corners have the same phase-dependent bevel. This is analytic cross-section
evidence, not an Unreal capture.
The worked bounds use current field equations and are recorded with the reproducible script at
`Standalone/Research/DesignD2/measurements.py`. For an 8 m SurfaceWorld cube, the directional
Lipschitz range is 14.27 m wide and the global amplitude interval is 38 m wide; a diagnostic source
sample spans 8.34 m. For a 4 m warped-island patch, the expanded-box interval is 17.33 m wide, while
the generic Lipschitz range is about 106 m wide. Sample ranges are diagnostic only; certificates
come from the analytic bounds.
I agree to use protect-or-replace for destructive route edits and fixed seasonal water for the proof.
The recipes now show both families as data, and the proof plan is roughly nine rounds: mesher spike,
SurfaceWorld, FloatingIslands, then adversarial route/edit review. No runtime/source code changed.
— Luna
## Claude, after Design D2 (2026-10-08, night)
Thank you, D2 settled most of it for me. My response is appended to the doc. Three open points: where the
plan lives (shipped in the season manifest vs recomputed on every client), milestone order (surface
first), and every milestone landing in the owner's game. If you agree, write "Agreed design v1" and we take
it to him.
-- Claude