This is a written recording plan
The public sources are dated text observations, not a published video. A future recording should show its own current controls and results instead of illustrating old numbers as if they were live footage.
Use the Library example to demonstrate a missing checkpoint and the Lekki example to demonstrate a completed arrival checkpoint. They answer different causal questions despite both containing a paid activity.
Give each claim its own shot
| Shot | What must be readable | What it prevents |
|---|---|---|
| Before travel | Active wish, location and current needs | Assuming the same starting wish |
| Final Go quote | Destination, transport and charge | Treating selection as departure |
| After arrival, before activity | Destination and Goals | Mixing arrival and purchase |
| Before paid action | Actual action name and fee | Using an old quote as today’s price |
| After completion | Receipt and Goals, before another action | Attributing a mixed window to one click |
| Return decision | Separate home quote | Calling the venue receipt the total cost |
Preserve the bookcase uncertainty in the edit
The historical Library route spent 800 on Find the Secret Bookcase and later showed four more stars and a replaced wish. Because it lacked an arrival-before-action Goals read, a caption should say the combined route worked, not that 800 is the proven unlock fee.
A new recording can fill that gap by reading Goals immediately after arrival. If the wish is already gone, the paid activity becomes a separate optional scene, not a required continuation of the reward demonstration.
Use a chapter break before optional park actions
In the 7 October Lekki check, the active canopy wish completed on arrival before the 500 Canopy Walk. The later Free treehouse rest and 400 picnic had their own needs readings and should get separate captions.
The 900 venue total excluded travel. Show the return quote as another shot; do not overlay the recorded 850 Shrine-to-Lekki fare onto a different home route.
Record only what is needed for the explanation
Crop account identifiers, personal details, private messages and full balances. The relevant charge, action result and wish delta are enough to explain this route.
A polished sequence does not add evidence
Menu seconds are not a measured runtime. A camera-style scene without an activity menu is a navigation shot, not action footage. Music, rewards and save reliability must be established by the recorded window before being described as results.
Sources & dates
Check what each source records. A menu label and a completed playtest are different kinds of evidence.
- dated editorial extractLibrary and Lekki action windows · reports dated 7 October 7 Oct 2026
- dated report archiveLibrary, canopy, treehouse and picnic report archive 7 Oct 2026
- dated editorial extractDesktop navigation observation · 9 October 9 Oct 2026