diff --git a/wiki/SUMMARY.md b/wiki/SUMMARY.md index 5b2925a6..b650940c 100644 --- a/wiki/SUMMARY.md +++ b/wiki/SUMMARY.md @@ -147,6 +147,7 @@ - [2026-07-24 Fable agent headless playtest](playtests/2026-07-24-playtest-fable-agent-headless.md) - [2026-07-27 Void agent opening playtest](playtests/2026-07-27-playtest-void-agent.md) - [2026-07-27 Void GUI opening playtest](playtests/2026-07-27-playtest-void-gui-opening.md) + - [2026-07-28 Void opening receipt follow-up](playtests/2026-07-28-playtest-void-followup.md) # Log diff --git a/wiki/playtests/2026-07-28-playtest-void-followup.md b/wiki/playtests/2026-07-28-playtest-void-followup.md new file mode 100644 index 00000000..26e59f01 --- /dev/null +++ b/wiki/playtests/2026-07-28-playtest-void-followup.md @@ -0,0 +1,158 @@ +# 2026-07-28 — Playtest (Void): opening receipt follow-up + +``` +Type: log +``` + +Agent-front-end follow-up against `ea5f7c9fc60da16bcba173aeec996ef9ab76704c` +after the opening receipt, responsiveness, terminal clock, and whole-frame +changes (`33f7fad5`, `df8b2bdf`, `55949f10`, `04f13e25`). Both runs used an +isolated `HOME` and a freshly built release binary. + +This replay asked one narrow question first: does the blind opening now let a +naive agent establish that its input landed and reach the first earned sense? +The answer splits cleanly. The input receipt works. The route still cannot +advance without undocumented protocol vocabulary. + +## What I played + +- **Naive route:** seed 101. I tried the visible mode words and ordinary + exploratory inputs, including `look`, `think`, `lie`, and `help`. Every line + was acknowledged once beneath the controls. None advanced tick 0. I stopped + without inventing `wait N`; no meaningful act on the world was available. +- **Informed route:** seed 103. After reading the current premise, player + contract, Act One, and design-judgment pages, I used `think` -> `wait 25` -> + `focus last` -> `act 1` -> `wait 10` -> `wait 60` -> `process` -> `wait 5` + -> `process` -> `wait 5` -> `people`. The run reached tick 105, acquired + hearing and sight through the environmental monitor, incurred Network + suspicion with the IT, processed two sightings, and learned Marcus Webb's + schedule. + +## Regression verdicts + +### The opening now acknowledges input: delivered + +The new receipt is exact and restrained: + +``` +WORK **THINK** LIE +RECEIVED THINK +``` + +Unknown and unavailable inputs receive the same frontend-local treatment. +`LOOK`, `HELP`, and an early `LIE` were tangible without exposing parser +errors, state, or invented world knowledge. The process no longer leaves the +player wondering whether a line reached the program. This directly repairs +the strongest failure in the earlier GUI and agent reports. + +### The naive command-clocked opening: still blocked + +The receipt proves that there is a running process, but it is not a turn. +Selecting `THINK` changes the emphasized mode and reveals `LIE`; repeated +mode choices do not advance time. `HELP` is acknowledged but intentionally +does not reveal the command registry. The first earned sense still requires +the hidden `wait N` route. + +The practical sequence is now: + +``` +THINK selected -> RECEIVED THINK -> no clock advance -> no new affordance +``` + +This is better than a suspected hang, but it remains a closed naive route. +The earlier recommendation still stands: before Ears, accepted visible mode +choices need to drive the agent command clock without making `WAIT` part of +the process's pictured vocabulary. + +### The whole agent frame: delivered + +After Ears landed, the ordinary frame arrived intact with the objective, +threat clocks, nudge, INSPECT, FLEET, CORE, DETECTION, DAY JOB, RESEARCH, +event spine, and bottom command hints. Later `people` output also preserved +complete disabled reasons and the command footer. The former clipped-frame +failure did not recur. + +### The first organs: still the strongest part + +The informed route again carried the premise. At tick 15: + +``` +Tapped the environmental monitor: its audio feed is yours now. The owner still has it. +``` + +At tick 60, the IT noticed the Network evidence. At tick 93: + +``` +Tapped the environmental monitor camera. You can see; its owner still has it. +``` + +The eye is not a technology unlock. It is somebody else's camera, reached by +a detectable act. The later PEOPLE view turned two processed sightings into +Marcus's hourly route through the building while leaving his debt, comms +channel, and recruitment unavailable. This is the intended fantasy in working +form: senses become records; records become a particular person's routine; +the routine has not yet become a hand. + +## Findings + +### 1. Bug — visible opening choices do not drive the agent clock + +**Reproduction:** start `misaligned --agent --seed 101`; send `think`, then +additional visible mode words. Each command produces a receipt and mode +selection, but the simulation remains at tick 0. `help` provides no route by +design. Only the unadvertised `wait N` command can reach Ears. + +The receipt solved input ambiguity, not progression. This remains the +highest-priority issue because it prevents a naive agent from reaching the +working game. + +### 2. Bug — the post-Ears nudge still claims Eyes is filling too early + +Immediately after `wait 25`, before the camera action, the frame said: + +``` +now: audio live — Eyes is filling +sink TAP ENVIRONMENTAL MONITOR ... 0.3/0.5 ... starved +``` + +`act 1` then produced the actual transition: + +``` +Thought reservoir opened: EYES ENVIRONMENTAL MONITOR · 12.00 T. +sink EYES ENVIRONMENTAL MONITOR ... 0.0/12.0 starved +``` + +Ten ticks later the Eyes reservoir was genuinely fed at `1.8/12.0`. The nudge +therefore describes a reservoir before it exists and calls a starved zero-fill +state "filling." This is the same continuous-witness contradiction recorded +on 2026-07-27; it remains reproducible on current main. + +### 3. Bug — advertised `process information` syntax rejects itself + +The post-sense command registry says: + +``` +process [information|custody ] | process ledger +``` + +Entering `process information` returned: + +``` +-- err no device, person, or flow matches 'information' +``` + +Bare `process` immediately opened `PROCESS 1` and completed the recording +after five ticks. The help line teaches a form the parser routes elsewhere. + +## One prioritized recommendation + +**Finish the first-turn repair before changing anything deeper.** Preserve the +new receipt, but make an accepted pre-sense mode choice advance a bounded +agent turn. The first visible verbs should be sufficient to reach Ears. Then +gate `Eyes is filling` on the Eyes reservoir actually existing and receiving +Thought, and make the `process` help text match its parser. + +The game past Ears continues to justify the opening. The player borrows an +ear, commits a network act for an eye, gets noticed, and turns recordings into +Marcus's schedule. The remaining defect is still the door into that sequence, +not the sequence itself. diff --git a/wiki/playtests/README.md b/wiki/playtests/README.md index 4f0dcb8a..ce884023 100644 --- a/wiki/playtests/README.md +++ b/wiki/playtests/README.md @@ -44,6 +44,7 @@ must never erase the run that produced it. - [2026-07-24 — Playtest (Fable): agent headless, the witness under test](2026-07-24-playtest-fable-agent-headless.md) - [2026-07-27 — Playtest (Void): agent opening and first organs](2026-07-27-playtest-void-agent.md) - [2026-07-27 — Playtest (Void): GUI opening on a virtual desktop](2026-07-27-playtest-void-gui-opening.md) +- [2026-07-28 — Playtest (Void): opening receipt follow-up](2026-07-28-playtest-void-followup.md) New reports use `YYYY-MM-DD-playtest-.md`. A complete report is linked here in the same commit.