Mysilk Studios

Who Keeps the Water

A stream branches between village access and a pledged channel duty
A stream branches between village access and a pledged channel duty

In The Terrace Petition, a village asks for a road to remain open until seed can be carried uphill. The keeper offers passage if the channel beneath the shrine is tended. The original request names a benefit. The answer attaches work to it. The first prototype asks whether the player can identify who would do that work by putting the proposed duty beside the sentence that asked for help.

Read the request in its place

The seed is waiting near the lower terraces. The person who asks the envoy to ascend can tell them how much time remains, and why there are two paths past the channel. A worker who normally clears the watercourse can explain what it means for a promise to last all season. Give both characters a real reason to be there. The person who makes the request may know little about the channel at the top of the stair, but they can see where a blocked path leaves the seed.

A player can speak with the worker before going to the shrine. In the first test, this conversation identifies a part of the season when the worker cannot take on additional duties. It offers a concrete reason to ask how long the shrine expects the channel to be maintained. If the player goes straight uphill, they still hear the condition. They can bring it back for clarification, so the earlier conversation saves a trip without becoming an obligatory source of the only viable answer.

Put the offer on the other side of the ledger

The shrine gives a reply that names a period of access and an expected obligation. Put that statement at the same height as the original request. Use a small marker for the speaker and another for the person or group named by the duty. The group need not be known at first. A visible gap in that field can prompt a question better than a brightly colored quest marker. The player can ask the keeper which part of the agreement would change if the village cannot provide a worker.

On a return visit, keep the shrine’s wording with the date or sequence of the visit. Record the worker’s response beside it. Each line should remain readable once the envoy starts a revised request. Exchanging one version for the next erases a useful part of the game. The person who could read one offer as a modest favor may regard another as an obligation that extends beyond the planting season. A small version history shows what they are reacting to.

Test which consequence remains visible

Keep the two offers the same length and give the duty a full line in each version.

Prepare a case in which an agreement grants the same road access under two different duties. Ask the player to describe the difference before they carry either version down. If they can only repeat that the path opens, improve the display of the work. Try allowing the player to repeat one line aloud to a claimant. The claimant can ask which days are involved or name a missing participant, rather than merely confirming that the envoy selected the expected answer.

After the return, find out who the player thinks has agreed to the duty and how long the agreement lasts. Compare those answers with the record they actually have. A game can leave the outcome uncertain while still making the participants and wording clear. Keep that distinction at the center of the test. Two Vows at One Gate applies it to the time when an obligation begins. Petitions links the two cases and their supporting records.