A Pact in the Margin

A resting place in Debt of the Quiet Nave offers recovery and a promise about the return. The player can take that promise without knowing exactly what the next room looks like. The design question is whether a player can still find the condition when it matters. It is reasonable for them to forget the wording of a long note after spending several minutes on a route. The ledger should make the relevant part available again.
Read the agreement at the refuge
The first test begins in a niche with a shallow candle tray and a view of one arch. Use a short sentence to say what the refuge gives and a second to name the condition attached to it. Place each sentence next to the corresponding drawing of the opening or marked shelf. The player can rest or go past without needing to resolve an unrelated clue. That choice establishes what appears in the margin as they continue uphill.
Another version displays a single folded line with the offer and condition together. It can be read without a second screen, but it asks the player to notice that part of the line refers to another visit. Watch which noun they repeat after they make the decision. If they mention only the candle, they may have understood the place and missed its condition. If they name a return threshold, the record has given them something usable for the descent.
Let the ledger travel without taking over the scene
While the route continues, the margin keeps a small mark for the agreement and the name of the refuge. It should be possible to open the wording on purpose. A player studying a staircase should not need to read the whole line at every landing. In a test where two refuges are used, sort their notes by where someone can recognize them, not by which promise sounds more important. A familiar name helps at the moment the player looks across the shaft.
Use the same short title on the physical arch and in the ledger. Both marks should tolerate a change in light. A name embedded in a bright picture could disappear when the view darkens, so keep a text label alongside it. The player should be able to move between the place and its line in the record without learning a second set of names. That pairing is enough for the first prototype.
Bring the question back on the way down
The next time a condition affects a route, show the mark of the refuge again. The question is not whether the player memorized the line. Ask whether they can find the promise and identify which alternative still remains. The current route could pass the older refuge, or it could lead to a side stair with fewer places to stop. The ledger gives the reason the old path changed. It leaves the player free to choose the other route.
Ask the same question after a run that ignored the first refuge. If the new route shows the same message about a promise, the information is too generic. Instead let the place remain quiet when there is no condition to report. A second test can show whether the absence of a mark is clear when the knight has now taken a promise somewhere else.
Compare the notes after a run
Find the first point where someone can name the correct refuge on the return. If the map works and the wording remains ambiguous, change that wording before adding another marker. The Landing You Leave looks at a similar memory on the route. The Bell Below the Landing uses the same approach to a change caused by a signal.