Join the Cartaris Exploration Society on a race against a self-sealing temple door. Along the way, practise pulling a genuine who/what/why out of every teammate's tangled report — then prove it at the temple itself, finishing a lost expedition's unfinished work sorting old correspondence into requirement, solution, assumption, and out of scope to crack the final lock.

The developer quit on Friday. The repo is a mess. The new developer starts Monday. You are the Product Owner — and everything Joel built lives in code only he understood.

Work through three code files, a half-finished handover document, and a database schema. Find the technical debt, identify what is missing, and write the story that will brief the incoming developer. The combination to unlock your access is hidden somewhere in the work Joel left behind.

Your uncle Marcus is missing. The release he deployed on Friday night is broken in a way nobody can explain. On his desk: a laptop, still open. A sticky note reads: "If you're reading this, you know what to do. Start with the logs." Decode the deployment logs, trace the broken sequence diagram, find the missing requirement — and crack the safe that will tell you who took him and why.