Module 2 — Relating to a rune

Course plan → the course overview. Previous → Module 1 — Rune literacy. Next → Module 3 — Body and state. Ontological basis → the three ontologies of a rune.

Why this module

In Module 1 you learned a rune "from the outside" — glyph, name, meaning. Here comes the turn: from "knowing about a rune" to "being in a relationship with it." This is the heart of our frame: a rune is not a dead anchor-sign but a presence you address and that answers you.

After this module you: can get acquainted with a rune, address it (a spoken charge + galdr call), receive a response, and feed the relationship with attention — honestly, without self-deception.

What "rune-as-presence" means (honestly)

The three frames are unpacked in the three ontologies of a rune; here we take the third — rune-as-entity/egregore.

• practice-instruction You relate to the rune as something with its own character and voice: you greet it, ask, listen, thank it.
• mechanism-evidence What this "presence" is under the hood: the accumulated collective thought-form of the sign (a charge from generations of practitioners — a real thing, like Durkheim's "power of the flag") + your attention, which gives it a voice (absorption).
• [unverified] Whether a rune exists as an autonomous entity outside your attention and the collective charge is an open question. We practice "as-if," without passing it off as fact.

A stance of addressing, not commanding. The key difference from "energy": you don't "pump force" out of the rune and don't command it — you address and listen. The same letting-go stance as in Module 5 — The "conduit" stance.

Four steps of the relationship

1. Acquaintance (after Diana Paxson, Taking Up the Runes — revival-claim). Sit with one rune. Draw it, keep it in view, chant the name (galdr). Stay with it silently for 5–10 min: what image, feeling, "character" arrives? Write it in the journal — without judging "right/wrong." This is not "receiving secret knowledge" but building a personal bond (your associations = your working language with the rune).

2. Addressing (spoken charge + call).

• Spoken charge (ogovor, a Russian-tradition practice, ethnographic-data) — say aloud whom you're calling and why, as an address/request, not a command: "[Rune name], be with me in [matter]; I ask for [what]."
• Galdr call — vibrate the rune's name (3–9 times). Galdr here is not only state-tuning (M3) but a call by name (Paxson: "call the rune").
• Offering (optional, ethnographic-data/revival-claim) — a symbolic gesture of thanks (a candle, a word, water). The pact is two-way: attention and gratitude ↔ presence.

3. Listening for the response.

• After the call — wait quietly, don't force it. The response arrives as an image, a word, a bodily feeling, a "knowing," a turn of attention.
• mechanism-evidence Honestly: the "response" is absorption + intuition + drift of interpretation (see the three ontologies of a rune). This does not devalue it as a working tool — it explains where it comes from, without a supernatural assumption.
• Write the response in the journal. ⚠️ Distinguish "the response" from "what I wanted to hear" — the log guards against wishful reading.

4. Feeding with attention. Relationships grow with regularity (Paxson: "the longer you work with the runes, the easier each becomes"). Return to "your" rune daily — a short call, a couple of words, an entry. A presence lives exactly as long as you feed it with attention (Tomberg/Ambelain on the egregore — revival-claim).

Honest belief and the shadow side

• Invest fully while holding the question open (the pact from Module 0 — Orientation and the honesty pact): to address a rune as a living presence is a working "as-if" stance, not self-deception. Belief = fuel.
• ⚠️ The shadow caveat. A relationship with a "presence" has a shadow: (1) don't hand your will over to it — "the creator becomes a slave to what it created" (Tomberg); the presence serves you, not the reverse; (2) don't slide into passive waiting — addressing ≠ "the rune will do it"; the action remains (M6); (3) keep feedback — the log, not closed eyes.

The historical / revival boundary (don't mix layers)

• historical-fact Some runes are named after gods/beings: Tiwaz → the god Týr, Ingwaz → Ing(-Freyr), þurs → giant; Odin won the runes (Hávamál, Rúnatal 138–139). "Addressing the rune Týr" has a real historical anchor — to the god the rune is named after.
• revival-claim / practice-instruction But "every rune is an autonomous spirit-interlocutor that answers" is not in the primary sources; it is a modern practice (Thorsson, Paxson). Addressing a rune, honestly, is practice, not an ancient fact.

Module practice

1. Choose one working rune (for a current goal from M1).
2. For a week: daily acquaintance/call (steps 1–3), 5–10 min, write the response in the journal.
3. At the end of the week reread your notes: what "character" has the rune taken on? what was a response, and what was your wish?

Readiness checklist (for Module 3)

• I made acquaintance with at least one rune (the journal exists).
• I can address a rune (spoken charge + galdr call) as a presence, not as a "battery."
• I distinguish "the response" from "what I wanted to hear"; I write both in the log.
• I understand: a presence is real as a thought-form + as-if; an autonomous entity = an open question; "rune-spirit" = revival, not antiquity.

Links

the three ontologies of a rune · Module 0 — Orientation and the honesty pact · Module 5 — The "conduit" stance · Thorsson's catalog of techniques · the Elder Futhark reference. Next → Module 3 — Body and state.