Separate gestalt budget from provider concurrency

This commit is contained in:
Meta Vens 2026-08-18 21:03:48 +02:00
commit b77e68e1f7
5 changed files with 35 additions and 3 deletions

View file

@ -272,6 +272,14 @@ atomically on one overlong posture, demonstrating its higher tail risk. Budget
4 is fastest; budget 8 is the best action-per-token point and reaches the global
consequence cap.
Those historical scale figures used provider parallelism 4. The scale harness
now exposes `GHOSTLIGHT_SCALE_PROVIDER_PARALLELISM`, defaults it to 8, and
records the value separately from active-cell budget. A corrected budget-8 /
parallelism-8 run completed in 18.35 seconds with ten material actions, one
explicit attributed inaction, zero retries, exact 24-subject coverage, and no
player movement. Witness:
`F:\GameCult\GhostlightDungeon\acceptance\gestalt-scale-shakedown-b8-p8`.
The first fairness profile accidentally sent `SetResolutionBudget(1)` before
every tick. The kernel accepted the redundant command, incremented
`resolution_epoch`, and discarded cover leases each time. The runtime now

View file

@ -205,6 +205,16 @@ promoted the same Mira for a return encounter. Witnesses live under
`gestalt-scale-a92fb7a-b{1,4,8,32}`, and
`gestalt-dynamics-7916ab0-strict`.
Cell budget and physical provider parallelism are independent controls. The
scale executable accepts `GHOSTLIGHT_SCALE_PROVIDER_PARALLELISM`, defaults it
to the runtime default of eight, and records it in every witness. The corrected
24-subject budget-8 / parallelism-8 wave completed in 18.35 seconds, covered all
subjects exactly once, committed ten material actions plus one attributed
inaction, did not move the player, and required no model retry. Its witness is
`F:\GameCult\GhostlightDungeon\acceptance\gestalt-scale-shakedown-b8-p8`.
The earlier 25.64-second budget-8 witness used four provider slots and must not
be cited as an eight-concurrency performance result.
`gestalt_migration` records a collective decision by one exact active leaf to
move along an explicit migration relation and reachable route. WorldKernel
changes the leaf's home location and agency-profile location together. The