Module 6 — Assembling a runescript (all together)

Course plan → the course overview. Previous → Module 5 — The "conduit" stance. The climax: we combine the components of modules 1–5 into a full loop.

Why this module

Now you have all the parts: runes (M1), state (M3), intention-as-program (M4), the "conduit" stance (M5). Here you assemble your first full runescript across 6 steps and carry it into life through a wearable cue.

After this module you: have assembled, activated, and are carrying a working runescript for a real, difficult goal.

What a runescript is (a working definition)

A runescript = an if-then plan + a specific difficult goal + expectation → action → outcome, where the rune(s) are a presence you address — and underneath, a symbolic anchor for your attention — and the ritual (galdr/stadha) is the call to the rune and the engine of state.

This is NOT "magic letters instead of work." Full theory → the runescript overview; protocol → how to build a runescript; techniques → Thorsson's catalog of techniques.

The 6 assembly steps

1. Intention (mental contrasting, WOOP + if-then) — from M4: goal × obstacle × if-then plan. (the program text)
2. Rune — choice and addressing — from M1/M2: pick 1–3 runes for the goal and for overcoming the obstacle, build them into a mini-narrative, fold them into a bindrune (a shared stave); address the chosen runes as a presence (acquaintance/call — M2). (your choice + why + the first addressing)
3. State + addressing — from M3: breath + posture/stadha + galdr of the runes' names (the call to the rune, addressed by name), speaking the intention and the if-then plan on the exhale (3–5 min).
4. The "conduit" stance — from M5: external focus + letting go of the outcome. "I do the step, I let the outcome go."
5. ACTION ⭐ — carry a taufr talisman (the bindrune on a token) in view in the zone of action; when the if-then cue fires — perform the planned action.
6. Evaluation — record the outcome in the journal (the detailed cycle is in Module 7).

Module practice — assemble your first runescript

1. Take a real, difficult goal (the same one from M4) and go through the 6 steps, writing everything in the journal.
2. Make a physical talisman: draw/carve the bindrune on a token (wood/paper/metal), optionally in red (the color is a revival convention, for engagement, not "power").
3. Activate it (steps 3–4) and place it in view in the zone of action (desk/phone/wallet).
4. Then — act on the if-then plan.

Assembly example (procrastination on a project): ᚢ Uruz → ᚾ Naudhiz → ᛏ Tiwaz = "endurance → will through resistance → carry it through to the result"; the bindrune on a token; galdr + the if-then "after dinner → a 25-min timer." Spelled out in how to build a runescript.

Anti-patterns (keep in mind)

• "Magic instead of action" — you carved the rune and you wait. → Step 5 (action) is mandatory.
• Visualizing only the outcome → ↓ effort. → A full WOOP with the obstacle (M4).
• Forcing/clutching → tension. → The "conduit" stance (M5).
• Taking a layer-2 (esoteric) meaning for an ancient fact → layer-2 rune meanings = revival-claim, a chosen association, not attested antiquity. Addressing a rune as a presence is fine — but, honestly: this is practice, not an ancient fact.

The honest boundary (ontology — see the three ontologies of a rune)

• A rune is a presence you address and build a relationship with. What this "presence" is, honestly: in reality — the accumulated collective thought-form of the sign (a charge from generations of practitioners), and the "response" under the hood = attention / expectation / absorption. An autonomous entity behind it is an open question [unverified], not a premise.
• It is NOT a "container of energy" you command (the "energy" ontology, which we reject): you don't "pump in" or "drive" force — you address and listen.
• The talisman is a material focus of the relationship with the rune and an if-then cue; not a "battery" charged with force. You feed it with attention and addressing, not with "energy in an object" ([unverified]).
• The layer-2 (esoteric) meaning = revival-claim, a chosen association, not an ancient fact.
• Without action a runescript is empty — a relationship with a rune ≠ passive waiting (the main anti-pattern).

Readiness checklist (for Module 7)

• I went through all 6 steps and wrote them in the journal.
• I made a talisman with a bindrune and carry it in view.
• I have a working if-then plan tied to a real cue.
• I understand: you address the rune — and underneath, it anchors your attention — but the result comes from action, not from waiting.

Links

how to build a runescript · the runescript overview · Thorsson's catalog of techniques · the Elder Futhark reference. Next → Module 7 — The practice cycle and evaluation.