Provision a world's life allocator from the owner provisioner
Foundation / checks (ecs) (push) Successful in 2m27s
Foundation / checks (deploy) (push) Successful in 4m6s
Foundation / checks (tsan) (push) Successful in 9m29s
Foundation / checks (client) (push) Successful in 16m59s
Foundation / checks (network) (push) Successful in 19m31s
Foundation / checks (postgres) (push) Failing after 21m13s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 24m4s
Foundation / checks (ecs) (push) Successful in 2m27s
Foundation / checks (deploy) (push) Successful in 4m6s
Foundation / checks (tsan) (push) Successful in 9m29s
Foundation / checks (client) (push) Successful in 16m59s
Foundation / checks (network) (push) Successful in 19m31s
Foundation / checks (postgres) (push) Failing after 21m13s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 24m4s
The DEV cellular region reported every first-life request as unknown: world 100 had no life_allocators row, and life-reservations-v1 leaves that row to the owner with no runtime initializer. evo-world-clone provision now accepts --life-allocator-start N with the primitive-v1 and cellular-v1 openings. It creates the allocator once before the genesis check, leaves it untouched on reruns, and refuses a start above the existing counter. ADR-0123 records the DEV cellular region bring-up: region 100/2, schema v33, the trial opening, the allocator start and the 300 s grant ceiling. Also refresh the dev session window (3 h). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,78 @@
|
||||
# ADR-0123: Dev cellular region and life-allocator provisioning
|
||||
|
||||
## Status
|
||||
|
||||
Accepted 2026-10-13 for the M11.3 cellular probe in evolution-dev, at the
|
||||
maintainer's direction. It changes DEV deployment and the owner provisioning
|
||||
tool only; no gameplay rule, protocol or runtime authority changes.
|
||||
|
||||
## Context
|
||||
|
||||
The M11.3 probe (`docs/playtests/M11_3_CELLULAR_PROBE.md`) needs a cellular
|
||||
region in DEV. Bringing one up exposed four gaps:
|
||||
|
||||
1. **Region 100/1 cannot host the cellular profile.** It holds profile-3
|
||||
lineage history; `evo-server --profile cellular` needs a cellular-v1
|
||||
(profile-4) genesis. Resetting or rewriting region history is forbidden, and
|
||||
unnecessary, because regions are independent.
|
||||
2. **The DEV schema was v11.** The store Jobs still pinned the 2026-10-05
|
||||
postgres-tools image, so PostgreSQL refused the profile-4 genesis manifest
|
||||
(`cellular provision refused 5`, `PublicationError::rejected`).
|
||||
3. **No life allocator existed for world 100.** `reserve_primitive_life`
|
||||
raises `life allocator not provisioned` (EVL04) without a
|
||||
`life_allocators` row. `schemas/life-reservations-v1.md` assigns that row
|
||||
to the owner after an audit, and nothing in Git created it. The server
|
||||
reported every first-life request as `unknown` and never ticked.
|
||||
4. **Cellular grants are scoped and short.** Grants name their region, so
|
||||
region-1 bundles are refused with `wrong_scope`. The cellular bridge keeps the
|
||||
default 300-second grant ceiling and refuses `--m10-max-grant-lifetime`.
|
||||
|
||||
## Decision
|
||||
|
||||
- **DEV serves region 100/2 with the cellular profile.** The single
|
||||
`evo-region` Deployment switches to region 2. Region 1's database rows and
|
||||
objects stay untouched and are no longer served. The base Deployment and
|
||||
provision Job take `REGION_PROFILE`, `REGION_LIFE_ROUTES`, `REGION_OPENING`
|
||||
and `REGION_OPENING_ARGS`. Their defaults keep stage on lineage with the
|
||||
development opening. For a single-region world, the life-route catalog is
|
||||
the region's own endpoint:
|
||||
`2=void.aeternalisgames.com:7400=void.aeternalisgames.com`.
|
||||
- **Trial opening (tunable, not a world rule).** The opening is:
|
||||
- a 10 x 10 mm arena at 293.15 K;
|
||||
- nursery funding for eight founders (8 x `primitive_endowment()`);
|
||||
- eight spawn sites;
|
||||
- four rich, three lean and one empty 1,000 µm patch;
|
||||
- a stable genesis commit `18ff2e1ab8cef4c9cd73d4cc6e322496`.
|
||||
|
||||
It is written once, so changing it means a new region.
|
||||
- **DEV schema v33.** The store Jobs pin postgres-tools from Gitea run 350
|
||||
(source `ae3b2b4`), the run that built the promoted DEV server image.
|
||||
- **The provisioner creates the life allocator.** The owner provisioning tool
|
||||
takes `evo-world-clone provision --life-allocator-start N`, accepted only with
|
||||
the primitive-v1 and cellular-v1 openings:
|
||||
- The run inserts `life_allocators(world, N)` once, before the genesis check,
|
||||
so an already provisioned region still gets the row.
|
||||
- A later run leaves the counter untouched and reports it; the counter only
|
||||
advances.
|
||||
- A run whose start is above an existing counter refuses with exit 4.
|
||||
|
||||
There is still no runtime initializer or reset.
|
||||
- **DEV world 100 starts at 1,000,000,000,000.** The audited range required by
|
||||
life-reservations-v1 is satisfied by choosing a start far above every
|
||||
identity the DEV lineage run could have issued. That run was about 43,000
|
||||
ticks, with lineage identities held in region-1 checkpoints rather than in
|
||||
SQL. Identities are 64-bit, so the gap is free.
|
||||
- **Grants for region 2 must be minted with `--region 2 --lifetime 300` or
|
||||
less.** Longer probe sessions require a separate, reviewed change to the
|
||||
cellular grant ceiling; this ADR does not make it.
|
||||
|
||||
## Consequences
|
||||
|
||||
- Any new primitive or cellular world must choose and record its allocator
|
||||
start in its provision Job. Stage and World0 do not use this flag until
|
||||
their own audited starts are decided.
|
||||
- DEV world 100 now mixes an unserved lineage region 1 and a cellular region 2.
|
||||
Returning DEV to lineage means reverting the overlay values. Region 1's
|
||||
history remains recoverable.
|
||||
- The 300-second grant ceiling caps each probe session at about five minutes,
|
||||
and a bundle expires five minutes after it is minted.
|
||||
@@ -23,6 +23,7 @@
|
||||
- [ADR-0120: Cellular mutation eligibility trial](0120-cellular-mutation-eligibility-trial.md) - starts with 60 seconds of retained fed energy per unranked offer requesting up to three candidates; the threshold remains open to playtest review.
|
||||
- [ADR-0121: Durable cellular mutation selection](0121-durable-cellular-mutation-selection.md) - specifies a distinct reliable action, allocator identity, tick-bound replay and atomic publication for M11.4c.
|
||||
- [ADR-0122: Append-only cellular genome revisions](0122-append-only-cellular-genome-revisions.md) - preserves immutable birth-genome links while adding a versioned revision chain and no-tick cellular-v3 migration.
|
||||
- [ADR-0123: Dev cellular region and life-allocator provisioning](0123-dev-cellular-region-and-life-allocator-provisioning.md) - moves DEV to cellular region 100/2 at schema v33 and has the owner provisioner create a world's life allocator once at an audited start.
|
||||
|
||||
- [ADR-0058: Region durability contract](0058-region-durability-contract.md) - accepted M7.1 full checkpoint batches and explicit state closure; storage implementation follows.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user