The maintainer's direction after the sign-in playtests, as a proposed design for
three rules versions:
- Rules 7: offers are weighted by what each life does (moving, eating, budding,
engulfing) and by its accept and decline history; declining lowers a trait's and
related traits' odds but never rules them out; single candidates can be declined.
- Rules 8: buds roll attached (the player's colony) or detached (wildlife anchored
near where the owner logged out), with colonization, budding efficiency and other
new capabilities.
- Rules 9: the player steers the colony as one body with separate reserves, and
can later choose a funded Coalesce transition into a multicellular organism.
Not implemented.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The playtest found mutation offers the arena could never pay for. A mutation's
matter cost is the real body difference (ADR-0118), so it cannot be discounted.
Rules 6 cut it honestly:
- genome schema 3 steps a third as far (1/300 of the range);
- development version 3 charges a third of the construction energy (13 instead of
40 pJ per 1000 fg).
Founder 2 uses both. The cellular-v5 opening creates rules-6 regions on bundle v7,
which schema v41 admits. Existing lineages, regions and committed history are
unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An offer the cell cannot afford stayed open, and only one offer is issued at a
time, so banked feeding credit never became a new offer. A v10 choice naming
operator 0 now declines the exact outstanding offer. It is reserved and published
like any choice: schema v40 accepts operator 0 in the reserved input and trace
selections and stores result 3, declined. The owner consumes the offer and
changes nothing else, and the client reports it as committed. Old traces never
carry operator 0, so their replay is unchanged. The Evolution panel gets a
"Decline this offer" button.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The v10 cellular perception carries the bud cost after the diagnostics block: the
energy (construction plus the bud's provision) and matter per channel one bud takes
from a fully grown cell's reserve. biology::bud_cost reads it from fund_bud itself,
so the shown cost is exactly the charge; the server caches it per genome. The
client shows it and names the channels the reserve is short on. v10 clients must
be rebuilt.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Only one client per machine could sign in: the saved login lived under a single
Credential Manager name, and Keycloak ignores prompt=select_account, so the
browser reused its single sign-on session. --profile NAME keeps one saved login
per profile (the default name is unchanged), and authorization asks for
prompt=login so the browser shows the login form.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The aevolution-grant-issuer Secret was recreated with key issuer.key and the
broker has run from it since 18:57 UTC; reverts 73a0c5a.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The existing aevolution-grant-issuer Secret stores the raw 32-byte issuer scalar
under key.pem; the broker reads it at /run/grant-issuer/issuer.key.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign In / Register opens the system browser (PKCE S256, loopback 127.0.0.1:47600)
and keeps the refresh token in Windows Credential Manager. The client then fetches
a 10-minute grant from grants.aeternalisgames.com and connects to the cellular DEV
region. It renews the grant about a minute before expiry through SessionRefresh,
and again after a lost connection. Sign Out closes the session and revokes the
login at the broker and at Keycloak. Grant replies are cross-checked against the
grant record before use. The manual grant-bundle path stays for developers.
The bounded JSON reader moves to evo_json (evo::serialization), shared by the
broker and the client. Adds the client-auth tests. Completes work started in
another session: main.cpp wiring, refresh expiry tracking, no requests for a
superseded session, and clang-tidy and Windows header-order fixes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>