Gravity map: B39 planets drawn at the step; drawn-pose and tail-taming cut lines

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-10-15 21:12:35 +02:00
commit 46af8d4f09

View file

@ -76,6 +76,7 @@ All read at c6519383 in the detached worktree `C:\aeth-wt\ag2-docs` on 2026-10-1
- **B36. Readers of the period and of orbit velocity at 8f491fd3.** Period writers: `Orbit`'s constructor (Zone.cs:849-853, `settings.OrbitPeriod.Evaluate(data.Distance)`), `AsteroidBelt.Pose` per asteroid per call (Zone.cs:765), `BeltTargets` (BeltTargets.cs:63, which must divide by the same float Pose does). Readers of `Orbit.Period`: `GetOrbitPosition` (Zone.cs:484-486, which moves an orbit only when Period > .01) and three tests (ZonePlacedAtBuildTests.cs:113, 137, 143; RunStartTests.cs:325). `Zone.CreateOrbit` is gone (B17's dead writer was deleted). Orbits are constructed (Zone.cs:159-162) and placed (:167-168) before any body exists (:170-195), and `BeltTargets` is built inside the body loop (:181), so a period that reads a parent's well needs the bodies first: construct orbits, build bodies, derive periods, then place and build belt targets. Orbit velocity is a difference of placed positions (Zone.cs:283-287); `OrbitalEntity.Update` copies it to stations and turrets (OrbitalEntity.cs:30-31) and a docked ship copies its parent's (Entity.cs:1891). Docking checks distance only, 25 u (ActionGameManager.cs:896-897, `DockingDistance`), never relative speed; undocking keeps the station's velocity. AI `MoveToOrbitState` chases the orbit's position at TopSpeed (100) with no lead (MoveTo.cs:18-38); turrets lead targets by `target.Velocity` (TurretController.cs:68). So faster rails (B35) break no mechanism: a pilot holds within 25 u of a station moving 14-24 u/s (48 at most), where today it moves 6.3. No Unity-side code reads `OrbitPeriod` or `Period` (git grep). Tests that set `OrbitPeriod`: GravitySubtractTests.cs:49, MiningCut1Tests.cs:40, MiningCut2Tests.cs:43, MiningCut3Tests.cs:54, MiningIndexTests.cs:461, PotentialOwnerTests.cs:49, 86, 141, WellFixture.cs:13, ZonePlacedAtBuildTests.cs:45; MiningCut1Tests.cs:100-116 re-implements the curve. Fixtures whose parents carry no well (they move today only because the curve ignores the parent): ZonePlacedAtBuildTests (bodyless root; a bodyless moon under the moon's moon), MiningCut1Tests (a parentless root orbit at Distance 4000 that circles its FixedPosition, a shape the generator never makes: generated roots sit at distance 0), and MiningCut3Tests and MiningIndexTests (belts round a SunData of mass 0 under a PlanetSettings with no WellStrength, so c = 0). c = 4π² gives T = d exactly outside the core, today's game periods. The Lagrange station orbit adds PI/3 to Phase (ZoneGenerator.cs:264), but Phase is in turns (`OrbitData.Evaluate`, ZoneData.cs:234-237), so a station sits 0.047 turns (17°) from its planet, not at L4 or L5 (follow-up `lagrange-phase-in-turns`).
- **B37. Bodyless parents and the ring law.** ZoneGenerator's `ExpandRosette` (ZoneGenerator.cs:551-592) leaves the parent node empty and puts n children on one circle at phases i/n; binaries are rosettes of two (:484-487), roots can be rosettes of suns (the probe's 321 empty root suns), and a later `ExpandSolar` on an empty node adds outer children beyond the ring. In 2D a point of strength c_j at distance s on the same circle pulls a ring member inward by exactly c_j/(2d) (radial part of c_j/s with s² = 2d²(1-cos θ)), so a ring member's rail is v² = ½·Σ_{j≠i} c_j; and by 2D Gauss's law, which holds for log potentials, a ring exerts c_ring/d on anything outside it and nothing on anything inside it. So the field gives every child of an empty node a definite pull: the strength of its siblings strictly inside its distance, each with its whole family (a sibling's moons orbit with it), plus half the strength of siblings on its own circle (within 0.1 u, the generator's own rosette test, ZoneGenerator.cs:227) when the child itself carries strength. The last clause keeps a bodyless companion (a station or turret orbit at a planet's distance) on its planet's period: neither the planet nor its companion counts the other. Probed: no child of a generated zone is left without a field under this rule (B35), and nested binaries (an empty binary member that holds its own binary) get the ring term through their family's strength.
- **B38. Parent-only rails against the summed field** (`o1.py`). By 2D Gauss's law (B37) the phase-averaged pull at a child's distance from a body parent is the parent plus every sibling inside that distance, each with its family; siblings outside pull nothing on average. The circular speed of that enclosed field over the parent-only rail speed (B35), p10/p50/p90/p99, by the child's class: suns (children of a root or rosette) 1.44/1.98/2.44/2.75, gas giants 1.00/1.58/2.14/2.55, planets 1.00/1.21/1.65/2.05, planetoids 1.00/1.00/1.37/1.61, belts 1.00/1.14/1.49/1.88. Enclosed speeds: suns' children 24.4/46.0/60.3 u/s, planets 11.0/21.8/32.3. So under the funnel the operator kept (`funnel-kept-until-flown`), a ship coasting free at a body's orbital radius, away from the body, needs 1.2-2x the body's rail speed; patched conics' premise, that the parent dominates, is weak where c ∝ m^0.2 (the root holds 18% of a zone's total c, B19). The enclosed rule would also break field-strength-ruled's 12-18 u/s for planets round a median sun. Question `aetheria-gravity:question:rails-enclosed-or-parent` carries the fork; the two options differ by one term in one function.
- **B39. Planets are drawn at the step, the camera at the drawn time** (source read and Yggdrasil probe at 09ec04a8, 2026-10-15, after the operator's flight: "if I look at the planet while doing that, it jumps back and forth every frame"). `ZoneRenderer.Update` places each planet at `Zone.GetOrbitPosition` (ZoneRenderer.cs:582-585), the cached `Orbit.Position` the last `Zone.Update` wrote (Zone.cs:507-532), with no `Lead`; ships, and through them the follow camera, are drawn `Lead` past that step (EntityInstance.cs:405, B32). The sim runs before every presenter in the frame (ActionGameManager executionOrder -10, ZoneRenderer 50), so the gap is one of clocks, not of order. Probe (`DrawnPoseProbe.cs`, Imagination scratchpad `imagination-ag3-planet-jitter/`, via ygg-verify): a ship kept 60 u beside a planet moving 20 u/s, sim at 60 steps/s; planet-minus-ship along the motion spans 0.306 u at 144 Hz with 239 reversals in 286 frames (75 Hz 0.27, 120 Hz 0.17 reversing every frame, 165 Hz 0.30, 240 Hz 0.25, 60 Hz 0). Amplitude is the planet's speed x Step, so orbits-from-field (B35) made it 2.65x larger. Evaluating the orbit at `ExactTime + Lead` gives 0.0002 u and no reversals. Also drawn at step time: belts and the belt UI (`EvaluateBelt` at `_time`, ZoneRenderer.cs:546-549, 719), the drawn wells (GravityLowering.cs:53), loot and mines (`Body.Position`, ItemPickup.cs:43-44, MineInstance.cs:58-59), the chunk reticle (ActionGameManager.cs:1184) and the flow clock (VolumeSampling.cs:112); the ship's drawn ride height reads wells at step positions (source-read consequence, unprobed). Stations, clouds and rounds are already drawn ahead. `LookAtPoint` and group aims read the previous frame's drawn transform (EntityInstance.cs:396 before 405-406). Fixed by `cut-drawn-pose-at-drawn-time.r1`.
## Model page
@ -121,6 +122,8 @@ Cells not filled, plainly: whether a per-body multiplier on c or the core is eve
Mapped and admitted (2026-10-14, base 11b2d7ad): `aetheria-gravity:cut_spec:cut-gravity-subtract.r2` and its sibling `aetheria-gravity:cut_spec:cut-orbits-placed-at-build.r1`, both merged at 5dd1f6b7. Mapped and admitted (2026-10-14, base 5dd1f6b7): `aetheria-gravity:cut_spec:cut-potential-owner.r3` (rebased on 3f5cef68 on 2026-10-15, after rulings `funnel-kept-until-flown` and `core-inside-roche-curve`), one Hands pass; it carries follow-ups `deep-orbit-placement-test` and `gravity-subtract-test-residuals`. Between it and grid-lowering the drawn grid lags (B23). The operator will fly the funnel before ruling on it again (`funnel-kept-until-flown`), so potential-owner and grid-lowering must both be on one playable branch before that flight; grid-lowering is stacked on potential-owner, not a sibling (B26), and its map is the next Imagination pass once potential-owner's report lands. Mapped and admitted (2026-10-15, base dd06f39d, stacked on potential-owner's head): `aetheria-gravity:cut_spec:cut-grid-lowering.r1`, one Hands pass, Starfire-verified; on its branch the drawn grid is the field (B30) and the Sector Waves noise is off the grid until grid-noise-presentation. Mapped and admitted (2026-10-15, base 8f491fd3, stacked on grid-lowering's head): `aetheria-gravity:cut_spec:cut-fog-precision-and-jitter.r1`, the slope jitter (B32) and the patch's second gravity lowering (B33), one Hands pass. Mapped and admitted (2026-10-15, base 8f491fd3, a sibling of fog-precision-and-jitter on grid-lowering's head, disjoint files): `aetheria-gravity:cut_spec:cut-orbits-from-field.r1`, periods from the field (B35-B38), one Hands pass; it raises `aetheria-gravity:question:rails-enclosed-or-parent` and is written for the recommended parent-only option. Not yet mapped:
- **drawn-pose-at-drawn-time** (mapped and admitted 2026-10-15, base 09ec04a8: `aetheria-gravity:cut_spec:cut-drawn-pose-at-drawn-time.r1`, one Hands pass): `DrawAhead` owns every drawn pose at T = ExactTime + Lead (B39); closes item 3 of `fog-jitter-residuals`.
- **tail-taming** (ruling `tame-tails-parent-only-rails`): the wells' tails are tamed so the parent dominates near its children and parent-only rails are honest; mechanism waits on the Eyes pass `docs/research/gravity-tail-taming.md`, then Imagination.
- **potential-owner** (mapped, above): one ServerShared potential (c from an authored compressed curve G·m^p, authored core-radius curve, uniform-disc core, log tail, superposition, analytic gradient, no gate, global K in PlanetSettings, reference zero at the root's zone radius); every CPU force reader (Ship, floating bodies, clouds, mines) and `Zone.Flow`'s slope term read it; GetHeight = φ/K; deletes `GravityAcceleration`, `GravityReferenceRate`, `GetNormal` as a force source, the PowerPulse well and `GravityDepthExponent`; field strength per field-strength-ruled. Waits on both admitted cuts. May split into the potential and its readers if one Hands pass cannot hold both.
- **children-within-reach**: ZoneGenerator places children inside a fraction of the parent's tidal radius and the core radius inside the innermost child (softening-radius-ruled); tested over generated zones. It reads `Planet.RocheLimit` (lower bound) and half the tidal radius (upper bound); the windows per class are in B25, and a body with no window (4-7% of small bodies) gets no children. Seam: it places children on GeneratorPlanets before any Zone exists, so it needs the strength a child's rail obeys (`Zone.PeriodAround`'s pull: parent well, or the ring law for bodyless parents) over generator data; it lifts that pull to a pure function both read, rather than spelling the ring law a second time, and its tidal radius uses the same pull. Waits on orbits-from-field.
- **grid-noise-presentation**: the Sector Waves noise (after grid-lowering on layer 10, drawn only into the nebula patch height) and fine-grid detail move to non-slope presentation (grid-gravity-only-ruled); it also owns the Main Menu's own Surface Displacement brushes (B29, follow-up `menu-grid-brushes`). Waits on grid-lowering.