Five-week validation will test whether players understand the representative quest, solve it independently and choose to continue exploring. Two small test rounds will guide improvements to instructions, clues and reward presentation. The participant numbers and thresholds below are planning targets.
Two observation rounds
The plan is to test six participants in each of weeks 4 and 5: three using Korean and three using English. Findings from the first round will inform revisions for the second. Recruitment will prioritize new participants for round two, and the report will state the actual sample and any repeat participation.
Hypotheses to observe
| Item | Internal target | Observation |
|---|
| Goal understanding | 5 of 6 | Explain the task in their own words after reading the request |
| Independent two-clue solution | 4 of 6 | Select an answer using both clues; record hints and observer help separately |
| Reward understanding | 5 of 6 | Explain the seal, title, map change and use for the seal |
| Voluntary next exploration | 4 of 6 | Open the letter or next objective without being asked |
Independent solving means connecting both clues without an observer explaining the answer. Hint use will be recorded, and missed targets will guide revisions to instructions, clue legibility, choices and feedback. Findings will be interpreted as usability evidence for the participants and conditions tested.
Functionality and restoration
| Check | Record |
|---|
| NFC entry | Device, tag and app versions, read position, success, failure and retry |
| Two-clue puzzle | Correct and wrong answers, three hint levels, feedback and progression |
| First reward | One award per place; no duplication through language changes, scans or replay |
| Seal use | Ownership, letter unlocked, next objective visible, no extra points |
| Save/resume | Restored stage, answer, hints, letter state and collection |
| Korean/English parity | Same clues and core rewards; legibility and comprehension |
What to record
Record participant code, language, gaming experience, device/app/tag versions, wrong answers, hint levels, observer interventions and reasons, save/resume results, next action and its reason. Observers record where people get stuck before explaining solutions.
Distinguish curiosity from return visits
This test will observe letter reading and next-objective selection as signals of interest in further exploration. Visits to the next location and return visits on another day will be measured separately during later field operations.
Demonstration and findings
The proposal presentation will use a 90–120-second sequence focused on city changes, clue use and explorer records. The APK, physical tags, bilingual specification, video, revisions and retest findings will let partners assess both the experience and its production evidence. Actual solving and walking times will be measured during field tests.
Current evidence consists of functionality checks on the web demo. Integrated Android/NFC testing and actual user sessions are planned under the schedule above. Long-term return visits will be measured in later field operations.
MVP production and validation · The first visit
