Commit Graph
170 Commits
Author SHA1 Message Date
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
aevolution-gitops-bot 1094f65222 deploy(dev): promote selected server image 2026-10-13 11:11:04 +00:00
dingoandClaude Opus 5.5 ae3b2b4800 Admit v22+ schemas only on an exact migration history
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 53m9s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 14s
Foundation / image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 2m8s
Foundation / server-image (push) Successful in 5m13s
apply.sql matched v1..v21 against the full checked-in history but v22..v33
only against the final entry, so a changed checksum for any earlier
migration was admitted once a database reached v22. postgres-check's
checksum-drift rehearsal caught this (zeroed v14 sha256 migrated cleanly).
Build the exact v21 history once and extend it per version.

Verified on PostgreSQL 18.6: fresh migrate and re-run, v30 -> v33 upgrade,
and refusal of a fake v34 and of zeroed checksums for v2, v14, v21, v22,
v30 and v33, including a drifted v30 database. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 21:15:06 -04:00
dingoandClaude Opus 5.5 dfed25bda3 Audit an unfenced cellular helper instead of a fenced lookup
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m30s
Foundation / checks (postgres) (push) Failing after 40m45s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
postgres-check expected granting find_region_action_record to the
runtime role to fail the role audit, but migration 19 grants it and the
audit lists it as fenced, so the grant was a no-op and the audit passed.
Exercise the internal check_cellular_action_block validator instead,
mirroring the existing check_action_block case. Refresh the dev session
window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 18:14:49 -04:00
dingoandClaude Opus 5.5 bf5dcc7a6e Check failed-migration schema version against its prior value
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m28s
Foundation / checks (postgres) (push) Failing after 40m43s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
The upgrade rehearsal asserted the schema stayed at version 23 after a
deliberately failing migration, but migrations now reach 33, so it
reported "schema version moved" although nothing changed. Record the
version before the failing migration and compare against that. Refresh
the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 16:28:57 -04:00
dingoandClaude Opus 5.5 fcccdf552f Compare migration deferral checks as text
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (deploy) (push) Successful in 3m29s
Foundation / checks (tsan) (push) Successful in 8m38s
Foundation / checks (checks) (push) Successful in 37m37s
Foundation / checks (postgres) (push) Failing after 41m14s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
The primitive_life_bindings foreign key and evidence trigger checks
selected a bare boolean, which libpq returns as "t", but compared it
with "true" (region migration test line 216). Cast to text like every
other check in the file. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 15:41:40 -04:00
dingoandClaude Opus 5.5 b8feaad6f3 Expect migrations through v33 in migration test
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 2m2s
Foundation / checks (deploy) (push) Successful in 3m36s
Foundation / checks (tsan) (push) Successful in 8m40s
Foundation / checks (checks) (push) Successful in 36m53s
Foundation / checks (postgres) (push) Failing after 40m52s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Migrations 31-33 were added without updating the history the migration
test expects after running migrate-postgres.sh (region migration test
line 214). postgres-check.sh already expects 1..33. Refresh the dev
session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 14:47:40 -04:00
dingoandClaude Opus 5.5 17dc50483c Corrupt encoded bytes for unsupported cellular bundle test
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m3s
Foundation / checks (deploy) (push) Successful in 3m29s
Foundation / checks (tsan) (push) Successful in 9m5s
Foundation / checks (checks) (push) Successful in 38m8s
Foundation / checks (postgres) (push) Failing after 39m55s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
encode_manifest refuses unsupported cellular version bundles, so the
migration test could never produce the manifest it sends to the SQL
parser (region migration test line 587). Encode the valid v1 manifest
and bump the archive version byte at offset 188 instead. Refresh the
dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 13:51:54 -04:00
dingoandClaude Opus 5.5 b073ac7672 Give primitive provisioning fixture its own region
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (deploy) (push) Successful in 3m36s
Foundation / checks (tsan) (push) Successful in 8m50s
Foundation / checks (checks) (push) Successful in 37m4s
Foundation / checks (postgres) (push) Failing after 39m46s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
The primitive provisioning test provisioned world 7 region 87, which the
synthetic load suite provisions again later in the same disposable
cluster, failing with region_leases_pkey SQLSTATE 23505. Move it to the
unused region 89. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 13:02:44 -04:00
dingoandClaude Opus 5.5 f77e4ea67f Use a 32-byte build identity in primitive provisioning test
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m4s
Foundation / checks (deploy) (push) Successful in 3m38s
Foundation / checks (tsan) (push) Successful in 8m41s
Foundation / checks (checks) (push) Successful in 37m4s
Foundation / checks (postgres) (push) Failing after 38m15s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
The primitive provisioning fixture passed a 66-hex-digit --build, which
evo-world-clone rejects as a usage error, so the first owner provision
never ran (region store test line 322). Match the 32-byte identity the
fixture already retains. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 12:11:25 -04:00
aevolution-gitops-bot 066b85333b deploy(dev): promote selected server image 2026-10-10 16:26:57 +00:00
dingo 3d54a37ce5 Update deploy/kubernetes/region/dev-session-route/listener.yaml
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 5s
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / image (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
2026-10-10 14:53:35 +00:00
aevolution-gitops-bot 663c322f56 deploy(dev): promote selected server image 2026-10-10 14:45:43 +00:00
dingoandClaude Opus 5.5 93e1ab08ae Keep the phenotype wire-stable: rate period on the budget, not the phenotype
Foundation / checks (deploy) (push) Successful in 3m28s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m43s
Foundation / checks (network) (push) Successful in 13m32s
Foundation / checks (tsan) (push) Successful in 7m48s
Foundation / checks (checks) (push) Successful in 32m55s
Foundation / checks (postgres) (push) Successful in 46m26s
Foundation / postgres-tools (push) Successful in 1m41s
Foundation / server-image (push) Successful in 4m13s
Foundation / image (push) Successful in 2m35s
CI run 136 failed network: Phenotype::rate_microseconds (added with development version
2) is not carried by either session protocol, so the organism view no longer re-encoded
canonically. The phenotype keeps its replicated shape; the period follows from the
development version (development_rate_microseconds) and MetabolicBudget carries it.
No protocol change; first-bud times unchanged. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 16:47:23 -04:00
dingoandClaude Opus 5.5 51cf23dbc9 M11.1: development version 2 and the primitive founder (first bud in 5-15 min)
Foundation / checks (deploy) (push) Successful in 3m28s
Foundation / checks (ecs) (push) Successful in 1m53s
Foundation / checks (client) (push) Successful in 12m36s
Foundation / checks (network) (push) Failing after 10m52s
Foundation / checks (tsan) (push) Successful in 7m50s
Foundation / checks (checks) (push) Successful in 33m6s
Foundation / checks (postgres) (push) Successful in 46m9s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Development version 2 is defined per second; phenotype/budget rates carry their period
(rate_microseconds: 50 ms for v1, 1 s for v2) and the M2 fixture adapters accept only
v1. Tunable v2 constants (maintenance 10, membrane upkeep 15, movement 50 pJ/s per
1000 fg) and the primitive founder (schema 2: 1 um membrane, 8e6 fg, 200 um/s,
574,000 fg/s ingestion, 500 per-thousand bud) give a first bud in 300/600/901 s when
feeding 100/50/33 % of the time at full-speed movement (bud_funding_seconds; never at
10 %), the maintainer's 5-15 minute target. Tests pin the range; v1 is unchanged.
11.1 complete. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 15:36:02 -04:00
dingoandClaude Opus 5.5 4319da2750 M11.1: environmental rules 3 with per-second rates (ADR-0099, segment 3)
Foundation / checks (deploy) (push) Successful in 3m27s
Foundation / checks (ecs) (push) Successful in 1m58s
Foundation / checks (client) (push) Successful in 12m20s
Foundation / checks (network) (push) Successful in 13m53s
Foundation / checks (tsan) (push) Successful in 8m9s
Foundation / checks (checks) (push) Successful in 33m4s
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 21m43s
Rules 3 is rules 2 with irradiance, growth, intake and decay per second. The community
derives its per-tick form once at creation and restore (rationals exact via the tick in
numerator and denominator, caps rounded down); steps and the snapshot layout are rules
2's; the codec reads formats 1-3. At 50 ms a x20 per-second twin steps identically
through feeding, death and decay and across a snapshot; at 25 ms caps halve. Rules 1/2
and the development-v1 opening are unchanged. Development version 1 outputs stay tied
to their 50 ms quantum and the tick-abstract M2 fixtures are not migrated (recorded).
environmental-qualification's "unknown rules" case moves from 3 to 4.
Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 14:55:45 -04:00
aevolution-gitops-bot b5ea632165 deploy(dev): promote selected server image 2026-10-09 18:21:04 +00:00
dingoandClaude Opus 5.5 17fe23e5f0 M11.1: genome schema 2 with per-second rates (ADR-0099, segment 2)
Foundation / checks (deploy) (push) Successful in 3m32s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (client) (push) Successful in 12m56s
Foundation / checks (network) (push) Successful in 13m46s
Foundation / checks (tsan) (push) Successful in 7m59s
Foundation / checks (checks) (push) Successful in 33m36s
Foundation / checks (postgres) (push) Successful in 45m30s
Foundation / postgres-tools (push) Successful in 20s
Foundation / server-image (push) Successful in 25s
Foundation / image (push) Successful in 2m36s
Movement and ingestion are stored per second in schema 2 (ranges x20). Schema 1 records
stay valid, are never rewritten, and read as exactly x20 via Genome::per_second; drafts
default to schema 1 so existing literals keep their meaning. Development version 1
converts genome rates at its own 50 ms quantum (round down), so phenotypes are
unchanged. Mutation keeps the parent's schema and step; the lineage archive header names
exactly the highest schema held (all-schema-1 archives keep their bytes); the
development-v1 opening names schema 1. No golden changed; two tests that used 2 as an
unknown schema now use the next one. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 13:16:55 -04:00
dingoandClaude Opus 5.5 a4c6181540 M11.1: time-based rate conversion (ADR-0099, segment 1)
Foundation / checks (deploy) (push) Successful in 3m27s
Foundation / checks (ecs) (push) Successful in 1m51s
Foundation / checks (client) (push) Successful in 12m31s
Foundation / checks (network) (push) Successful in 13m30s
Foundation / checks (tsan) (push) Canceled after 8m42s
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 27m37s
Foundation / checks (postgres) (push) Canceled after 15m9s
Rates are stored per second in their integer base units and converted at the tick
boundary with no carried state: costs round up, capacities down (maintainer decision),
error below one unit per tick. per_second_from_per_tick is the migration's exact inverse
(x20 at 50 ms) and refuses inexact values. New rate-contracts test. No biology uses it
yet; genome v2, development v2 and process fields follow. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 12:50:54 -04:00
dingo 961b3e3c2f Refresh Listener
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
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 3m30s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
2026-10-09 12:33:14 -04:00
dingo 11ff95be49 Refresh Listener
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 4s
Foundation / checks (deploy) (push) Failing after 13s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
2026-10-09 12:27:05 -04:00
dingoandClaude Opus 5.5 3320a8a574 client: skip used grants; scale the engineering UI with the window
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / checks (ecs) (push) Successful in 2m2s
Foundation / checks (client) (push) Successful in 12m47s
Foundation / checks (tsan) (push) Canceled after 0s
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 11m44s
Foundation / checks (checks) (push) Canceled after 17m14s
Foundation / checks (postgres) (push) Canceled after 4m27s
- A stale_grant before Welcome spends only that grant: the session tries the next one
  in the bundle and ends as exhausted when none is left (other refusals still stop).
- UI scale (ADR-0084 amendment): embedded scalable font (ProggyForever), scale from
  logical window height (720 reference, 1.0-2.5) times a Ctrl+= / Ctrl+- nudge; panel
  sizes and table columns in logical units; movable panels placed again per scale.
- --size W,H for engineering review screenshots.
- Tests: client_remote_session (stale grant, exhausted), client_ui_state (scale).
Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 12:09:57 -04:00
dingoandClaude Opus 5.5 c468c70933 M11.1: record the first cellular loop decisions (ADR-0098)
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m33s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Maintainer decisions (2026-10-09) for the first playable loop: budding (parent keeps
control, one funded wildlife bud); funded in-life mutation from seeded candidates;
exact-copy heredity, no NPC mutation in M11; logout freezes at once, lingers vulnerable,
then suspends; resume in place or nearest valid spot within a bounded radius;
absorption plus engulfment by membrane-contested size ratio; first bud fundable within a
session (tunable); friend recognition deferred. Updates OPEN_QUESTIONS 7/10/14/31/33,
REPRODUCTION_MODEL, ROADMAP, STATUS; BACKLOG gains the open M10 native-client items.
Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 10:51:23 -04:00
dingoandClaude Opus 5.5 af156ab3f0 client: default the dev server name to void.aeternalisgames.com
Foundation / checks (deploy) (push) Successful in 3m29s
Foundation / checks (ecs) (push) Successful in 1m57s
Foundation / checks (client) (push) Successful in 12m43s
Foundation / checks (network) (push) Successful in 13m28s
Foundation / checks (tsan) (push) Successful in 7m55s
Foundation / checks (checks) (push) Successful in 31m54s
Foundation / checks (postgres) (push) Successful in 46m11s
Foundation / postgres-tools (push) Successful in 19s
Foundation / image (push) Successful in 2m32s
Foundation / server-image (push) Successful in 4m3s
The connect form paired the dev endpoint with the local test PKI's name
(dev-region.evolution.test), so a default connection to the dev region failed the
certificate name check. client_ui_model checks the new default; the tester doc names it.
Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 09:36:02 -04:00
aevolution-gitops-bot 4b494ecb4d deploy(dev): promote selected server image 2026-10-09 13:26:26 +00:00
dingoandClaude Opus 5.5 1daa62cf6d M10.9: raise the evo-server session cap to 2000 and close 10.9 for now
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m32s
Foundation / checks (network) (push) Successful in 13m34s
Foundation / checks (tsan) (push) Successful in 7m42s
Foundation / checks (checks) (push) Successful in 32m43s
Foundation / checks (postgres) (push) Successful in 46m18s
Foundation / postgres-tools (push) Successful in 17s
Foundation / image (push) Successful in 2m28s
Foundation / server-image (push) Successful in 4m5s
Maintainer decision (2026-10-09): the region session cap becomes a safety bound of 2000
(plus 64 connections of headroom); the load governor is the working limit. Library bounds
go from 1024 to 4096 in SessionControl, IntentAdmission and ReplicationServer (defaults
stay 32). Drills stop for now: saturation and native-client observation move to a later
2k drill, whose prerequisites ADR-0097 lists (single-thread CPU, region login rate,
256 MiB pod limit, linear lookups). Declared: >= 32 sessions within every budget on the
reference worker. Budgets v2, STATUS, ROADMAP, VALIDATION. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 08:22:04 -04:00
dingoandClaude Opus 5.5 24a2d4baaf M10.9d: record the fifth evolution-dev reference run
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 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m32s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Image c597c0ba (batched durable lookups). Clients within budget at 20-32 sessions; server
within budgets v2 at 24, 28 and 32 (the configured session cap): work p95 <= 12.9 ms,
commit ticks <= 44.3 ms, session p99 <= 13.3 ms, no tick debt. At 20, four refusals during
the login ramp and per-session p99 0.554 ms. Saturation beyond the cap and native-client
observation remain open. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 07:41:25 -04:00
aevolution-gitops-bot 07b85b9fb3 fix: renew dev session window from trusted time
Foundation / checks (client) (push) Successful in 25s
Foundation / checks (checks) (push) Successful in 33s
Foundation / checks (ecs) (push) Successful in 15s
Foundation / checks (network) (push) Successful in 11s
Foundation / checks (postgres) (push) Successful in 1m39s
Foundation / checks (deploy) (push) Successful in 3m29s
Foundation / checks (tsan) (push) Successful in 5m37s
Foundation / image (push) Successful in 11s
Foundation / postgres-tools (push) Successful in 17s
Foundation / server-image (push) Successful in 19s
2026-10-09 06:04:41 -04:00
aevolution-gitops-bot 3393b26d4d deploy(dev): promote selected server image 2026-10-09 09:57:52 +00:00
dingoandClaude Opus 5.5 07d12a4d82 M10.9d: batch durable action lookups (one per poll, one per commit)
Foundation / checks (deploy) (push) Successful in 3m27s
Foundation / checks (ecs) (push) Successful in 1m57s
Foundation / checks (client) (push) Successful in 12m41s
Foundation / checks (network) (push) Successful in 13m33s
Foundation / checks (tsan) (push) Successful in 7m54s
Foundation / checks (checks) (push) Successful in 32m56s
Foundation / checks (postgres) (push) Successful in 46m10s
Foundation / postgres-tools (push) Successful in 18s
Foundation / image (push) Successful in 2m33s
Foundation / server-image (push) Successful in 4m24s
The fourth dev drill showed a synchronous PostgreSQL round trip per action on the
simulation thread: at admission (uniqueness) and again at commit (first-record rule).
About 12 lookups landed on each commit tick (commit ticks 58-70 ms, session p99 30-39 ms).

- ActionLedger::find_all; persistence::find_region_actions applies the schema v11
  find_region_action to many pairs in one statement (no migration).
- IntentAdmission::admit/verify: actions only the ledger can refuse wait for one verify
  per poll; receipts still go out in the same poll. committed() asks once per commit.
- Tests: deferred_actions (network_control), find_region_actions and find_all (Postgres).
- ADR-0097 fourth run, ADR-0092 amendment, VALIDATION; refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 21:35:43 -04:00
aevolution-gitops-bot 572316944a dev: retain prior promoted build for newest recovery
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 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m32s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
2026-10-08 19:43:03 -04:00