Repository navigation
Explore play-first doke: eight ideas and three playable mocks - #3
Open
ishaansathaye wants to merge 2 commits into
Open
ishaansathaye wants to merge 2 commits into
ishaansathaye wants to merge 2 commits into
Conversation
This was referenced Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make the visitor's input matter
doke's proposed timing experiment offered an explanation to operate, but little to create or change. This research PR explores experiences where the visitor makes something recognizable and the system responds: an inhabited world, a retained mark, or a journey through the body.
It contains eight concepts, three original playable mocks, source research, and a proposed Rust implementation path after a direction is selected. The application is unchanged. This branch starts directly from the original
mainbaseline and does not depend on #1 or #2. Those PRs remain unmerged. This is a design review, not approval to implement or merge a direction.Start here
Open the local address in a browser. The mocks also open directly as HTML files. No build, account, data download or API key is needed. The localhost link is a local preview, not a public deployment.
Three experiences to try
After a Bite
Little Stranger
Memory Loom
These are captures of working mocks, not generated concept images. Only three compact previews are committed; raw captures and test output are ignored. The sketches use Canvas/SDR glow; the existing Rust/Wasm/HDR application is unchanged.
Other ideas evaluated
The research also scopes Echo (local sound becomes a recurring acoustic sculpture), Your Tempo (a personal rhythm leaves a persistent signature), Borrowed Eyes (a virtual gaze explores an adapting field made from your image), A Day in Tides (composed events shift generic body rhythms), and Project Memory (sanitized change events organize a memory surface). Each has a reason to return and a specific failure risk.
Primary inspiration includes Phloem, NeuroMechFly, Growing Neural Cellular Automata, Particle Lenia, Lenia, Sandspiel, Simbrain, Karl Sims, Evolution, Chrome Music Lab and Dear Data. The research separates design inferences from those projects' findings. No external code, art, audio or trained weights were copied.
The food/body work draws on primary studies and NIDDK/NIDCD material, distinguishing human evidence from mouse/preparation results. It separates sensory information, local gut control, blood-borne substances and endocrine mechanisms. Food names do not establish personal neurotransmitter levels or a digital twin.
Recommendation and decision
My recommendation is Little Stranger for the strongest game, Memory Loom for the smallest personal-input experiment, and After a Bite for the closest extension of the brain–body vision. These are judgments to test, not demonstrated enjoyment. A body playground should first earn its scale through one satisfying local mechanic.
The next production PR should implement only the interaction the project owner wants to keep playing. The document proposes explicit playtest gates and a bounded, reproducible Rust model, with actual model signals driving the existing renderer. Accounts and leaderboards are deferred.
Review and verification
node tests/play-mocks.mjspassed locally in Chrome: transport/replayed taste cues, drag, wave, zoom, pause/reset, food consumption, paint/erase, partial-cue retrieval, ambiguity refusal, empty-cue handling and keyboard drawing.9bf25d3(run). GitGuardian,git diff --checkand local Gitleaks scans also passed.