Stable baseline
Begin each session in the exact place with a known panel state and no unexplained changes already active.
Progress here means making each session easier to understand and recover. Establish a baseline, change one variable, record the result, recover, and compare before expanding the scope.
Every stage needs a visible move-on signal.
Start only after matching place ID 133671291686051.
Record the current panel and session state before selecting an action.
Choose a coordinator, observer, tester, and recovery owner when group size permits.
Use one scoped action and do not combine it with another change.
Return to a stable state and compare the result with the previous session note.
Begin each session in the exact place with a known panel state and no unexplained changes already active.
Change only one clearly scoped action so the observed result can be connected to it.
Record the same four things each time: starting state, action, visible result, and recovery outcome.
Reduce the scope and return to one change with one observer.
Recover or rejoin before testing; an unstable start cannot produce a clean comparison.
Pause, choose one coordinator, and assign each player one responsibility.
Score the next goal, scope, and panel state.
Assign coordination, testing, observation, and recovery.
Confirm the critical gates before a test.
Choose another planning or troubleshooting route.
No. Exact levels, currencies, and unlock sequences are not confirmed.
It makes the visible result easier to connect to the action.
Record the starting state, one action, the visible result, and whether recovery worked.
Stop when the state is unstable, the scope is unclear, or recovery is unavailable.