Runes

Yes or no runes: a conditional method, stop rule and three-rune alternative

A practical guide to yes or no runes: method options, the absence of an ancient universal table, neutral answers, reversals, conditions, a stop rule and when to use three runes.

You can use runes for a yes-or-no question, but a responsible answer is rarely an unconditional verdict. There is no historically documented universal chart assigning every rune a permanent “yes” or “no”. Modern readers use several workable systems: one rune, a prewritten three-category scale, upright and reversed positions, or a three-rune layout that exposes conditions. Choose the rule before drawing, record the known facts, and define what would count as “yes”. When the result is neutral, do not keep pulling until the answer becomes comfortable. Ask what condition is missing, take one verifiable step, and return on a date tied to a real event.

Early in my rune practice, I kept a tidy list beside the bag. A few signs meant yes, a few meant no, and the rest were “uncertain”. It felt disciplined until I saw the same decision framed in two different ways: “Should I accept this project?” and “Is this project compatible with my existing workload?” One symbol could not answer both honestly because the criteria were different. The weak point was not the rune. It was the question. I now decide what must be true before I draw anything.

Historical evidence and modern practice are not the same thing

Runes were first of all writing signs. The Historical Museum at the University of Oslo describes the futhark as a runic alphabet and traces its development as a writing system. That matters because a modern yes/no table does not become ancient merely by using old characters.

In chapter X of Tacitus’s Germania, marked pieces cut from a branch are cast on a white cloth and selected three times. An unfavourable result ends consultation on the same matter for that day. Tacitus does not call the marks runes and does not give meanings for individual signs. The passage supports the existence of a historical lot practice and an interesting stop rule. It does not prove a modern futhark-based yes/no method.

Keep three layers separate:

LayerA careful claimA claim the evidence does not support
Historical sourcesrunes functioned as writing; sources describe marked wooden lotsone ancient yes/no chart governed every rune
Later and modern practicereaders create conventions, including reversalsthose conventions are compulsory or universal
Personal methodyou may choose a consistent rule and test it in a journalchanging the rule after the draw to rescue a preferred answer

Define what “yes” means before you ask

“Will I get the job?” hides several questions: whether you will be interviewed, whether an offer will arrive, whether the terms are acceptable, and when any of this may happen. A more testable question is narrower:

  • “Is there enough evidence to submit this application now?”
  • “Does the current situation support asking for a pay review before 30 September?”
  • “Should I accept this project if the workload is capped at ten hours a week?”
  • “Which condition am I ignoring before I decide?”

Write four lines first:

  1. Known facts. What is confirmed by a message, document, conversation or observable behaviour.
  2. The yes criterion. The specific outcome that would support moving forward.
  3. A red line. The condition that makes the answer no regardless of the rune.
  4. A review point. The date or event when new evidence should exist.

A red line outranks a symbol. If a contract contains unacceptable exposure, a relationship is unsafe, or a decision requires medical, legal or financial expertise, runes do not remove the need for evidence and qualified help.

Four ways to work with yes or no runes

1. One rune without reversals

Before drawing, divide the signs into three functional groups rather than “good” and “bad”:

  • supports movement;
  • stops or warns;
  • depends on a condition.

This is simple, but it requires you to accept a neutral answer. Raidho may support movement when the question concerns a route and agreed stages, yet it does not guarantee a successful destination. Isa can describe a pause rather than a permanent no. Perthro may foreground uncertainty that one rune cannot honestly close.

2. One rune with upright and reversed positions

Some readers treat upright as the freer expression of a principle and reversed as obstruction, internal resistance or a distorted route. Not every rune looks different when turned, and there is no single historical rule for reversals. If you use them, decide in advance:

  • which runes you consider reversible;
  • whether reversal means no, delay or a shadow form;
  • how you will treat symmetrical signs;
  • what a sideways rune means in your method.

A reversed rune need not be a final prohibition. Reversed Raidho, for example, could mean that the route, timing or agreement is disordered, not that movement is impossible forever.

3. A personal chart tested by a journal

A personal scale can be useful only when the rule is written before the reading, applied consistently, and checked against outcomes. Record the exact question, criterion, rune, original interpretation and real event. Do not turn a failed “no” into “yes, but later” after the fact.

4. Three runes instead of a binary verdict

Three runes are better when the stakes are high, several conditions interact, or useful ambiguity matters more than certainty.

PositionQuestionPractical output
1. SupportWhat can I genuinely rely on?a resource or confirmed advantage
2. ObstacleWhat makes yes risky?a limit, cost or missing fact
3. ConditionWhat must change?a next step and test criterion

This layout does not choose for you. It shows why the answer is conditional.

How to read a neutral or conditional answer

A neutral rune is not a failed reading. It may show that:

  • the question is too broad;
  • the outcome depends on another person or a formal process;
  • important information is missing;
  • both options carry comparable costs;
  • the event is not yet at a stage where yes/no helps;
  • a condition matters more than a predicted result.

Replace “the runes said nothing” with a testable statement:

The answer is currently undetermined because condition X is unconfirmed. Before date Y, I will take action Z and check fact N.

The rune does not support an unconditional yes. The decision is acceptable only if boundary X is respected.

This is not a permanent no; it is a pause until evidence Y exists.

These sentences are less dramatic than prophecy and much more useful.

Ask the mandatory condition question

After any rune, do not immediately draw another. Write: “Under what conditions would this interpretation be true?”

If Fehu appears in a purchase question, the condition may be a real budget rather than an image of prosperity. If Gebo appears for a collaboration, test reciprocity: contribution, responsibility, exit rights and payment. If Tiwaz appears, clarify the goal, authority and price of conflict. If Isa appears, identify the frozen procedure and who can restart it.

A condition brings the symbol into observable life. It may be uncomfortable. Sometimes the best answer is: “Yes, if the deadline is confirmed in writing,” or “No, while there is no three-month reserve.”

The stop rule

Set the stop rule before you begin:

  • one question gets one draw or one preselected spread;
  • repeat only after a new fact or the scheduled review point;
  • do not rephrase while keeping the same hidden question;
  • do not add clarifiers until a wanted yes appears;
  • when anxiety is high, pause and return to the factual record.

Tacitus’s account is useful here not as proof of modern rune reading, but as a reminder that an unfavourable lot was not immediately retested that day. The contemporary reason is straightforward: repeated draws quickly become a way to regulate distress rather than investigate a decision.

A complete composite example

Consider a composite case. Maya has been invited to join a small side project. She likes the subject, but the pay is vague, the workload has no ceiling, and her main employment contract restricts some outside work. “Should I say yes?” is too wide.

She records the facts:

  • there is a verbal invitation but no written agreement;
  • “a few hours” has not been defined;
  • pay depends on results, with no formula;
  • she must answer within five days;
  • her red line is no written approval and no weekly hour cap.

She chooses three runes:

  1. Gebo — support. The collaboration could be reciprocal if exchange and expectations are explicit.
  2. Nauthiz — obstacle. Time and contractual limits cannot be wished away; helpfulness may create overcommitment.
  3. Ansuz — condition. Precise questions and written language are required.

Interpretation one: a conditional yes

Maya can accept if the parties put payment, tasks, maximum hours and the right to refuse extra work in writing before the checkpoint. The criterion is a document she understands and can honour without breaching her main contract.

Interpretation two: not yet, possibly no

Nauthiz may outweigh Gebo. The attraction of partnership is masking a genuine lack of capacity. Ansuz may then indicate a clear refusal rather than negotiation toward a deal. Evasion when Maya asks for specifics would support this line.

How does she choose? Not by selecting the nicer story. She sends four questions and checks again in three days. Concrete answers that survive contractual review preserve the conditional yes. More promises without terms trigger the red line and make the answer no.

A decision tree after one rune

  • The rune supports movement and facts do not breach a red line → take one small reversible step.
  • The rune warns and evidence confirms the risk → stop or obtain specialist advice.
  • The rune is neutral → name the missing condition; do not pull a replacement.
  • The decision depends on several parties → use three positions rather than force a binary scale.
  • You want to ask again → check whether anything real has changed. If not, the stop rule applies.

Common mistakes

Inventing the table after seeing the rune. That is rule-fitting, not interpretation.

Treating every pleasant-looking rune as yes. A principle changes with the question, price and context.

Making every reversal a permanent no. It may indicate delay, resistance or a poorly chosen route.

Asking for another person’s private thoughts. Replace “Does he love me?” with observable signals, your needs, boundaries and a conversation.

Using runes instead of a contract, doctor or calculation. Symbols cannot verify legal terms, diagnose illness or establish financial resilience.

Recording only hits. A mismatch is information about the method, not an invitation to rewrite the original answer.

Questions people ask

Which runes mean yes?

There is no universal historically verified list. Modern systems often classify some signs as supportive, but the meaning depends on the question and the rule selected beforehand.

What should I do with a neutral rune?

Do not draw a replacement. Name the missing fact or condition, choose an action and set a review point.

Is a reversed rune automatically no?

Only if that was your stated method before the draw. A richer reading may treat reversal as blockage, delay or shadow expression and test the context.

When are three runes better?

When the decision is costly, hard to reverse, dependent on several conditions, or one rune produces a hypothesis too broad to act on.

When may I repeat the question?

After a new event or the review date. Repetition without new evidence usually increases noise.

Finish with an action, criterion and review date

Complete one record:

  • My question: one precise fork.
  • Known facts: no guesses.
  • Original interpretation: before clarifiers.
  • Condition: what must be confirmed.
  • Small action: one reversible step.
  • Criterion: an observable outcome.
  • Review point: a date or real event.

Sources for the historical section

In Reflecta, you can save the exact question, original interpretation, condition and review point, then add the real outcome later. That record prevents a quiet rewrite of the answer. For me, a good yes-or-no reading is not a loud promise. It is the moment a person can see the boundary clearly: what is known, what remains unknown, and which next step actually belongs to them.

— Nora Vale, Official Rune Reader at Reflecta

Important

This material is intended for learning and self-reflection. It does not promise to predict the future and does not replace professional help.

Continue in practice

Explore your situation in Reflecta

Choose Tarot, Runes or metaphorical cards, save a useful result and return to it after real events.

Start practice