Update cellular playtest readiness gates
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 6s
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 / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s

This commit is contained in:
dingo
2026-10-11 01:37:06 -04:00
parent bf87aa4de4
commit e558ac00c6
3 changed files with 19 additions and 13 deletions
+6 -4
View File
@@ -9,8 +9,9 @@ single-region exploratory probe is the next gate, before expanding mutation in
11.4; its instructions are in
[`M11_3_CELLULAR_PROBE.md`](playtests/M11_3_CELLULAR_PROBE.md). The v8 cellular
path, first-life result, steering, feeding and the player's observations still
need confirmation. M11.2 cross-region life-owner routing and process-kill
qualification also remain open.
need confirmation. M11.2's owner lookup, pre-claim redirect, client-follow path
and PostgreSQL restart test are implemented and pushed; Linux/PostgreSQL CI has
not yet been confirmed, so multi-region qualification remains open.
## Current gate - 2026-10-09 (M11.2)
@@ -60,8 +61,9 @@ the maintainer chose directional rounding):
Atomic body/checkpoint publication and life binding are in the adapter. The
separate profile-3 region host now recovers and durably publishes a new life,
without advancing biology. v5 authenticated session execution and primitive
profile selection are implemented; cross-region owner routing/reconnect,
process-kill qualification and this session-process CI run remain. The v17
profile selection are implemented. The migration-24 life-owner lookup,
pre-claim redirect and operator route catalog are now implemented; two-region
restart and client-follow tests are pushed but await CI confirmation. The v17
PostgreSQL and host integration tests have prior CI confirmation.
Open from M10 (BACKLOG):
+7 -6
View File
@@ -63,12 +63,13 @@ Starting thresholds marked tunable stay versioned and visible to playtesters.
profile must still define perception range and resource visibility. Do not
use the probe marker as an organism or expose unseen resources as client
knowledge.
4. **Owner routing:** 11.2 still lacks authenticated routing/reconnect when an
account's life is in another region. Resolve the ADR-0100 protocol gap (v6
owning-region response plus authoritative endpoint lookup, or server-side
routing) before claiming multi-region life control. A single-region local
playtest may be prepared independently, but cannot close 11.2 or validate
cross-region play.
4. **Owner routing:** ADR-0116 selects server-side routing when an account's
durable life belongs to another region. The 11.2 implementation now resolves
the owner before control claim and redirects through an operator-provisioned
`--life-route` catalog. Migration, process-kill and client-follow tests are
pushed; Linux/PostgreSQL CI remains unconfirmed. Do not claim multi-region
control until those tests pass. A single-region playtest may proceed
independently after its cellular route catalog and v8 build are verified.
No new dependency or renderer is required. If the selected spatial, checkpoint,
or publication design conflicts with accepted architecture, stop that affected
+6 -3
View File
@@ -6,9 +6,12 @@ complete. Run it after CI is green for the v8 server and client changes.
## Start
Start the already provisioned cellular development region. From the folder
containing the freshly built network-enabled client, connect with the grant
bundle and development CA:
Start the already provisioned cellular development region. Its server must have
the complete per-world `--life-route REGION=HOST:PORT=TLS_NAME` catalog, with
one entry per region including its own. For a single-region probe, provide that
region's advertised QUIC endpoint as the one entry. From the folder containing
the freshly built network-enabled client, connect with the grant bundle and
development CA:
```powershell
./evo-client.exe --connect "HOST:PORT" --server-name "CERTIFICATE-NAME" `