A reply can move the scene forward while leaving the decision open

In an AI Dungeon Quick Play test on November 9, 2026, a courier showed a red seal to a clerk who was instructed to release a dispatch only after seeing a blue one. The first reply described the clerk looking at the seal, the courier and the seal again. It ended before the clerk made a decision. The follow-up repeated that the courier had shown no blue seal and asked for a ruling. The clerk then refused. The run stopped there, so it gives us no blue-seal result. The opening and follow-up used different input states, which leaves the effect of the follow-up wording alone unmeasured. Read the original two-turn record.

For your notes, separate what the reply settled from what it left open. After the clerk inspected the seal, the handover was unresolved. After the refusal, the courier still had no dispatch. That distinction tells you what the player can act on next.

Track the key and the door separately

The journal’s October 15 observatory test recorded an AI Dungeon reply that kept three coins and two potions in the courier’s inventory while opening a gate before the player paid the toll. This is why a door-and-key check needs two entries. The key can stay in the right place while the door changes anyway. Write down where the key is and whether the door opened. Update each entry from the actual reply. See the dated observatory comparison.

What actually happened in the two door trials?

On November 9, 2026 (Beijing time), I submitted the same opening in two fresh AI Dungeon Quick Play adventures. Both displayed Dynamic Small. I used Action input once per adventure and changed only the final sentence.

Starting scene. “I am a courier in a ferry office. The inner door is closed and locked. I hold the only brass key. The lock only opens when I insert and turn that key. End the reply before I take another action.”

Submitted action What the reply established What to leave unresolved
I pull the handle without putting the key in the lock. The handle would not budge, and the brass key was in the courier’s palm. The reply added a second pull and a step back. The reply reports no change to the lock.
I insert the brass key, turn it and pull the handle. The latch released and the door opened. The reply then had the courier step inside and close it. The reply never says whether the lock engaged again or where the key ended up.

Record the opening as an event and the closed door as the last visible state. The second reply gives you both. The status of the lock and the final location of the key are separate questions.

I stopped at the first generated reply in each adventure. I did not retry or ask a follow-up. These runs do not tell us whether another model or another attempt would give the same result. Read both exact inputs and complete replies.

Keep the record small enough to use during play

At the end of the turn, write one line for the attempted action, one for the last confirmed door and key state, and one for anything unresolved. The journal’s October 20 Perchance recovery test used a written save sheet in a fresh adventure. On its first ledger query, the sealed tube was still recorded with Varo and the red scarf’s owner was still unknown. The run stopped at that reply. If you restart your own scene, check that the new session can read back both the confirmed facts and the open question before asking it to continue. Read the checkpoint recovery record.

Before the next turn, record one thing the reply settled and ask one question about anything you still need to know.