Commit Graph
699 Commits
Author SHA1 Message Date
dingo bda1631ded Finish birth refusal integration and stabilize client panel checks
Foundation / checks (checks) (push) Successful in 42m5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m24s
Foundation / checks (network) (push) Successful in 18m43s
Foundation / checks (postgres) (push) Successful in 44m0s
Foundation / checks (tsan) (push) Successful in 10m8s
Foundation / checks (client) (push) Successful in 15m13s
Foundation / postgres-tools (push) Successful in 31s
Foundation / server-image (push) Successful in 3m18s
Foundation / image (push) Successful in 3m23s
2026-10-15 13:02:43 -04:00
dingoandClaude Opus 5.5 40426777a0 ADR-0131: grant broker reachable only through HTTPS 443
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m47s
Foundation / image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
The broker NetworkPolicy no longer admits the node subnet. Port 8080 is the
in-cluster backend for ingress-nginx pods only; players use
https://grants.aeternalisgames.com on 443.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 12:19:46 -04:00
dingoandClaude Opus 5.5 68880ba3b4 ADR-0131: Keycloak grant broker and schema v39 account identities
Foundation / checks (checks) (push) Successful in 42m13s
Foundation / checks (deploy) (push) Successful in 4m5s
Foundation / checks (ecs) (push) Successful in 2m25s
Foundation / checks (network) (push) Successful in 19m18s
Foundation / checks (postgres) (push) Successful in 44m19s
Foundation / checks (tsan) (push) Successful in 9m48s
Foundation / checks (client) (push) Failing after 12m6s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
evo-grant-broker verifies realm aeternalis access tokens offline (RS256 against
the pinned JWKS; audience aevolution-grants, client aevolution-game, verified
email) and issues 10-minute session grants:
- POST /grant routes to the region holding the account's life, or the default.
- POST /logout makes every issued grant stale and expires current control.
- GET /healthz.

Schema v39 maps (issuer, subject) to stable accounts with strictly increasing
serials. The binary ships in the server image. The DEV manifests are in
deploy/kubernetes/grant-broker-dev and are not yet enabled in region/dev; that
waits for the image promotion and the out-of-band Secrets and Ingress.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 10:20:27 -04:00
dingo 817a830a8a ADR 0127
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (tsan) (push) Successful in 10m11s
Foundation / checks (client) (push) Failing after 14m26s
Foundation / checks (network) (push) Successful in 18m54s
Foundation / checks (checks) (push) Successful in 42m9s
Foundation / checks (postgres) (push) Successful in 43m51s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
2026-10-15 09:32:51 -04:00
dingo 0a0f6c3bb1 Update Listener
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m47s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 4s
2026-10-15 07:42:45 -04:00
dingo 8148ef0a53 Record successful client upgrade push
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / image (push) Successful in 4s
Foundation / server-image (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 4s
2026-10-14 19:56:44 -04:00
dingo 1519287d5b Record verified v10 client package and publishing limit
Foundation / checks (deploy) (push) Successful in 5s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (client) (push) Canceled after 27s
Foundation / checks (checks) (push) Canceled after 29s
Foundation / checks (tsan) (push) Canceled after 22s
Foundation / checks (network) (push) Canceled after 28s
Foundation / checks (ecs) (push) Canceled after 28s
Foundation / checks (postgres) (push) Canceled after 29s
2026-10-14 19:56:18 -04:00
dingo 68958a9e54 Upgrade cellular client to v10 with readable play and assisted steering 2026-10-14 19:53:28 -04:00
dingoandClaude Opus 5.5 75b8bbb333 Promote the server with offer costs and engulf reasons to DEV
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 3s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 3s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m44s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Server 4a8b0a9d from CI run 380 (7c16a13). Build 58aab8aa, which committed region 4
history, stays retained. Also fixes a literal newline in the v10 schema doc.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 16:35:25 -04:00
dingoandClaude Opus 5.5 7c16a13dd9 Show what a mutation costs and why an engulf failed
Foundation / checks (ecs) (push) Successful in 2m24s
Foundation / checks (deploy) (push) Successful in 4m7s
Foundation / checks (tsan) (push) Successful in 9m49s
Foundation / checks (client) (push) Successful in 17m12s
Foundation / checks (network) (push) Successful in 19m34s
Foundation / checks (checks) (push) Successful in 43m5s
Foundation / checks (postgres) (push) Successful in 44m57s
Foundation / server-image (push) Successful in 31s
Foundation / postgres-tools (push) Successful in 1m13s
Foundation / image (push) Successful in 3m24s
After the first M11.9 playtest (ADR-0129 amendment): each offered candidate now
carries its funded cost to the cell, construction energy and matter per channel,
so the client can grey out what the reserve cannot pay; a candidate is affordable
by that cost exactly when the owner would fund it. A failed engulf now reports no
contact, prey too large, or membrane too thick. The v10 candidate record grows to
64 bytes, so v10 clients must be rebuilt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 15:39:35 -04:00
dingoandClaude Opus 5.5 dba73a97f5 Promote the server image with the cellular grant ceiling to DEV
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 3s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m44s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
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>
2026-10-14 13:09:21 -04:00
dingoandClaude Opus 5.5 1675bb688d Let cellular sessions use the DEV grant ceiling
Foundation / checks (ecs) (push) Successful in 2m18s
Foundation / checks (deploy) (push) Successful in 3m50s
Foundation / checks (tsan) (push) Successful in 9m44s
Foundation / checks (client) (push) Successful in 16m45s
Foundation / checks (network) (push) Successful in 19m6s
Foundation / checks (checks) (push) Successful in 42m3s
Foundation / checks (postgres) (push) Successful in 44m10s
Foundation / postgres-tools (push) Successful in 1m8s
Foundation / image (push) Successful in 3m20s
Foundation / server-image (push) Successful in 3m25s
The cellular profile refused --m10-max-grant-lifetime and the Deployment never
passed it, so playtest grants were capped at the 300 s default. The cellular
bridge now applies the DEV-only ceiling like lineage, and the Deployment passes
the overlay's ceiling (4 h in DEV) to both profiles. Recorded in ADR-0123.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 12:14:45 -04:00
dingoandClaude Opus 5.5 e803a1e182 Serve DEV region 4 with the cellular-v4 opening for the M11.9 playtests
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m42s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 5s
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>
2026-10-14 09:45:41 -04:00
dingoandClaude Opus 5.5 215a9eaa01 Refresh the dev session window for the M11.8 and M11.9a push
Foundation / checks (checks) (push) Successful in 42m10s
Foundation / checks (client) (push) Successful in 17m6s
Foundation / checks (deploy) (push) Successful in 3m51s
Foundation / checks (ecs) (push) Successful in 2m21s
Foundation / checks (network) (push) Successful in 19m18s
Foundation / checks (tsan) (push) Successful in 9m46s
Foundation / checks (postgres) (push) Successful in 34m1s
Foundation / postgres-tools (push) Successful in 26s
Foundation / image (push) Successful in 3m21s
Foundation / server-image (push) Successful in 3m26s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 08:10:13 -04:00
dingoandClaude Opus 5.5 d298d31115 Predeclare the M11.9 playtests and add account-free play telemetry
M11.9a (ADR-0130): the repeated-life playtest plan fixes its questions, sample
and recording before any session. summarize_cellular_play derives aggregates
(population, death causes, lifespans, buds, mutations, variety) from a committed
cellular state, and evo-world-clone summary prints them for a region head,
read-only and without account data. The roadmap records M11 status.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 08:09:42 -04:00
dingoandClaude Opus 5.5 69e3866fd9 Tell the owner what its engulf and bud did, and why its cell died
M11.8 server half (ADR-0129): v10 diagnostics report the tick's engulf and bud
results in two reserved bytes, and v10 type 27 tells the owner its life ended with
the cause (starved or engulfed). The bridge fills both from the owner's tick
feedback and corpses; v9 views are unchanged. Client presentation stays with the
maintainer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 07:57:37 -04:00
dingoandClaude Opus 5.5 e74bdf286b Freeze offline cells, linger, suspend and resume them
Foundation / checks (ecs) (push) Successful in 2m15s
Foundation / checks (deploy) (push) Successful in 3m53s
Foundation / checks (tsan) (push) Successful in 9m46s
Foundation / checks (client) (push) Failing after 13m47s
Foundation / checks (network) (push) Successful in 19m5s
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 19m34s
Foundation / checks (postgres) (push) Canceled after 19m28s
M11.7 (ADR-0128): a frozen step intent, set by the server for every owned life
whose account holds no session, leaves the cell unchanged but engulfable. Owner
format 6 / rules 5 track presence: lingering for 200 ticks, then suspended out of
the world without aging; an unfrozen intent resumes it in place or at the nearest
clear spot within three extents. Bundle v6, schema v38 and the cellular-v4
opening carry it. The server refuses an offline account's carried actions, ticks
while anyone lingers, and skips suspended cells in replication and perception.

Also fixes the TSan failure of CI run 374: the rules-4 owner test read the bud
through a reference into a replaced state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 07:50:45 -04:00
dingoandClaude Opus 5.5 e71147f7a6 Refresh the dev session window for the M11.5d and M11.6a push
Foundation / checks (ecs) (push) Successful in 2m24s
Foundation / checks (deploy) (push) Successful in 4m0s
Foundation / checks (tsan) (push) Failing after 9m34s
Foundation / checks (client) (push) Successful in 16m59s
Foundation / checks (network) (push) Successful in 19m20s
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 22m59s
Foundation / checks (postgres) (push) Canceled after 22m58s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 07:27:50 -04:00
dingoandClaude Opus 5.5 4130092d7a End dead lives durably so a player can start again
M11.6a (ADR-0127, schema v37): a published life is marked ended once, by a
commit of its region, through the lease-fenced end_cellular_lives. One active
life per account replaces one life per account, so after a death the account
reserves and publishes a new primitive founder while the corpse, archive and
descendants stay. The host records endings after the death's publication and
again for every founder corpse on recovery. The cellular server now refuses only
an unusable carried action, not the whole tick.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 07:26:33 -04:00
dingoandClaude Opus 5.5 212ca14e83 Drive wildlife with a deterministic controller recorded in the trace
M11.5d (ADR-0125): wildlife_intents gives each unowned cell a bud intent when it
can fund one (at most once a second), else steers it to the nearest perceived
food patch and feeds, else wanders. The cellular server puts these intentions
into each tick's baseline, so replay and publication treat them like player
input. fund_bud refuses a reserve short of the bare investment before scanning
growth levels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 06:45:48 -04:00
dingoandClaude Opus 5.5 f22a540135 Carry bud actions and the v5 bundle through protocol and persistence
Foundation / checks (ecs) (push) Successful in 2m30s
Foundation / checks (deploy) (push) Successful in 4m0s
Foundation / checks (tsan) (push) Successful in 10m37s
Foundation / checks (client) (push) Failing after 13m56s
Foundation / checks (network) (push) Successful in 19m9s
Foundation / checks (checks) (push) Successful in 42m54s
Foundation / checks (postgres) (push) Successful in 44m9s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
M11.5c (ADR-0125): v10 cellular actions, the canonical input and the trace carry
target kind 3 (bud), matched to durable actions; below rules 4 the owner
ignores it. The v5 version bundle is admitted in C++ and by schema v36, which
also admits kind 3 in SQL action inputs; the provisioner offers cellular-v3.
A PostgreSQL test publishes a bud from a fed founder and recovers it after a
host restart. The publication tests now use commit ids no other suite produces.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 06:42:41 -04:00
dingoandClaude Opus 5.5 5b255ad940 Let a PostgreSQL parameter carry a whole cellular trace
The adapter bounded each parameter to 4 KiB of text (ADR-0059), and a cellular
publication sends its replay trace as one hex bytea parameter, so a 64-tick
batch or a one-tick batch of about 85 lives was refused client-side as
"invalid". CI run 372 hit this in the M11.4c-1 publication test. ADR-0126 raises
the bound to 4 MiB, enough for the largest trace the codec admits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 06:42:27 -04:00
dingoandClaude Opus 5.5 66632f53b3 Bud unowned wildlife from the cellular owner under rules 4
Owner format 5 / rules 4 (ADR-0125) adds the bud intent: after the tick's
mutations a parent pays fund_bud's investment and provision, and the bud is
placed touching it with the next region-namespace identity, the parent's
current genome and its parent life. Buds are wildlife with no account and
never earn mutation offers; restore enforces the identity namespace and
sequence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 23:20:35 -04:00
dingoandClaude Opus 5.5 972c19843e Propose a funded bud from a grown parent's reserve
ADR-0125 and the M11.5 plan define budding and wildlife descendants. The first
piece is biology only: fund_bud pays the ADR-0032 investment and a 30 s
provision from the parent's reserve, builds the bud at the largest growth the
investment matter allows, and sends construction energy to heat, refusing with
nothing spent when any channel is short.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 23:12:50 -04:00
dingoandClaude Opus 5.5 f77956e579 Send the owner its outstanding mutation offer over v10
Session protocol v10 adds type 26: the life's earned offer with its unranked
candidates in operator order and each successor's capability value,
maintenance and total mass. The cellular bridge sends it when the offer or the
owner's session changes and clears a consumed offer; the client keeps the
latest one for the maintainer's choice UI (ADR-0121, 11.4d server half).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 23:07:50 -04:00
dingoandClaude Opus 5.5 187b1a7b98 Refresh the dev session window for the 11.4c push
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (deploy) (push) Successful in 3m59s
Foundation / checks (tsan) (push) Successful in 9m35s
Foundation / checks (client) (push) Successful in 17m6s
Foundation / checks (network) (push) Successful in 19m23s
Foundation / checks (postgres) (push) Failing after 25m1s
Foundation / checks (checks) (push) Successful in 41m11s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 22:57:03 -04:00
dingoandClaude Opus 5.5 f59c8498b1 Admit v10 mutation choices through the cellular host and sessions
The region host checks a choice against the committed offer, reserves the
successor for the next tick, and publishes it with that tick's batch; the
owner's v10 session gets the receipt and final outcome. Schema v35 now
refuses a checkpoint that skips a reserved choice, and the host reloads
pending reservations after uncertainty, refusal or recovery (ADR-0121).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 19:45:23 -04:00
dingoandClaude Opus 5.5 1bbac48543 Publish mutation choices atomically with their checkpoint
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>
2026-10-13 19:23:39 -04:00
dingoandClaude Opus 5.5 bf5c626f19 Pin the cellular v4 bundle and admit it in schema v34
Foundation / checks (checks) (push) Successful in 41m8s
Foundation / checks (deploy) (push) Successful in 4m26s
Foundation / checks (ecs) (push) Successful in 2m29s
Foundation / checks (network) (push) Successful in 19m43s
Foundation / checks (postgres) (push) Successful in 44m7s
Foundation / checks (tsan) (push) Successful in 10m5s
Foundation / checks (client) (push) Successful in 13m57s
Foundation / postgres-tools (push) Successful in 1m24s
Foundation / image (push) Successful in 3m20s
Foundation / server-image (push) Successful in 3m23s
ADR-0124: checkpoints pin cellular bundle v4 (rules 3, owner envelope 4,
revision archive) with the revision history profile and format-3 traces.
A format-4/rules-3 opening provisions on v4, and evo-world-clone accepts
--opening cellular-v2 for it. Migration 34 widens canonical action input
validation to target kind 2 (engulf, no coordinates), admits v4 manifests
through the existing v3 parser chain, and lets birth binding read
format-3 traces for v3 and v4. The migration runner and its checks extend
to version 34, with SQL and provisioning tests for v4.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 19:11:43 -04:00
dingoandClaude Opus 5.5 e17ade8cb7 Carry the engulf intent on v10 sessions and the batch trace
Foundation / checks (ecs) (push) Successful in 2m28s
Foundation / checks (deploy) (push) Successful in 4m6s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 6m47s
Foundation / checks (checks) (push) Canceled after 6m58s
Foundation / checks (client) (push) Canceled after 6m59s
Foundation / checks (tsan) (push) Canceled after 4m28s
Foundation / checks (network) (push) Canceled after 6m58s
ADR-0124: byte 12 of the canonical cellular input, the CellularAction
wire message and the batch trace record becomes a target kind (0 none,
1 patch, 2 engulf with zero coordinates). Kind 2 exists only on v10,
which no server admitted before; cellular servers now admit v10 with v9
behaviour plus engulf, and still refuse a v10 mutation choice until
11.4c. Admission, the session-batch adapter, trace codec, matcher and
action-block validator carry the kind.

The client session library accepts v10 and an engulf flag, and its send
no longer reports a message its version cannot encode as sent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 19:04:46 -04:00
dingoandClaude Opus 5.5 02adc35fa2 Run the cellular owner on rules 3 with corpse causes
Foundation / checks (ecs) (push) Successful in 2m26s
Foundation / checks (deploy) (push) Successful in 4m21s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (network) (push) Canceled after 10m41s
Foundation / checks (postgres) (push) Canceled after 10m38s
Foundation / checks (tsan) (push) Canceled after 8m19s
Foundation / checks (client) (push) Canceled after 10m48s
Foundation / checks (checks) (push) Canceled after 10m53s
ADR-0124's engulf profile starts a region on owner format 4 and rules 3,
with the revision-format archive. Ticks pass genome membrane thickness and
source to the region step, record each corpse's cause and predator, insert
detritus patches and validate rules-3 corpses as empty. Format-4 snapshots
carry the cause and predator and refuse an unknown cause, a predator on a
starvation corpse or a non-empty corpse. Mutation selection accepts both
genome-revision formats (3 and 4).

Persistence (version bundle, schema 34), protocol v11 and provisioning
follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:54:03 -04:00
dingoandClaude Opus 5.5 0fb67c3257 Resolve cellular engulfment and detritus in the region step
Foundation / checks (ecs) (push) Successful in 2m17s
Foundation / checks (deploy) (push) Successful in 3m57s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 6m13s
Foundation / checks (checks) (push) Canceled after 6m19s
Foundation / checks (tsan) (push) Canceled after 3m58s
Foundation / checks (client) (push) Canceled after 6m17s
Foundation / checks (network) (push) Canceled after 6m18s
ADR-0124 implements ADR-0098's predation and corpse rules for the
cellular trial. Under rules 3 the pure region step adds an engulf phase
after every life's step: in ascending life id, a predator takes the
lowest-id contacted survivor whose total mass, times 1.5 per micrometre
of its membrane, is at most the predator's. The prey's whole inventory
moves once; the predator keeps what its remaining per-tick intake allows
and the rest, like every starvation corpse, becomes detritus in the
patch at the dead cell's 1 mm cell. Corpse candidates report their cause.
Rules 2 is unchanged and ignores engulf intents.

Owner, protocol v11, persistence and recovery wiring follow in the next
11.3f steps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:47:48 -04:00
dingoandClaude Opus 5.5 4751b23857 Record the first M11.3 cellular probe run
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m44s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
The 2026-10-13 probe in DEV region 100/3 showed steering and feeding
working end to end after the session fixes, and not yet enough game to
judge fun. Record its findings and inputs for 11.4-11.8, and mark the
remaining 11.3 work (engulfment and corpse absorption) in the roadmap.
Also refresh the dev session window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:40:28 -04:00
dingoandClaude Opus 5.5 5c92cf137a deploy(dev): promote the cellular session-fixes server image
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m36s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 5s
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>
2026-10-13 17:59:04 -04:00
dingoandClaude Opus 5.5 e9b010ed01 Send a life identity on the wire only with a born outcome
Foundation / checks (checks) (push) Successful in 40m57s
Foundation / checks (deploy) (push) Successful in 3m59s
Foundation / checks (ecs) (push) Successful in 2m19s
Foundation / checks (network) (push) Successful in 19m0s
Foundation / checks (postgres) (push) Successful in 43m16s
Foundation / checks (tsan) (push) Successful in 9m41s
Foundation / checks (client) (push) Successful in 13m43s
Foundation / postgres-tools (push) Successful in 18s
Foundation / server-image (push) Successful in 3m0s
Foundation / image (push) Successful in 3m15s
A fresh client launch sends a new birth request. For an account that
already has a cell, the cellular host reports existing_life with the
reserved identity, and RegionSessions forwarded it although the codec
accepts an identity only with born. The client closed with protocol and
retried with the next grant until the account was rate-limited, so no
account with a cell could log in from a new launch. Clear the identity
and commit on every other result at the session boundary, and test that
an existing_life refusal arrives valid while the session stays open.

The client now names the cause of a protocol close on stderr, which is
how this was found. Record it in ADR-0123. Also refresh the dev session
window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:51:09 -04:00
dingoandClaude Opus 5.5 f3aecaf36a Tick cellular births only for accounts holding a session
Foundation / checks (ecs) (push) Successful in 2m19s
Foundation / checks (deploy) (push) Successful in 3m56s
Foundation / checks (tsan) (push) Successful in 9m34s
Foundation / checks (client) (push) Successful in 16m45s
Foundation / checks (network) (push) Successful in 18m57s
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 28m43s
Foundation / checks (postgres) (push) Canceled after 28m44s
A second account's queued birth outlived its session. Every following
batch failed check_life_control with EVL02, which the host reads as a
lost region lease, so region 100/3 fenced, reacquired and failed again
every 20 s, refusing logins. Include, and tick for, only births whose
account holds a session; the rest stay queued until the account returns.
Record the incident in ADR-0123. Also refresh the dev session window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:22:31 -04:00
dingoandClaude Opus 5.5 b735860bff Admit a cellular action every tick and feed DEV region 3
Foundation / checks (checks) (push) Successful in 40m12s
Foundation / checks (deploy) (push) Successful in 3m55s
Foundation / checks (ecs) (push) Successful in 2m13s
Foundation / checks (network) (push) Successful in 18m47s
Foundation / checks (postgres) (push) Successful in 42m20s
Foundation / checks (tsan) (push) Successful in 9m38s
Foundation / checks (client) (push) Successful in 13m51s
Foundation / postgres-tools (push) Successful in 28s
Foundation / server-image (push) Canceled after 58s
Foundation / image (push) Canceled after 59s
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>
2026-10-13 15:24:18 -04:00
dingoandClaude Opus 5.5 532f45b99a Frame and follow the own cell in the cellular client view
Foundation / checks (ecs) (push) Successful in 2m22s
Foundation / checks (deploy) (push) Successful in 4m1s
Foundation / checks (tsan) (push) Successful in 9m43s
Foundation / checks (client) (push) Successful in 16m51s
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 18m3s
Foundation / checks (network) (push) Canceled after 18m2s
Foundation / checks (postgres) (push) Canceled after 18m9s
The camera started at 0.05 px/mm, the metre-scale lineage default, so the
whole 10 mm cellular arena drew inside half a pixel and the player could
not find their cell. In the cellular trial, frame about 12 mm around the
own cell (organism id == life identity) once, then keep it centred while
keeping the player's zoom. Draw food patches as their true 1 mm footprint
under the organisms, so contact with a patch is visible.
Also refresh the dev session window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 15:06:19 -04:00
dingoandClaude Opus 5.5 2a93d875a7 deploy(dev): promote the genesis-resolution server image
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m42s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
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>
2026-10-13 14:21:28 -04:00
dingoandClaude Opus 5.5 5e45be3b6b Resolve a cellular genesis under the build that wrote it
Foundation / checks (checks) (push) Successful in 40m17s
Foundation / checks (deploy) (push) Successful in 3m54s
Foundation / checks (ecs) (push) Successful in 2m24s
Foundation / checks (network) (push) Successful in 18m40s
Foundation / checks (postgres) (push) Successful in 42m11s
Foundation / checks (tsan) (push) Successful in 9m39s
Foundation / checks (client) (push) Successful in 13m33s
Foundation / postgres-tools (push) Successful in 1m13s
Foundation / image (push) Successful in 3m10s
Foundation / server-image (push) Successful in 3m16s
Promoting the dev server image changed --build, and the cellular
provision rerun re-encoded the genesis manifest with the new build, so it
refused region 100/2 as a different genesis. The check could also never
pass once the head moved past genesis. Match an unadvanced cellular
genesis under its recorded build, and accept profile and frame past
genesis as the other openings do. A different commit or opening is still
refused. Add a PostgreSQL process test and record the finding in ADR-0123.
Also refresh the dev session window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 13:14:15 -04:00
dingoandClaude Opus 5.5 7271fa684b deploy(dev): promote the allocator-provisioning server image
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m46s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
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>
2026-10-13 13:02:27 -04:00
dingoandClaude Opus 5.5 56e7525bfb Check the allocator row through a named optional
Foundation / checks (checks) (push) Successful in 40m39s
Foundation / checks (deploy) (push) Successful in 3m54s
Foundation / checks (ecs) (push) Successful in 2m20s
Foundation / checks (network) (push) Successful in 18m45s
Foundation / checks (postgres) (push) Successful in 42m50s
Foundation / checks (tsan) (push) Successful in 9m28s
Foundation / checks (client) (push) Successful in 13m50s
Foundation / server-image (push) Successful in 40s
Foundation / postgres-tools (push) Successful in 1m25s
Foundation / image (push) Successful in 3m20s
clang-tidy's bugprone-unchecked-optional-access could not follow the
optional cell through the indexed row in the provisioner and its test,
failing the PostgreSQL analysis build (run 357). Read the cell through a
checked reference instead. Also refresh the dev session window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 11:54:33 -04:00
dingoandClaude Opus 5.5 a3939bda4e 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
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>
2026-10-13 11:30:16 -04:00
dingoandClaude Opus 5.5 6615e4325c deploy(dev): migrate the dev database to schema v33
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m57s
Foundation / postgres-tools (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
The cellular-v1 provision hook failed with PublicationError::rejected:
the dev store Jobs still pinned the schema-v11 postgres-tools image,
so PostgreSQL refused the profile-4 genesis manifest. Pin the
postgres-tools image from Gitea run 350 (source ae3b2b4, migrations
through 0033), the same run that built the promoted dev server image.
Also refresh the dev session window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 11:09:55 -04:00
dingoandClaude Opus 5.5 1826c2a799 Anchor the route selftest on the dev world, not region 1
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m55s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 5s
The dev overlay now serves region 2, so the selftest's literal
REGION_ID "1" anchor no longer exists and setup aborted. Anchor the
injected listener patch on REGION_WORLD instead, and refresh the dev
session window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 10:44:33 -04:00
dingoandClaude Opus 5.5 c9cc302884 deploy(dev): refresh the session window
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Failing after 3m22s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 10:30:17 -04:00
dingoandClaude Opus 5.5 b923ce1721 deploy(dev): serve a cellular region 100/2 for the M11.3 probe
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>
2026-10-13 10:23:52 -04:00
dingoandClaude Opus 5.5 a33755c60d Cut PostgreSQL CI time: parallel builds and split qualification
Foundation / checks (ecs) (push) Successful in 5m55s
Foundation / checks (deploy) (push) Successful in 6m56s
Foundation / checks (tsan) (push) Successful in 9m35s
Foundation / checks (client) (push) Successful in 20m0s
Foundation / checks (network) (push) Successful in 22m38s
Foundation / checks (checks) (push) Successful in 44m57s
Foundation / checks (postgres) (push) Successful in 48m59s
Foundation / server-image (push) Successful in 40s
Foundation / image (push) Successful in 3m11s
Foundation / postgres-tools (push) Successful in 4m26s
Compile the PostgreSQL stages with PG_BUILD_JOBS=6 (was 2), including
PostgreSQL itself. postgres-check.sh gains --full (release),
--sanitizer (ASan: C++ suite plus backup/DR/upgrade process checks that
run the instrumented binaries) and --suite-only (clang-tidy build), so
SQL-only checks run once. Each run prints per-phase timings, and the
postgres job logs runner CPU, memory and disk headroom.

Also refresh the dev REGION_SESSION_WINDOW.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 08:38:26 -04:00
dingo 08b4e843c1 Merge branch 'main' of https://git.aeternalisgames.com/dingo/AEvolution
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 58s
Foundation / checks (deploy) (push) Successful in 3m44s
Foundation / postgres-tools (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
2026-10-13 07:12:26 -04:00
dingo 8e74a2d43d New Listener Window 2026-10-13 07:12:13 -04:00