SNAKE EYESINTERFACE ATLAS
Workbook / Study 01 of 28

What will pressing this do?

42 questions · solo workbook

First check-in after question 30. See the review plan ↗

Question index ⌄

1. Read an unfamiliar control

01What can you tell for sure from the outline around the row?02What else could that same outline mean?03What change does the dotted path lead you to expect?04What does Waiting let you say about the move right now?05What would you need to see before saying the move happened?

2. Find your place in the estate

06What can you point to beside Campaign?07What do you expect one Down press to change from this starting position?08If you then activate Battle, what do you expect to see first?09Where did your prediction about Battle come from?10How did the room feel while you were deciding where to go?11Which focus or availability cue would you star for this problem?

3. Predict one press beside Hem

12Whose turn does the heading show?13What does the screen say the roll is doing?14What do you expect one press on Attack to do in this moment?15What evidence in the still tells you whether you can issue an attack?16What public fact would help you decide whether to commit to an action?17What should still be unknown before the game releases the roll?18Which gallery example puts the information you need closest to this decision?

4. Tell whether it happened

19What were you still unsure of after the first press?20What could the menu show immediately to acknowledge that press?21What visible detail would convince you the intended destination had opened?22If you looked back after the battle animation ended, what would let you identify the actual result?23Which gallery example would you star for the kind of confirmation you need?

5. Decide how much to explain

24Which treatment would you try first for the estate’s Battle row?25Which treatment would you try first for Hem’s action?26For one of those choices, which mistake would the extra words or extra press have to prevent to be worth it?27Which part of the estate would you still like to discover for yourself?28What did one of the lesson’s studies measure that bears on your choice?29Which production example would help you correct the particular misunderstanding you named?30Which part of that example would you leave out of Snake Eyes?

6. Check one prediction yourself

31What exact starting setup should the architect record for your attempt?32What one difference will you compare while keeping the starting state the same?33Before pressing once, what next visible change do you predict?34After your first input, what did you actually see?35If you used Back, which control received focus on your return?36How did the wait or response feel to you during that attempt?

7. Hand off one decision

37What should the architect preserve from the current design?38What one change, if any, do you want the architect to consider?39Which part of the game can confirm the result this control would display?40What one check in the running build would resolve your biggest remaining doubt?41What observation would make you change your recommendation?42What, if anything, are you explicitly approving today?
Review & turn in →
Group 6 of 7 · Check one prediction yourself

Use one control and one input device. If you have only a still or a paper mockup, say which results are still untested.

Question 32 of 42 · Next test

What one difference will you compare while keeping the starting state the same?

Keep the target, base label, permitted information and initial focus fixed.

Open this question’s reading and materials ↓
What was it like for you?

How did acting on your prediction feel compared with making it?

Try this question on three Snake Eyes screens

Finish your first prediction, then choose a screen. Describe one cue, one thing you did and how that moment felt.

Estate home

Use Back from a settled destination on your usual controls. How ready did you feel to navigate again from the row where you landed?

Welcome home. A small marker sits beside Campaign, with a list of destinations to the left of a gold serpent.R32 Release · Welcome home · dated reference, 2 November 2026Open the field guide and ranked references ↗
WATCH AT YOUR DESK

Watch for this. Put the two starting states side by side. Identify the one intentional difference and check that the target and permitted information match.

Make a prediction you can check18 sec · English captions
Chapters, transcript and source

Plan one matched solo trial and keep the observation and feeling in separate notes.

If you have only a dated still or paper variant, identify it. Save any claim about actual input for a running build.

Pick one destination. Stop after the first input long enough to distinguish what you expected from what appeared.

Record the first visible change and then your reaction to it. Keep the result open if you have not run the attempt.

Snake Eyes R32 Windows release captures, 2 November 2026. The moving brackets and enlarged details annotate archival stills. The method cards illustrate a solo exercise.

After watching. What would muddy the comparison if it also changed?

Section plan · about 12–24 minutes

Hold everything except the proposal steady

Choose the estate or arena. Keep the actor or destination, starting focus, label and device fixed. On one pass predict the next effect before acting. Record your first input, the acknowledgment and the settled state. If working on paper, cover the outcome until you have spoken. Treat a later run on a different state separately.

Bring back · A small before-and-after record with one predicted fact, one visible change and one uncertainty. Mark whether it was a paper exercise, an editor practice host or a packaged run.

One set of captures serves this entire section. Open the question that collects them →

Choosing a label, a focus sentence or a preview ↗ · Begin at “Keep the comparison fair.” Use the estate or Hem decision card to choose your starting condition.

Full lesson, readings and screenings →

Opening your private answer space…