Commit Graph
125 Commits
Author SHA1 Message Date
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
aevolution-gitops-bot f6ca6f695a deploy(dev): promote selected server image 2026-10-08 23:16:32 +00:00
dingoandClaude Opus 5.5 9f9a93d4c8 M10.9d: watermark coalescing, budgets v2, evo-load action ids
Foundation / checks (client) (push) Successful in 14s
Foundation / checks (checks) (push) Successful in 16s
Foundation / checks (deploy) (push) Successful in 15s
Foundation / checks (network) (push) Successful in 18s
Foundation / checks (postgres) (push) Successful in 1m34s
Foundation / checks (ecs) (push) Successful in 1m53s
Foundation / checks (tsan) (push) Successful in 5m44s
Foundation / server-image (push) Successful in 1m0s
Foundation / postgres-tools (push) Successful in 1m38s
Foundation / image (push) Successful in 2m34s
- IntentLimits::watermark_coalesce (evo-server: every 4, coalesce 4); ADR-0092 amendment.
- m10 load-report splits poll/replicate and commit-tick/other-tick maxima.
- Budgets v2: work p95 <= 25 ms over all ticks, commit ticks <= 50 ms (ADR-0097);
  moving the commit off the tick is a recorded follow-up.
- evo-load: time-based action ids, duplicate_actions, receipts before outcomes;
  drill ramps at 500 ms and judges by v2.
- Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 18:00:41 -04:00
aevolution-gitops-bot 1b266b12be dev: retain prior head build for recovery
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 4m48s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 5s
2026-10-08 16:51:22 -04:00
aevolution-gitops-bot 3a5eb34b47 deploy(dev): promote selected server image 2026-10-08 20:17:34 +00:00
dingoandClaude Opus 5.5 46b6358606 Share replication encoding per interest; fix dev retained builds
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (client) (push) Successful in 12m36s
Foundation / checks (network) (push) Successful in 13m35s
Foundation / checks (tsan) (push) Successful in 7m48s
Foundation / checks (checks) (push) Successful in 32m51s
Foundation / checks (postgres) (push) Successful in 46m20s
Foundation / postgres-tools (push) Successful in 1m35s
Foundation / image (push) Successful in 2m32s
Foundation / server-image (push) Successful in 4m14s
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>
2026-10-08 15:03:45 -04:00
dingo 9409d65947 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 (network) (push) Successful in 4s
Foundation / checks (deploy) (push) Failing after 13s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
2026-10-08 14:19:06 -04:00
aevolution-gitops-bot f88bee20b3 dev: retain region head build for recovery
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 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (deploy) (push) Failing after 12s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
2026-10-08 13:38:41 -04:00
aevolution-gitops-bot 61df6a19cf dev: retain promoted region build for recovery
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 3s
Foundation / checks (deploy) (push) Failing after 12s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
2026-10-08 12:35:30 -04:00
aevolution-gitops-bot ce5c25a426 deploy(dev): promote selected server image 2026-10-08 16:11:14 +00:00
dingoandClaude Opus 5.5 d173f076ea Fix load governor startup refusal and drill issues from the first dev run
Foundation / checks (deploy) (push) Successful in 3m24s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (client) (push) Successful in 12m24s
Foundation / checks (network) (push) Successful in 13m35s
Foundation / checks (tsan) (push) Successful in 7m58s
Foundation / checks (checks) (push) Successful in 32m32s
Foundation / checks (postgres) (push) Successful in 45m25s
Foundation / postgres-tools (push) Successful in 17s
Foundation / image (push) Successful in 2m32s
Foundation / server-image (push) Successful in 4m15s
ADR-0097. The first evolution-dev load drill (image 6c96629e) did not
measure capacity: the governor refused six seconds after the restart with
no session (p95 over a window of only startup ticks), and the bots spent
their grants retrying every 2 s. Reference numbers with one session: tick
work p95 4.0 ms with 33 ms spikes, session layer p95 0.68 ms.

- The governor acts on work only over a full 40-tick window; tick debt
  still counts at once.
- evo-load backs off 10 s after a load refusal and, in bundle mode,
  reuses the grant the region refused before using it.
- The drill waits for a calm load-report before the bots start, takes the
  drill pod's whole log before restoring (the live follow died), and
  confirms the restore against a pod other than the drill pod.

Refreshes the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 11:01:02 -04:00
dingo 9b868b3ae2 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 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m24s
Foundation / postgres-tools (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
2026-10-08 09:58:38 -04:00
aevolution-gitops-bot df0d3322c8 deploy(dev): promote selected server image 2026-10-08 13:48:15 +00:00
dingoandClaude Opus 5.5 ada77fd761 Add M10.9d load drill harness and serialize Mbed TLS use
Foundation / checks (deploy) (push) Successful in 3m24s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (client) (push) Successful in 12m18s
Foundation / checks (network) (push) Successful in 13m30s
Foundation / checks (tsan) (push) Successful in 8m0s
Foundation / checks (checks) (push) Successful in 32m39s
Foundation / checks (postgres) (push) Successful in 45m47s
Foundation / postgres-tools (push) Successful in 17s
Foundation / image (push) Successful in 2m30s
Foundation / server-image (push) Successful in 4m8s
ADR-0097. tools/ops/load-drill.sh (runbook docs/networking/M10_LOAD_DRILL.md)
runs the evolution-dev reference qualification: synthetic inputs on for
the run (the ADR-0073 drill-time override, restored on exit), bundle-mode
evo-load bots through the public route, and each step's hold matched with
the server's reports. evo-server logs "m10 load-report" every 10 s, since
the agent cannot reach the ops port. evo-load gains --grants FILE
--grants-per-bot C, exhausted=, hold_utc= and close_reasons=;
evo-session-probe grants gains --accounts N.

Finding: Mbed TLS/PSA are built without MBEDTLS_THREADING_C, and bots on
different threads verifying their first connections at once were refused
as untrusted (two per smoke run). One process-wide recursive crypto lock
now guards every network-library entry point that touches them; the
smoke went from 2/2 failing to 3/3 clean. quic-transport adds a
concurrent-connect test. Refreshes the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 08:38:13 -04:00
dingoandClaude Opus 5.5 4a72897679 Fix dev crashloop: session window within the 4-hour maximum
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 4s
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 5s
b2f224d set REGION_SESSION_WINDOW to expire about 5.2 hours after the pod
started; evo-server refuses windows longer than 4 hours
(SessionWindow::max_duration_seconds) and exited with
"error m10-window-too-long" in a loop. The window now expires 3 h 50 min
after it was written.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 07:28:39 -04:00
dingo b2f224d0a2 update 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 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m18s
Foundation / server-image (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 5s
2026-10-08 07:14:36 -04:00
aevolution-gitops-bot c3b40f4d14 deploy(dev): promote selected server image 2026-10-08 11:13:21 +00:00
dingoandClaude Opus 5.5 39edfb0773 Add M10.9c-2 lease loss under load process test
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / checks (tsan) (push) Successful in 8m14s
Foundation / checks (checks) (push) Successful in 32m35s
Foundation / checks (postgres) (push) Successful in 46m6s
Foundation / server-image (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 19s
Foundation / image (push) Successful in 2m37s
ADR-0097. 24 evo-load bots against a real evo-server on a fixed loopback
port: a SIGKILL (the successor waits out the lease) and then a SIGTERM
drain, each followed by a successor under a new epoch. Every bot logs in
again within 15 s of the successor being ready (development reference:
5.0 s after SIGKILL, 2.4 s after drain), with 48 drops and no failed
logins counted over the hold.

Scope narrowed: no standalone raw-UDP sender; abuse stays in-process or
on loopback, and the per-connection datagram cap's eviction cost is
analysed in the ADR. Refreshes the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 06:21:15 -04:00
dingo fe43706395 refresh
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 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m21s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
2026-10-07 21:54:13 -04:00
dingo 326801a297 refresh listener
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 (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 3m23s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
2026-10-07 20:58:10 -04:00
aevolution-gitops-bot 11fd2b0970 deploy(dev): promote selected server image 2026-10-07 21:17:46 +00:00
dingo a3416e989b Reset listener, and setting fetch to 2
Foundation / checks (checks) (push) Successful in 34s
Foundation / checks (ecs) (push) Successful in 14s
Foundation / checks (deploy) (push) Successful in 3m19s
Foundation / checks (postgres) (push) Successful in 1m16s
Foundation / checks (tsan) (push) Successful in 5m47s
Foundation / checks (network) (push) Successful in 13m11s
Foundation / checks (client) (push) Successful in 15m41s
Foundation / image (push) Successful in 11s
Foundation / postgres-tools (push) Successful in 19s
Foundation / server-image (push) Successful in 4m9s
2026-10-07 16:56:35 -04:00