Files
dingo 8b54e7447a
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
Close M11.9 for now and review the overhauled cellular UI
2026-10-17 11:35:56 -04:00

3.6 KiB

M11.9: Run repeated-life playtests and close the loop

Maintainer closure - 2026-10-17

The maintainer explicitly closes M11.9 for now and authorizes proceeding with M12. This is the gate decision for continued engineering. The incomplete sample, solo feedback and fun/variety questions remain recorded; this closure does not invent completed sessions or empirical product validation. Retain the local playtest backlog for later iteration rather than using it to block M12 work. Review the current microscope UI and rules-8 contracts before further integration. The closure and UI review records the actual production-panel screenshots inspected and the scope of this decision.

The playtests themselves are human work for the maintainer and participants. This plan tracks what engineering provides for them: the predeclared plan (M11_9_REPEATED_LIFE_PLAYTEST), the bounded telemetry boundary (ADR-0130) and a DEV region running the complete M11 rules.

Segments

Segment Owner Acceptance evidence
11.9a: plan and telemetry Engineering Predeclared questions, sample and recording; evo-world-clone summary reports account-free aggregates; tests on owner states and a provisioned region
11.9b: DEV region Engineering, maintainer approval for the Argo sync A cellular-v4 region on a CI-built server image and postgres-tools with schema v38
11.9c: sessions and results Maintainer and participants Notes per the plan; answers per question; retested changes

Progress

  • 2026-10-16: solo feedback recorded against all eight questions. The maintainer reports repetitive food-camping, unproven mutation effects and incomplete predation/fun evidence; offline behavior and death-cause clarity have limited positive feedback. Returning to a living cell shows "Existing cell is already bound to this account" with no cell visible (M11-PT-001). Diagnose resume/routing/perception before further sessions. Proposed food scattering, feeding-rate experiments, feedback/death UI and budding motivation remain retest/design work. The sample and product acceptance are incomplete.

  • 2026-10-14: 11.9a implemented. summarize_cellular_play and evo-world-clone summary; owner tests check death and bud aggregates, and the PostgreSQL store test runs the command on a provisioned cellular-v4 region.

  • 2026-10-14: 11.9b prepared. CI run 376 (215a9ea) passed all jobs (the postgres job after re-running a timing flake in the ASan upgrade-comparison drain); the DEV overlay promotes server e891f942 and postgres-tools fe3558e9 (schema v38) and serves region 100/4 with the cellular-v4 opening. The maintainer's full Argo sync applies it.

  • 2026-10-15: region 4's nursery ran out. It funded 8 founders, and ADR-0127 has no refill, so births were refused for every account. DEV now serves region 100/5 with the same cellular-v4 opening and a 64-founder nursery. The grant broker's default region and route follow it. Region 4 stays in the stores, unserved. A nursery refill rule remains a separate design question.

  • 2026-10-15: after the first sign-in playtest, DEV serves region 100/6 on cellular-v5 (rules 6, ADR-0132): a third of the mutation step and of the construction energy, the same 64-founder nursery, and 16 patches holding about 7.5x region 5's food. Buds show their cost (ADR-0129 amendment) and offers can be declined (ADR-0120 amendment, schema v40). Region 5 stays in the stores, unserved.