Document the first cellular playtest
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s

This commit is contained in:
dingo
2026-10-11 01:15:27 -04:00
parent 1bba54ebd8
commit 108879d2fc
3 changed files with 59 additions and 0 deletions
+4
View File
@@ -370,6 +370,10 @@ scoped change before starting the next segment.
markers, lists their exact perceived stocks, and lets the player select a
patch for continuous feeding. The client build and live-region probe still
need verification before this segment can be called playable.
- 11.3e-4: [the probe checklist](../playtests/M11_3_CELLULAR_PROBE.md) records
startup, controls, scope limits and the human feedback needed to decide
whether the cellular loop merits further investment. It is ready for use
after CI confirms the v8 server/client build.
## Exit boundary
+4
View File
@@ -6516,3 +6516,7 @@ result. It is not counted as a build or test result. QUIC runtime, PostgreSQL
CI, and the real-region player probe remain pending. `clang-format` is not
installed in this Windows environment, so formatting validation is also
pending in CI.
The M11.3 cellular probe checklist was added for the first human session. It
does not count as live-region or usability evidence; those results must be
recorded after the operator confirms CI and runs the dev-region probe.
+51
View File
@@ -0,0 +1,51 @@
# M11.3 cellular probe
This is the first hands-on check of the cellular stage. It is a one-player,
single-region engineering trial, not a balance sign-off or a claim that M11 is
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:
```powershell
./evo-client.exe --connect "HOST:PORT" --server-name "CERTIFICATE-NAME" `
--ca "C:\Dev\tokens\dev-ca.pem" --grants "C:\Dev\tokens\m10-grants" --cellular
```
Replace the endpoint and certificate name with the values for the running dev
region. The launcher can do the same: fill in endpoint, server name, CA and
grant bundle, check **Cellular trial (v8)**, then connect. Do not select the
load-test grant bundle for an interactive session.
On first successful login, the client submits a stable first-life request. The
Session panel reports whether a founder was born or an existing life is bound.
Use the client’s **Controls** panel for the current movement bindings. Nearby
provisioned food appears as green markers when stocked and grey markers when
empty. The panel shows the server’s exact perceived stock; **Feed this patch**
continues targeting it until **Stop feeding** is pressed. The server still
decides movement, contact, intake and costs.
## Notes to record
- Client build identity, region, session tick, and the status shown for the
first-life request.
- Whether the cell is easy to see and steer, and whether movement feels
responsive at the current 50 ms tick.
- Whether nearby patches and their inventory make it clear where to go; note
how often the selected target is out of contact and what feedback explains
that result.
- Whether feeding changes the chosen patch stock as expected, whether it is
clear when stock is empty, and whether the visible resource/action feedback
lets you understand the cell’s costs.
- The first confusing moment, the first satisfying moment, and whether you
would choose to play another five minutes. Include an approximate duration.
## Scope limits
The probe covers one primitive life in one region. It does not cover mutation,
reproduction, death recovery/re-entry, cross-region ownership, or the final
presentation. Record any balance or tuning impressions as observations; do not
turn them into game rules without a later decision.