Why "Rune"?

Symbols that carry meaning.

---

Origin

The name Rune comes from the runic alphabets used by Germanic and Nordic peoples.

A rune is more than a letter.

Historically, the word rune is associated with:

• mystery
• knowledge
• wisdom
• hidden meaning

Runes were symbols used to convey meaning, not merely sounds.

---

Meaning Over Representation

Source code already represents information.

Rune focuses on something different:

meaning.

Just as a rune represents more than a mark on stone, repository understanding is more than lines of code.

Source code explains:

How.

Rune explains:

Why.

---

Repository Understanding

Git stores:

• commits
• branches
• diffs

Rune stores:

• architecture
• relationships
• conventions
• feature maps

Git preserves history.

Rune preserves understanding.

---

Why Not Another Technical Name?

Names like:

• ContextDB
• RepoGraph
• CodeIndex
• SmartContext

describe implementation.

They do not describe purpose.

Rune represents the idea that repositories contain hidden meaning that humans naturally understand but machines often miss.

---

Small Symbols, Large Meaning

Ancient runes were compact symbols that conveyed meaning far beyond their appearance.

Similarly, a small amount of context:

graph.json
feature maps
file summaries
conventions

can often replace thousands of lines of source code.

The goal is not to store more information.

The goal is to store better meaning.

---

Why Not "Runes"?

Git uses the singular:

.git/

not:

.gits/

Likewise:

.rune/

represents one repository understanding layer.

Simple and memorable.

---

Philosophy

A repository contains more than source code.

It contains meaning.

Rune exists to make that meaning explicit and portable.

---

"Git stores history. Rune stores understanding."

Rune Context — Git for repository understanding.