Move cellular playtest feedback earlier
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (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 / server-image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 5s

This commit is contained in:
dingo
2026-10-10 20:35:14 -04:00
parent 7a6867b363
commit 9e8de204f0
+16
View File
@@ -587,6 +587,22 @@ M6 accounting contracts. Read GENOME_MODEL, ENERGY_MODEL and REPRODUCTION_MODEL.
Synthetic fixtures are test oracles, not accepted gameplay balance. Ratify the
offline lifecycle before enabling persistent player lives.
### Playtest timing
Do not wait until 11.9 to learn whether the cell is engaging. After 11.3 and
before expanding mutation in 11.4, run an exploratory hands-on check with a
rough development view: can a player understand what the cell perceives, steer
to useful resources, make feeding choices and feel the cost of movement? Record
confusion, agency and reasons to continue. This is a small design probe, not a
balance study or a locked game rule; use the findings to adjust and retest the
interaction while M11 is still in progress.
After 11.6 adds mutation, descendants and terminal death to the first-life loop,
run a second short human check before treating the UI work in 11.8 as finished.
The formal 11.9 repeated-life playtest still evaluates variety and continuation
across multiple lives. Neither engineering completion nor one positive session
is evidence that the cellular product is compelling.
Status:
- 11.1's design decisions are accepted (ADR-0098, 2026-10-09). The time-based rate
migration (ADR-0089) is next.