Elder Futhark rune research is documented by recording each search term, filter, and inspected field you use in the Rune Meanings catalogue, not by copying the meaning itself as a final answer. A good documentation log captures what you typed into the search box, which of the three aett groups you filtered to, the Unicode code point of the row you opened, the transliteration you saw, the reconstructed literal gloss, and the uncertainty note attached to that specific entry. Because the catalogue runs entirely in browser memory and never stores queries, resets do not save anything for later, and there is no account or fetch call that would archive your activity. Your documentation must therefore live outside the tool: a notebook, a spreadsheet, or a plain text file where you re-enter each step by hand while the page is open. Recording the workflow this way preserves the distinction between Unicode encoding facts and scholarly reconstruction, and it gives you a reproducible record you can compare across sessions. The result is a working log of how you actually use the catalogue rather than a single static list of rune keywords.
What "documenting your steps" means for a historical catalogue
When you study Elder Futhark, documenting your steps means keeping a written or typed record of the exact moves you made inside the Rune Meanings catalogue: the query you typed, the filter you set, the row you selected, and the fields you read on that row. It does not mean copying a single keyword from the page and treating it as your final answer. The catalogue is a historical-language reference, so what you write down is partly a Unicode encoding fact, partly a scholarly reconstruction, and partly an explicit uncertainty note. A documentation log should preserve all three layers so that months later you can still tell which sentences in your notes were sourced from the catalogue and which were commentary of your own.
Searches and aett filters run entirely in browser memory, and the page never writes to localStorage, sessionStorage, or any external endpoint. There is no query history to scroll back through. If you refresh the browser, your working state is gone. That constraint is the reason for taking notes by hand: the catalogue treats your session as ephemeral by design, and the only persistent copy of your research workflow is the one you keep outside the page.
Fields the Rune Meanings catalogue exposes for logging
Every row in the 24-entry catalogue shows the same set of fields, and each one is worth writing into a log because each one answers a different kind of question. The Unicode code point (for example U+16A0 for the first row) is an encoding fact that does not change. The standard Unicode name is also an encoding label rather than a translation. The transliteration is a conventional phonetic spelling, and the literal name gloss is a reconstructed label that scholars have inferred from later Germanic rune-name traditions. The aett group and position tell you where the entry sits in the conventional three-by-eight sequence. The uncertainty note records, in plain English, where scholars disagree about that specific row.
Capturing all of these fields turns your notes from a list of meanings into a structured record. A simple two-column entry, "field" on the left and "what I saw on this row" on the right, works well for a single session. For longer projects, a spreadsheet with one row per rune and one column per field lets you filter and sort without retyping.
| Field | What to log | Source status |
|---|---|---|
| Code point | U+16XX value exactly as displayed | Unicode encoding fact |
| Standard Unicode name | Verbatim uppercase name from the row | Unicode encoding label, not a translation |
| Transliteration | Conventional phonetic form | Varies by scholarly convention |
| Literal name gloss | Reconstructed common label such as cattle, gift, hail | Scholarly reconstruction, not contemporary |
| Aett group and position | First, second, or third aett and position 1–8 | Conventional grouping of 24 into three groups of eight |
| Uncertainty note | Plain-English qualifier attached to that row | Recorded per row, e.g. Perthro, Algiz, Kenaz |
The point of this table is not to compute anything; it is to fix a uniform template so that every rune entry in your log carries the same six fields and the same source-status labels. When you compare two entries later, the labels let you see whether a difference is in encoding, in transliteration convention, or in scholarly reconstruction.
Recording each lookup with the Rune Meanings catalogue
The actual mechanics of building a log are short and repeatable. The Rune Meanings page is designed so that every action produces a visible state you can write down. Use the following sequence as a template for each entry you record:
- Write the date and the goal of the session at the top of your log, for example "lookup all entries in the third aett" or "compare transliteration conventions for Algiz."
- In the search box, type a query that matches one of the documented fields: the rune character itself, the common name, the Unicode code point, the transliteration, or the literal gloss.
- If you want to narrow the list, open the aett selector and choose first, second, or third; record which one you selected and why.
- Pick a matching row from the filtered list and record every field on that row exactly as it appears: code point, Unicode name, transliteration, aett, position, literal gloss, and uncertainty note.
- Repeat from step 2 for the next rune. If a search returns nothing, write "no match" in the log instead of leaving it blank, so the absence itself becomes a documented result.
- When you finish or want to start over, click the Reset catalogue control and note that the full 24-entry view returned; this confirms that no background state survived.
This sequence captures both the inputs (the search term, the aett choice) and the outputs (the row fields) of a single lookup. Because nothing is stored inside the catalogue, the log is the only place where the order of those inputs and outputs survives a browser refresh.
The three aett groups and how to log them
The catalogue groups the 24 entries into three conventional aett groups of eight. Logging the group along with the position lets you rebuild the sequence from your notes without opening the page. The table below records the conventional structure; the entries themselves are sourced from the Unicode Runic block, while the three-by-eight grouping is the standard scholarly arrangement.
| Aett group | Positions | Code-point range | What to log per entry |
|---|---|---|---|
| First aett | 1–8 | Begins at U+16A0 | All six fields plus position 1–8 |
| Second aett | 1–8 | Middle of the U+16A0–U+16DF range | All six fields plus position 1–8 |
| Third aett | 1–8 | Ends at U+16DF | All six fields plus position 1–8 |
When you log a session filtered to one aett, write down the aett name and the eight positions you visited. Even if you only inspected three of the eight, the empty positions in your notes tell you which ones you skipped, which is itself a piece of documentation.
Keeping reconstruction visibly separate from encoding facts
The single most common documentation error in runic research is treating a literal gloss like "cattle" or "gift" as if it were a translation straight out of an ancient inscription. The catalogue is explicit about this distinction: Unicode names are encoding labels, and the literal glosses are scholarly reconstructions informed by later Germanic rune-name traditions. Your log should preserve that distinction in its own formatting. One practical convention is to put encoding facts (code point, Unicode name) in plain text and reconstruction fields (literal gloss, transliteration) in italics, with a short comment column reserved for your own reading.
Several entries in the catalogue have explicit uncertainty notes, and those notes deserve the same treatment. Perthro has no broadly agreed literal gloss. Algiz has disputed name, sound history, and meaning, with the common elk comparison marked as qualified. Kenaz or Kauna is shown with the qualified "boil" or "ulcer" gloss used by the selected independent table. Eihwaz, Laguz or Laukaz, and several reconstructed vocalizations vary by scholarly convention. If your log simply lists the gloss without recording the qualifier, you will lose the disagreement. The fix is mechanical: copy the uncertainty note into your log verbatim, on the same row as the gloss it qualifies.
For readers who want a deeper source-criticism pass on the reconstruction-versus-encoding line, the guide on whether Elder Futhark rune meanings are ancient definitions pairs naturally with a documentation log: it covers the historical argument, while your log records what you actually saw on the page.
Anchoring your documentation to primary runic references
Because the catalogue itself sits between two kinds of sources, Unicode's encoding authority and scholarly reconstruction, a useful log always notes which authority each field came from. A practical pattern is a small "source" column at the end of every rune row: encoding fields sourced from the Unicode Runic block are tagged with the code-point authority, while reconstructed fields are tagged with the scholarly tradition you consulted. The catalogue's own context links make this easier: Penn State's institutional reference explains runic script families, phonetic function, Unicode encoding, and the way missing fonts display as boxes, while the Elder Futhark article documents the standard 24-rune table and the limits of reconstructed early names. Adding these two anchors to your log's preface turns your notes into something a future reader can audit.
A final documentation habit is to record what the catalogue explicitly does not do. It does not assign modern spiritual keywords, draw a rune, calculate a reading, diagnose personality, forecast an outcome, or claim supernatural accuracy. It does not search online dictionaries or send your query to a server. Writing those limits into your log at the start of a project is not defensive boilerplate; it is a way to make sure that when you return to your notes, you still know which questions the catalogue is designed to answer and which ones it deliberately leaves to other tools.
For a deeper look, see How to Make Sense of an Unclear Rune Reading Meaning.