An oracle is not a replacement game master. It is a conversation pattern between your question, the current fiction, a random result, and your interpretation. The loop is simple enough to write on an index card: ask, interpret, move.
Ask From the Scene
Good oracle questions come from what is already happening. “Does the gate guard know my name?” is easier to answer than “What is the plot?” “What does the abandoned room still contain?” is better than “What should happen now?”
Ask one question at a time. If you ask three at once, the answer will tangle. If you need more detail, ask a follow-up after the first result changes the scene.
Interpret Generously
A result should pass through context. If the table says “cost,” look at what the character values. If it says “delay,” look at time, weather, travel, and relationships. If it says “help,” decide who can help without breaking tone.
Do not force the most dramatic interpretation. Choose the interpretation that creates a playable next move.
Move Before Asking Again
The common solo trap is endless consultation: roll, interpret, ask again, roll again, ask again. After an answer, move a piece, write a sentence, change a resource, reveal a clue, or choose an action. The table should create play, not replace it.
If an answer feels wrong, reroll or revise. If it feels flat, add sensory detail. If it feels too intense, soften it to the nearest safe version.
Keep a Question Log
Write unresolved questions in one place. Cross them out when answered. This gives the campaign continuity without requiring a long recap. It also helps avoid asking the same question because you forgot what was already established.
Oracle dialogue is a practice. It gets better when you ask smaller questions and trust yourself to interpret.
