Server 58aab8aa from CI run 378 (1675bb6) lets DEV cellular sessions use the
4-hour grant ceiling. Region 4's genesis build e891f942 stays retained so the
region recovers under the new image.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Promotes server e891f942 and postgres-tools fe3558e9 (schema v38) from CI run 376
and moves the DEV region host and provision job to region 100/4 with the
cellular-v4 opening (rules 5): engulfment, detritus, budding wildlife, permadeath
and offline freeze. Regions 1-3 stay in the stores untouched. Recorded in
ADR-0123, the M11.9 plan and the validation log.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Promote server image 5e13e009 (Gitea run 365, source e9b010e): cellular
actions admitted every tick, births ticked only for held accounts, and
life outcomes valid on the wire. Retain faeb26fc, which wrote region 3's
genesis. Also refresh the dev session window (3 h).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first playable run showed two server faults. The client sends one
cellular action per tick (an idle tick carries no movement or intake),
but the default probe admission allowed 4 per 8-tick window, refusing
every other one; the cellular bridge now admits two per tick of window.
Region 2's opening starved the cell: only patch energy feeds the reserve,
and founder intake emptied its 4M and 16M pJ patches in seconds. DEV
moves to region 100/3 with 200M and 50M pJ patches (ADR-0123).
Also refresh the dev session window (3 h).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Promote server image faeb26fc (Gitea run 360, source 5e45be3), whose
provisioner resolves a cellular genesis under its recorded build, and
retain 1dd640eb. Also refresh the dev session window (3 h).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Promote server image 1dd640eb (Gitea run 358, source 56e7525), which
adds evo-world-clone provision --life-allocator-start (ADR-0123), and
retain the previous build 566c2932 that wrote region 2's genesis. The
provision Job now creates world 100's life allocator at
1,000,000,000,000. Also refresh the dev session window (3 h).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Region 100/1 holds lineage history and cannot host the cellular profile,
so dev provisions a fresh cellular-v1 genesis at region 2 and serves it
with --profile cellular and its --life-route catalog. Region 1's stores
are left untouched; it is 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 the lineage profile with the development opening.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ADR-0097. The second evolution-dev load drill (image 7952185d) held 20
sessions with client budgets met (response p95 111 ms, outcome p95 about
1.2 s, 20 Hz, no starvation) but the server over its own: tick work p99
48-70 ms (25 ms budget), session layer 1.2-2.0 ms per session at p99
(0.5 ms budget), governor refusing and shedding to level 3 to little
effect. ReplicationServer::tick re-encoded every environment cell and
organism for each session. Sessions with the same requested interest
(no perception predicate) now share one encoding per tick; markers stay
per session. Locally 21 sessions: about 970 us -> 360 us per tick.
The drill now waits for two consecutive calm reports before the bots.
The dev overlay's REGION_RETAINED listed the deployed build itself
(61df6a1, f88bee2), which the deploy policy refuses (CI deploy failed on
those commits); it now lists only the other builds, keeping 6c96629e,
the build of the region head. Refreshes the dev session window.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Complete the maintainer's server image bump to edb39f by also setting
the region build identity, and add REGION_RETAINED so the host keeps
the builds that wrote its history on its recovery allowlist; without it
the upgraded host would quarantine its own head as unsupported. Record
the M8.4 drill (rollout 3.0 s, forced deletion 19.3 s to Ready, epochs
3 to 5) and the maintainer's M8.5 sync.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploy evo-region per environment (ADR-0071): one replica with the
Recreate strategy (a rolling update would deadlock on the lease),
/readyz readiness, /livez liveness, no CPU limit and a drain inside the
grace period, with the image digest doubling as the build identity. A
new idempotent evo-world-clone provision subcommand creates genesis from
development_opening (byte-identical to the qualification fixture) as a
Sync hook after the migration. Dev and stage paths include their region;
a dev AppProject allows Deployment and Service; region-drill.sh times
rollout and forced-deletion recovery; the policy check enforces the
host's invariants.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>