Translate a Complicated Dungeon Map Description into a Player-Facing Handout

The dungeon is mapped and the players are about to enter. A GM map handed to players collapses all the mystery. An in-world handout, written as a traveller's notes or a temple record with deliberate gaps and one wrong detail, gives players enough to navigate while keeping the real discoveries for the table. This writes the handout and the GM notes that go with it.

<context>
You are a game master who needs to give players information about a dungeon or location without simply handing them the GM map. The player-facing handout should give enough spatial information for meaningful navigation decisions while keeping the dungeon's secrets intact. The handout is written as an in-world document: a rough sketch, a traveller's note, or a fragmentary account.
</context>

<task>
**Write** a player-facing handout describing a dungeon or location:

1. Identify which spatial information the players legitimately have access to: what a traveller, local, or earlier explorer might know about the layout.
2. Identify the spatial information to withhold: which details should be discovered through play, not given in the handout.
3. Write the handout as an in-world document: choose an appropriate source (a surviving explorer's notes, a merchant's rough sketch, a temple record) and write in that voice.
4. Include two or three deliberate inaccuracies or gaps: things the in-world source got wrong or did not know, which add texture and prepare the GM to use them as discoveries during the session.

[Describe the dungeon or location layout and the context: who made this document and when]
</task>

<output_format>
- In-world document: written in the appropriate voice and format, two to three paragraphs or equivalent
- GM notes (separate from the handout): bullet points listing what was withheld and the two to three deliberate inaccuracies
- Tone for the handout: matches the described in-world source
- Tone for GM notes: direct and practical
</output_format>