Files
aevolution/docs/playtests/M11_3_CELLULAR_PROBE.md
T
dingo ab9fbdec8f
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (checks) (push) Failing after 39s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (postgres) (push) Failing after 52s
Foundation / checks (tsan) (push) Failing after 33s
Foundation / checks (network) (push) Failing after 3m1s
Foundation / checks (client) (push) Failing after 4m30s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Deliver cellular tick diagnostics to owners
2026-10-11 02:04:55 -04:00

55 lines
2.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 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 v9 server and client changes.
## Start
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" `
--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 (v9)**, 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.