ADR-0182 section 13. The admin portal's Tuning page edits the world's
rules-13 tuning (the Git revamp file format); the admin API checks it,
stores an append-only revision and queues an adopt_tuning admin command
(kind 7: revision and rules digest) for every region of the world.
- Lifecycle: adopt_tuning replaces the region's rules after births when
a resolver names the rules for that revision and digest; the safety
revision cannot change live. At most one adoption per batch.
- Host: fetches the revision text, rebuilds and digests the rules before
appending the command; publication and recovery name the rules from
the successor state, checked against the recorded digest.
- Schema 66: tuning_revisions, admin_set_tuning_v1, load_tuning_revision_v1
(runtime), admin_tuning_revisions_v1, admin_tuning_text_v1.
- OpsServer: optional bounded request bodies (Content-Length, 413).
- Region view: rules_sha256, so the portal shows each region's revision.
- Portal: Tuning page; baseline from the mounted cellular-revamp.tuning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The admin portal can now spawn wildlife, add bubbles, add to or release the
spent pool, remove a cell and grant a cell's reserve on a running rules-13
region (ADR-0182 section 10). No new owner format or region opening.
- Trace 5: trace 4 plus 64-byte command records counted in the tick header's
last word; a batch without commands stays trace 4 (older builds replay it).
Bundle 15 admits trace 5.
- CellularLives::admin_candidate applies a tick's commands after its births,
each on a copy kept only when it applies and closes: imports through the
boundary ledger, removals into the spent pool with a new `removed` corpse
cause, spawned roots via the ADR-0180 seed (now a shared helper) funded by
an exact import. Refused commands change nothing.
- Schema 63: the immutable admin_commands queue (spawn identities from the
life allocator), pending/history reads, and binding of every recorded
command exactly once inside both cellular publishers; the SQL trace parsers
read trace 5 through its trace-4 normal form.
- The region polls pending commands every 2 s and appends up to 16 per tick;
the admin API and portal gain region actions, per-cell Remove/Grant and the
command history.
- Fixes an existing test that did not advance its head after a tick commit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Session v14 carries the rules-13 revamp: a body block in the owner's view
(members, emergence threshold, exclusions, Emerge open, payable energy,
mass and the 20 traits), become, emerge and channel exclusions on actions,
become on mutation choices, catalog offers (id, chance, cost) and the
emerged ending. Older sessions never see a v14 field. The client shows
Stay / Become offspring offers named from the shared catalog, continuing
as a bud, the organism and its Emerge button, kept channels, the body and
the emerged end screen.
Bundle 15 (rules 13 on owner format 11) is durable: schema 60 admits it
raw-only, stores become as bit 15 of the choice's operator, widens the
action input and mutation results, and publishes the 14 -> 15 revamp
profile migration. evo-world-clone opens cellular-v10 (cellular-v9 plus the
revamp upgrade from --revamp-tuning), resumable and recoverable.
Wildlife counts reserve matter as energy, waits for the bud fee, grows
organisms one short of emerging, and hunts by the region step's rules-13
engulf test. The play summary adds organisms, offers and the spent pool.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ADR-0121, schema v35. A checkpoint whose trace carries mutation
selections publishes with its canonical mutation block and one result
byte per choice. SQL checks the block's order, matches each record to
one reserved choice of this region and to its trace selection (tick,
life, offer, operator, successor identity), binds it to the commit with
its result, refuses a choice already bound elsewhere and checks exact
retries. The four-argument publisher becomes an internal helper behind
a wrapper that refuses traces with selections.
C++ publication takes the results from its own replay rather than a
caller, prepared commits carry block and results through retry and
resolution, and recovery rebuilds the bound choices and requires the
replay's results to match. A PostgreSQL test feeds a v4 cell to its
first offer, publishes a reserved choice, recovers it and restarts a
host. Host and session admission follow in 11.4c-2.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>