Filename: GLOSSARY.md
Scope: Entire RuneForgeAI / Mythic Engineering project ecosystem
Purpose: This document maps Norse, Germanic, Pagan, mythological, magical, historical, and Mythic Engineering terminology used throughout the project ecosystem to its technical meanings.
It is intentionally not tied to any single repository.
A mythological term may appear in multiple projects and may represent different technical concepts in each one. Therefore, this glossary distinguishes between:
- the historical or mythological meaning of a term,
- its general Mythic Engineering interpretation,
- and its specific implementation within individual projects.
Agents, developers, contributors, documentation systems, and AI coding assistants unfamiliar with Norse mythology or the project's naming conventions should consult this document before assuming the purpose of any mythologically named component, module, protocol, subsystem, service, variable, class, function, repository, daemon, agent, database, or architectural layer.
Never infer a component's technical function solely from its mythological name.
Mythological symbolism explains why a name may have been chosen.
The source code and project documentation determine what the component actually does.
If a term is encountered that is not documented here:
- locate its implementation,
- determine its actual technical role,
- identify the mythological or historical source of the name,
- document both,
- mark the mapping according to its verification status.
A mythologically elegant guess is still a guess.
An unknown mapping clearly marked as unknown is preferable to fictional documentation.
- How To Use This Glossary
- Ecosystem-Wide Naming Model
- Verification Levels
- Project Mapping Rules
- The Æsir, Vanir, Gods, and Divine Figures
- Runes and the Elder Futhark
- Objects, Weapons, and Mythic Artifacts
- Places and Cosmic Geography
- Beings and Creatures
- Concepts, Forces, and Metaphysics
- Structural and Sacred Terminology
- Mythic Engineering Architectural Vocabulary
- Cross-Project Name Reuse
- Confirmation Tracker
- Repository Population Procedure
- Automated Glossary Discovery
- Etymology Quick Reference
- Naming New Components
- Amendment Protocol
- Documentation Integrity Rules
- Final Principle
Each mythological entry should contain the following fields.
The preferred spelling of the mythological term.
ASCII forms, Anglicized forms, transliterations, historical variants, and spellings likely to occur in source code.
What the name actually refers to in Norse, Germanic, historical, magical, or related tradition.
The conceptual or symbolic technical associations suggested by the mythology.
This field explains the naming logic.
It does not prove implementation.
Actual technical implementations confirmed through source code or authoritative project documentation.
Example:
| Project | Technical Meaning | Status |
|---|---|---|
| Project A.E.S.I.R. | HTTP gateway | CONFIRMED |
| Another Project | Distributed transport | CONFIRMED |
| Third Project | Unknown | UNMAPPED |
Repositories, directories, modules, specifications, protocols, documentation, services, agents, or APIs known to use the term.
Ambiguities, spelling issues, naming collisions, architectural relationships, and anything else future maintainers should know.
The project ecosystem uses mythology as a semantic architectural language.
Names are not merely decorative.
A well-chosen mythological name can communicate:
- responsibility,
- relationships,
- lifecycle,
- authority,
- information flow,
- trust boundaries,
- persistence,
- memory,
- transformation,
- communication,
- observation,
- prediction,
- protection,
- orchestration,
- execution,
- resilience,
- and failure behavior.
For example:
- Bifröst naturally suggests a bridge between domains.
- Heimdallr suggests observation or guarding.
- Mímir suggests knowledge and consultation.
- Muninn suggests memory.
- Huginn suggests thought, research, or reasoning.
- Yggdrasill suggests a structure connecting multiple worlds or systems.
- Norns suggest state transitions, causality, time, or scheduling.
- Gleipnir suggests containment.
- Gjallarhorn suggests system-wide alerts.
- Sleipnir suggests rapid transportation between domains.
These correspondences make the ecosystem easier to reason about.
But mythology remains a semantic layer over engineering reality.
Source remains authoritative.
Every technical mapping should carry one of the following statuses.
| Status | Meaning |
|---|---|
| CONFIRMED-SOURCE | Verified directly from implementation |
| CONFIRMED-DOCS | Explicitly defined by authoritative project documentation |
| CONFIRMED-BOTH | Verified from both source and documentation |
| PROVISIONAL | Strong evidence exists, but verification is incomplete |
| HYPOTHESIS | Mythology suggests a possible role, but implementation has not been verified |
| UNMAPPED | Name is known, but technical meaning is unknown |
| RESERVED | Name is intentionally reserved for possible future use |
| HISTORICAL | Mapping existed previously but is no longer active |
| DEPRECATED | Component still exists but should not be used for new development |
| CONFLICT | Multiple sources disagree about the mapping |
Do not silently upgrade a HYPOTHESIS to CONFIRMED.
The mythological identity of Mímir does not change between repositories.
A project may use Mímir for:
- RAG,
- knowledge storage,
- validation,
- retrieval,
- advisory reasoning,
- or another related function.
Each project mapping must therefore be documented independently.
If several projects intentionally use the same mythological name for the same architectural function, the mapping may eventually become an ecosystem convention.
Example:
Bifröst → boundary-crossing transport
could become a general architectural convention even if one implementation is HTTP and another is RPC.
Two projects using Yggdrasill-related terminology do not necessarily share an implementation.
If an entire project is named after a mythological entity, distinguish:
Yggdrasill — mythological concept
from:
Yggdrasil Distributed Inference System — software project
Where possible, refer to components as:
PROJECT::COMPONENT
Examples:
AESIR::BifrostGate
WYRD::Verdandi
MUNINN::MemoryStore
This prevents mythological naming collisions from becoming architectural confusion.
Aesir, Æsir, aesir
The Æsir are one of the principal families of gods in Norse mythology, including Odin, Thor, Tyr, Baldr, Frigg, and others.
They are strongly associated with sovereignty, warfare, protection, wisdom, social order, and cosmic governance.
Possible architectural themes include:
- orchestration,
- governance,
- primary runtime systems,
- coordination,
- high-level execution,
- system authority.
| Project | Technical Meaning | Status |
|---|---|---|
| Project A.E.S.I.R. | Umbrella name for the bare-metal/local AI inference engine and surrounding runtime architecture | CONFIRMED-DOCS |
Do not assume every occurrence of aesir refers specifically to Project A.E.S.I.R.
The word may also be used generically in documentation describing Norse mythology.
Bragi is associated with poetry, eloquence, wisdom, language, and skilled speech.
He is traditionally described as the husband of Iðunn.
Potential semantic associations:
- language generation,
- prose generation,
- response composition,
- formatting,
- speech,
- TTS,
- narration,
- creative writing,
- dialogue generation.
No ecosystem-wide mapping currently confirmed.
UNMAPPED
Eir is associated with healing, medical skill, restoration, and care.
Strong architectural associations include:
- repair,
- self-healing,
- fault recovery,
- retries,
- diagnostics,
- remediation,
- automatic repair agents,
- service recovery,
- health monitoring.
Mappings must be added from individual project source trees.
Eir is an especially strong name for automated repair and recovery systems.
PROVISIONAL
Freya, Freyja
Freyja is a Vanir goddess associated with love, beauty, fertility, wealth, death, war, magic, and seiðr.
She receives part of the battle-slain in Fólkvangr and possesses the necklace Brísingamen.
Possible associations include:
- transformation,
- seiðr-related probability manipulation,
- adaptive systems,
- aesthetic generation,
- magical interfaces,
- high-level intelligence,
- preference systems,
- agent personality systems.
Freyja's mythology is extraordinarily broad.
Technical mappings should therefore never be guessed merely from her attributes.
UNMAPPED
Freyr is a Vanir god associated with fertility, prosperity, peace, abundance, kingship, sunshine, agriculture, and favorable seasons.
He owns the magical ship Skíðblaðnir and the boar Gullinbursti.
Potential associations:
- resource provisioning,
- optimization,
- abundance management,
- infrastructure provisioning,
- capacity planning,
- growth systems,
- environmental adaptation.
UNMAPPED
Heimdall, Heimdallr
Heimdallr guards Bifröst.
He possesses extraordinary sight and hearing and watches for threats to the gods.
He will sound Gjallarhorn at Ragnarök.
One of the strongest semantic mappings in the ecosystem.
Potential roles include:
- monitoring,
- intrusion detection,
- authentication,
- authorization,
- API ingress validation,
- watchdog services,
- observability,
- system health monitoring,
- anomaly detection,
- security gateways.
A system using:
Bifröst → gateway
Heimdallr → gateway guardian
Gjallarhorn → alarm system
forms a particularly coherent mythological architecture.
Project-specific verification required.
Hermod, Hermodr, Hermóðr
Hermóðr rides to Hel after Baldr's death to negotiate for his return.
He functions as a divine messenger and emissary.
Natural associations include:
- message passing,
- inter-process communication,
- RPC,
- event dispatch,
- notifications,
- message buses,
- cross-service communication.
UNMAPPED
Hoenir, Hœnir
Hœnir is associated in surviving Norse literature with deliberation and decision-making and appears prominently in the Æsir-Vanir exchange.
Potential associations:
- decision engines,
- arbitration,
- model selection,
- route selection,
- inference routing,
- policy decisions,
- candidate selection.
UNMAPPED
Idunn, Idun, Iðunn
Iðunn safeguards the apples associated with the gods' continued youth.
Possible associations:
- rejuvenation,
- cache renewal,
- model refresh,
- session renewal,
- lifecycle management,
- dependency updates,
- health maintenance.
UNMAPPED
Mani, Máni
Máni is the personification of the Moon and brother of Sól.
Potential associations:
- scheduled tasks,
- periodic cycles,
- background operations,
- nighttime processing,
- low-power modes,
- temporal systems,
- recurring maintenance.
UNMAPPED
Mimir, Mímir
Mímir is a figure of extraordinary wisdom and knowledge.
Mímisbrunnr, the Well of Mímir, is associated with wisdom beneath Yggdrasill.
Odin sacrifices an eye for access to its wisdom.
Strong associations include:
- knowledge,
- retrieval,
- verification,
- databases,
- RAG,
- reasoning assistance,
- advisory systems,
- epistemic governance.
The broader ecosystem includes:
Mímir-Vörðr
as a knowledge, verification, truth-governance, RAG, or hallucination-control architecture.
Do not automatically equate every component named Mímir with the Mímir-Vörðr project.
CONFIRMED-DOCS for ecosystem concept.
Individual implementations require separate verification.
Odin, Óðinn, Woden, Wotan
Odin is associated with sovereignty, knowledge, poetry, runes, magic, prophecy, war, death, inspiration, sacrifice, and relentless acquisition of wisdom.
Potential high-level uses include:
- primary orchestrator,
- meta-agent,
- supervisory intelligence,
- strategic reasoning,
- global decision systems,
- knowledge acquisition,
- agent coordination.
Because Odin's mythological domain is extremely broad, technical meanings require especially careful verification.
UNMAPPED
Odr, Óðr
Óðr is the wandering husband of Freyja.
The word belongs to a semantic family involving inspiration, poetry, mind, passion, and ecstatic or intensified consciousness.
Possible associations:
- creativity,
- stochastic exploration,
- speculative decoding,
- brainstorming,
- high-temperature inference,
- generative exploration.
UNMAPPED
Sol, Sól, Sunna
Sól is the personification of the Sun.
Possible associations:
- illumination,
- visualization,
- dashboards,
- foreground computation,
- wake states,
- monitoring displays,
- primary output surfaces.
UNMAPPED
Skadi, Skaði
Skaði is associated with mountains, winter, skiing, hunting, independence, and harsh environments.
Potential associations:
- rugged deployment,
- environmental adaptation,
- resource-constrained computation,
- edge systems,
- sparse-resource optimization,
- search/hunting algorithms.
UNMAPPED
Thor, Þórr
Thor is associated with thunder, strength, protection, direct action, and the defense of gods and humans.
Potential associations:
- execution,
- heavy compute,
- protection,
- enforcement,
- high-performance kernels,
- decisive operations,
- workload execution.
UNMAPPED
Tyr, Týr, Tiw
Tyr is associated with law, justice, courage, obligation, oathkeeping, and the binding of Fenrir.
Strong potential associations:
- policy enforcement,
- contracts,
- permissions,
- validation,
- trust,
- cryptographic signing,
- invariants,
- safety constraints.
UNMAPPED
Ullr is associated with archery, hunting, skiing, skill, precision, and single combat.
Potential associations:
- precision execution,
- targeting,
- profiling,
- exact selection,
- single-purpose optimized kernels,
- deterministic inference.
UNMAPPED
Vidar, Vidarr, Víðarr
Víðarr is Odin's silent son and the god who avenges Odin by killing Fenrir during Ragnarök.
He survives the destruction.
Excellent symbolic associations include:
- catastrophic recovery,
- emergency response,
- last-resort execution,
- failsafe systems,
- disaster survival,
- resilient recovery.
UNMAPPED
The Elder Futhark is the oldest major form of the runic alphabet.
It contains 24 runes and was used broadly across Germanic-speaking regions during the early centuries CE.
Within the project ecosystem, runes may function as:
- identifiers,
- configuration flags,
- capability markers,
- protocol symbols,
- state markers,
- feature masks,
- semantic labels,
- security scopes,
- command abbreviations,
- model behaviors,
- symbolic UI elements.
There is no universal technical meaning automatically assigned to a rune.
For example:
ᚨ Ansuz
may control prompt behavior in one system and communication behavior in another.
Each mapping must therefore specify its project.
| Rune | Name | Phonetic | Mythic / Semantic Association | Project-Specific Mapping |
|---|---|---|---|---|
| ᚠ | Fehu | F | wealth, movable resources | Verify per project |
| ᚢ | Uruz | U | strength, vitality | Verify per project |
| ᚦ | Thurisaz | TH | force, giants, thorn | Verify per project |
| ᚨ | Ansuz | A | speech, Odin, communication | Verify per project |
| ᚱ | Raidho | R | journey, movement, order | Verify per project |
| ᚲ | Kenaz | K | torch, illumination, knowledge | Verify per project |
| ᚷ | Gebo | G | gift, exchange, reciprocity | Verify per project |
| ᚹ | Wunjo | W | joy, harmony | Verify per project |
| ᚺ | Hagalaz | H | hail, disruption | Verify per project |
| ᚾ | Nauthiz | N | necessity, constraint | Verify per project |
| ᛁ | Isa | I | ice, stillness | Verify per project |
| ᛃ | Jera | J | year, cycle, harvest | Verify per project |
| ᛇ | Eihwaz | EI | yew, endurance, axis | Verify per project |
| ᛈ | Perthro | P | uncertainty, lot, mystery | Verify per project |
| ᛉ | Algiz | Z | protection | Verify per project |
| ᛋ | Sowilo | S | sun, success, illumination | Verify per project |
| ᛏ | Tiwaz | T | Tyr, law, justice | Verify per project |
| ᛒ | Berkano | B | birch, birth, renewal | Verify per project |
| ᛖ | Ehwaz | E | horse, partnership, movement | Verify per project |
| ᛗ | Mannaz | M | humanity, personhood | Verify per project |
| ᛚ | Laguz | L | water, flow | Verify per project |
| ᛜ | Ingwaz | NG | Ing/Freyr, stored potential | Verify per project |
| ᛟ | Othala | O | inheritance, homeland | Verify per project |
| ᛞ | Dagaz | D | daylight, transformation | Verify per project |
The engine documentation references a full Elder Futhark masking system associated with the Masking Seidr subsystem.
The precise mapping of all 24 runes must be extracted from implementation rather than inferred from rune symbolism.
- Find the rune enum, table, constants, or configuration structure.
- Identify each rune's exact technical behavior.
- Record the repository and source path.
- Record the relevant function, struct, class, protocol, or configuration field.
- Mark the mapping
CONFIRMED-SOURCE. - Do not replace unknown behavior with rune divination meanings.
Bifrost, Bifröst
Bifröst is the bridge connecting Midgard and Asgard.
Heimdallr guards it.
One of the ecosystem's clearest architectural metaphors:
Bifröst = bridge between domains
Possible technical implementations include:
- HTTP gateways,
- APIs,
- RPC,
- network bridges,
- adapters,
- protocol translators,
- IPC,
- service boundaries,
- device-to-device communication.
| Project | Mapping | Status |
|---|---|---|
| Project A.E.S.I.R. | BifrostGate, bare-metal HTTP/API bridge between external callers and inference engine |
CONFIRMED-DOCS |
Bifröst should generally be preferred for crossing a meaningful architectural boundary.
Brísingamen is Freyja's famous necklace.
Possible associations:
- valuable shared resources,
- cryptographic keys,
- premium capabilities,
- capability tokens,
- negotiated exchange,
- identity artifacts.
RESERVED / UNMAPPED
Draupnir is Odin's ring.
Every ninth night it produces eight rings of equal weight.
Excellent associations include:
- replication,
- spawning,
- cloning,
- autoscaling,
- worker creation,
- batch expansion,
- recursive generation.
UNMAPPED
Heimdallr's horn, whose sounding announces Ragnarök.
Strong architectural uses:
- critical alerting,
- emergency broadcast,
- fatal event propagation,
- global notifications,
- shutdown warnings,
- incident alarms.
Heimdallr detects.
Gjallarhorn announces.
UNMAPPED
The magical fetter created to bind Fenrir.
It succeeds where ordinary chains fail.
One of the strongest possible names for:
- sandboxing,
- resource constraints,
- capability limits,
- process containment,
- runaway-agent controls,
- quota enforcement,
- isolation,
- safety boundaries.
UNMAPPED
Gram is the sword used by Sigurd to kill Fáfnir.
Potential associations:
- surgical operations,
- process termination,
- decisive optimization,
- exact modification,
- targeted tooling.
UNMAPPED
Odin's spear is famous for striking its intended target and carries strong oath-related symbolism.
Potential associations:
- deterministic targeting,
- exact routing,
- commit enforcement,
- signing,
- precision dispatch,
- immutable commands.
UNMAPPED
Megingjord, Megingjörð
Thor's belt of strength.
Potential associations:
- acceleration,
- turbo modes,
- compute amplification,
- hardware offload,
- parallelism,
- optimized execution profiles.
UNMAPPED
Mjolnir, Mjölnir
Thor's hammer.
It is simultaneously a weapon, protective object, and instrument of sanctification.
Excellent associations include:
- core execution kernels,
- high-power compute operations,
- build systems,
- deployment execution,
- protection,
- enforcement.
UNMAPPED
Skidbladnir, Skíðblaðnir
Freyr's magical ship can carry the gods yet be folded small enough to carry.
Particularly suitable for:
- portable deployments,
- compact distributions,
- edge packaging,
- self-contained binaries,
- portable runtime bundles,
- hardware-independent deployment packages.
This symbolism fits especially well with the ecosystem's emphasis on:
- local-first computing,
- edge AI,
- small systems,
- portable hardware,
- nomadic computing,
- Raspberry Pi,
- laptops,
- heterogeneous devices.
UNMAPPED
Asgard, Asgarðr, Ásgarðr
The fortified world associated with the Æsir.
Potential architectural meaning:
- privileged runtime,
- trusted compute zone,
- control plane,
- protected core,
- internal services.
Project A.E.S.I.R. documentation conceptually associates Asgard with the protected inference-engine interior reached through Bifröst.
PROVISIONAL / DOCUMENTED CONCEPT
Midgard, Midgardr, Miðgarðr
The human world or "middle enclosure."
Possible uses:
- user-facing environment,
- external clients,
- ordinary application space,
- public API domain,
- caller environment.
Miðgarðr → external world
Bifröst → bridge
Heimdallr → guardian
Ásgarðr → privileged world
This forms a coherent trust-boundary metaphor.
Utgard, Utgardr, Útgarðr
Literally the outer enclosure.
The term is strongly associated with what lies beyond the ordered inner world.
Potential uses:
- untrusted input,
- external networks,
- quarantine zones,
- adversarial environments,
- unknown devices,
- third-party systems.
UNMAPPED
Valhalla, Valholl, Valhöll
Odin's hall of the battle-slain.
Possible uses include:
- worker pools,
- archives,
- completed jobs,
- restartable agents,
- task staging,
- preserved processes.
UNMAPPED
Yggdrasil, Yggdrasill
The World Tree structures and connects the cosmological worlds.
Extremely strong associations include:
- distributed systems,
- network topology,
- hierarchical infrastructure,
- multi-node orchestration,
- graph systems,
- federation,
- inter-device computation.
The ecosystem contains the:
Yggdrasil Distributed Inference System
which uses the World Tree metaphor for distributed AI/inference architecture.
Do not assume an internal component called Yggdrasil is identical to the separate distributed-inference project.
Use repository-qualified names.
The chosen slain gathered for Ragnarök.
Potential associations:
- worker pools,
- reusable agents,
- respawning processes,
- disposable execution workers,
- distributed compute workers.
UNMAPPED
The great wolf destined to kill Odin at Ragnarök.
The gods bind him using Gleipnir.
Potential associations:
- runaway processes,
- uncontrolled workloads,
- adversarial stress tests,
- catastrophic load,
- dangerous capabilities,
- intentionally destructive testing.
Fenrir → dangerous force
Gleipnir → engineered containment
UNMAPPED
Fafnir, Fáfnir
Fáfnir becomes a dragon while guarding his treasure and is killed by Sigurd.
Possible uses:
- guarded resource stores,
- adversarial resource hoarding,
- bottleneck detection,
- high-value protected data,
- intentionally hostile test targets.
UNMAPPED
Hugin, Huginn
One of Odin's two ravens.
The name is associated with thought.
Huginn and Muninn travel through the worlds and bring information back to Odin.
Very strong candidate for:
- research agents,
- information gathering,
- external search,
- reasoning,
- exploration,
- scouting,
- observation.
Huginn → thought / research / information acquisition
Jormungandr, Jörmungandr
The World Serpent encircles Midgard.
Potential associations:
- ring buffers,
- circular queues,
- recursive systems,
- wraparound contexts,
- enclosing network layers,
- feedback loops.
UNMAPPED
Munin, Muninn
Odin's second raven.
The name is associated with memory or remembrance.
One of the most direct symbolic mappings available:
- persistent memory,
- episodic memory,
- long-term storage,
- recall,
- memory databases,
- knowledge persistence.
Muninn → memory
This mapping should normally be reused consistently unless a project has a compelling reason otherwise.
Nidhogg, Nidhoggr, Níðhöggr
Níðhöggr gnaws at the roots of Yggdrasill.
Potential associations:
- corruption detection,
- fuzzing,
- memory leaks,
- structural integrity testing,
- dependency erosion,
- destructive testing,
- fault injection.
UNMAPPED
Odin's eight-legged horse travels with exceptional speed and can move between worlds.
Excellent associations include:
- fast transport,
- RPC,
- high-speed I/O,
- multi-channel communications,
- cross-node messaging,
- heterogeneous transport.
UNMAPPED
Valkyries
The Valkyries choose the slain and bring selected warriors to Odin.
Potential associations:
- selection algorithms,
- candidate ranking,
- admission control,
- scheduler selection,
- top-k processing,
- model selection,
- task assignment.
UNMAPPED
Seidr, Seiðr
Seiðr is a complex category of Norse magical practice associated particularly with Freyja and Odin.
It includes traditions involving prophecy, influence, altered states, fate, perception, healing, harmful magic, and other magical operations.
Seiðr is particularly appropriate for systems that:
- transform probability,
- manipulate model behavior,
- influence outcomes,
- perform adaptive inference,
- alter state,
- apply hidden or indirect transformations.
| Project | Mapping | Status |
|---|---|---|
| Project A.E.S.I.R. | Masking Seidr, a logit-masking system shaping model output probabilities |
CONFIRMED-DOCS |
The metaphor is especially strong:
mythic seiðr → manipulation of possibility
Masking Seidr → manipulation of token probability
Orlog, Örlög, Ørlög, Örlǫg
Örlǫg can be understood as deep causal layers, inherited conditions, or foundational circumstances contributing to how events unfold.
Potential associations:
- historical state,
- persistent causality,
- foundational parameters,
- initial conditions,
- inherited configuration,
- long-term state,
- agent history.
The ecosystem contains an Ørlög system associated with temporal, biological, emotional, or persistent AI-companion state modeling.
Exact implementation should be documented from that project's authoritative source.
CONFIRMED-DOCS / PROJECT-SPECIFIC DETAILS REQUIRED
Vordr, Vörðr
A guardian, watcher, ward, or protective presence.
Natural technical meanings include:
- guardian,
- validator,
- monitor,
- security service,
- truth checking,
- oversight,
- quality control.
Mímir-Vörðr
uses the guardian concept in a knowledge-verification context.
Wyrd
Wyrd concerns the unfolding of events through accumulated causes, relationships, actions, circumstances, and fate.
Potential technical meanings include:
- world state,
- causal state,
- deterministic systems,
- event history,
- entity relationships,
- simulation,
- reality modeling.
The ecosystem contains:
WYRD Protocol
as a world-modeling / entity-component / structured-reality architecture.
Do not treat every lowercase use of wyrd as a reference to the formal WYRD Protocol.
Urd, Urðr
One of the three major Norns.
Urðr is commonly associated with what has become or the accumulated past.
Strong associations:
- historical state,
- immutable event logs,
- past events,
- provenance,
- audit records.
Verdandi, Verðandi
One of the Norns.
Her name is associated with becoming or what is presently coming into being.
Excellent association:
- event buses,
- live state transitions,
- present events,
- streaming updates,
- reactive systems.
VERÐANDI appears in the broader Mythic Engineering architecture as an event-oriented concept.
Where implemented, repository-specific behavior must be documented.
One of the Norns.
The name concerns what shall be, obligation, debt, or what is yet to occur.
Extremely strong associations include:
- task queues,
- future work,
- schedulers,
- TODO ledgers,
- planned operations,
- dependency tracking.
The broader architecture includes a Skuld task ledger concept.
A hof is associated with a temple, sanctuary, or cultic building.
Potential uses:
- namespace,
- project root,
- service container,
- top-level subsystem,
- trusted environment.
UNMAPPED
A vé is a sacred or consecrated space.
Vé is also the name of one of Odin's brothers in Norse cosmogony.
Possible technical meanings:
- isolated scope,
- trusted execution area,
- protected configuration,
- initialization boundary,
- sandbox.
UNMAPPED
A hall is both an architectural and social center throughout Norse literary and archaeological contexts.
Potential uses:
- registry,
- collection,
- worker pool,
- service grouping,
- shared namespace,
- aggregation point.
Well or spring.
Especially appropriate for:
- databases,
- knowledge sources,
- repositories,
- retrieval stores,
- memory stores.
Enclosure, yard, protected boundary.
Especially suitable for:
- security boundaries,
- namespaces,
- containers,
- execution domains,
- trust zones.
Mythic Engineering permits mythological terminology to become a meaningful architectural language.
A mature ecosystem should allow someone familiar with the naming system to infer relationships without pretending to know implementation details.
For example:
Huginn gathers knowledge.
Muninn remembers it.
Mímir interprets or verifies it.
Vörðr guards it.
Verðandi carries events.
Skuld tracks future work.
Bifröst connects realms.
Heimdallr watches the boundary.
Gjallarhorn broadcasts critical events.
Gleipnir constrains dangerous forces.
Yggdrasill connects systems.
This is not merely aesthetic naming.
It creates a semantic topology.
- Mímir
- Mímisbrunnr
- Huginn
- Muninn
- Muninn
- Urðr
- Örlǫg
- Verðandi
- Hermóðr
- Gjallarhorn
- Skuld
- Norns
- Bifröst
- Sleipnir
- Yggdrasill
- Heimdallr
- Tyr
- Gleipnir
- Vörðr
- Eir
- Víðarr
- Iðunn
- Valkyrjur
- Hœnir
- Thor
- Mjölnir
- Gungnir
- Gram
- Fenrir
- Gleipnir
- Níðhöggr
- Jörmungandr
The ecosystem may intentionally reuse mythological ideas.
This is acceptable.
The glossary must record the distinction.
Example:
| Term | Project A | Project B | Ecosystem Meaning |
|---|---|---|---|
| Bifröst | HTTP API | Node RPC | Boundary-crossing communication |
| Muninn | SQLite memory | Distributed memory | Persistent remembrance |
| Heimdallr | API validator | Node watcher | Observation / guarding |
This is preferable to forcing every project to implement the metaphor identically.
The mythological archetype remains stable while the engineering manifestation changes.
Because this glossary covers the entire ecosystem, confirmation tracking must happen on two levels.
| Category | Purpose |
|---|---|
| Mythology Confirmed | Historical/mythological description reviewed |
| Ecosystem Association Defined | General technical metaphor documented |
| Project Mappings Confirmed | At least one actual implementation verified |
| Fully Audited | All known repository usages documented |
| Project | Mythic Identifiers Found | Confirmed | Provisional | Unmapped | Audit Status |
|---|---|---|---|---|---|
| Project A.E.S.I.R. | TBD | TBD | TBD | TBD | IN PROGRESS |
| Mímir-Vörðr | TBD | TBD | TBD | TBD | NOT AUDITED |
| WYRD Protocol | TBD | TBD | TBD | TBD | NOT AUDITED |
| Yggdrasil Distributed Inference System | TBD | TBD | TBD | TBD | NOT AUDITED |
| Ørlög | TBD | TBD | TBD | TBD | NOT AUDITED |
| Other repositories | TBD | TBD | TBD | TBD | NOT AUDITED |
Add every current and future repository to this table.
Every repository should be audited individually.
Identify all projects in the ecosystem.
Do not assume the glossary already lists them all.
Search the entire repository.
Examples:
find . -type fFor a Mojo project:
find . \( -name "*.mojo" -o -name "*.🔥" \)For Python:
find . -name "*.py"For Rust:
find . -name "*.rs"For C/C++:
find . \( -name "*.c" -o -name "*.cpp" -o -name "*.h" -o -name "*.hpp" \)Never assume mythological terms appear only in executable source.
Also inspect:
README files
architecture documents
configuration
tests
CI files
scripts
schemas
protocol definitions
database names
API routes
CLI commands
environment variables
service units
systemd files
examples
benchmarks
experimental directories
Search names such as:
grep -RniE \
"aesir|odin|thor|tyr|freya|freyja|mimir|muninn|huginn|bifrost|heimdall|wyrd|orlog|verdandi|skuld|yggdrasil|seidr|valkyr|fenrir|gleipnir|mjolnir|gungnir" \
.Expand this search whenever new terminology is discovered.
For every match determine:
What code executes?
What data does it manage?
What interfaces call it?
What calls it?
What state does it own?
What assumptions does it enforce?
What happens if it fails?
Only then assign a technical mapping.
Every confirmed mapping should eventually include:
Repository
Path
Symbol
Technical function
Verification status
Date verified
Example:
### Bifröst
**Project:** Project A.E.S.I.R.
**Symbol:** `BifrostGate`
**Path:** `...`
**Technical Function:** HTTP/API gateway
**Status:** CONFIRMED-SOURCEChange:
UNMAPPED
to:
CONFIRMED-SOURCE
only after verification.
Suggested commit:
git commit -m "docs: expand ecosystem mythological glossary"For repository-specific audits:
git commit -m "docs: verify mythic terminology mappings for <project>"Long term, the ecosystem should automate at least part of this process.
A glossary audit tool could:
- scan repositories,
- identify mythological terms,
- identify unknown names,
- compare source with glossary entries,
- detect undocumented usages,
- generate candidate mappings,
- require human or agent verification,
- update the confirmation ledger.
Example conceptual command:
mythic-glossary audit .Possible output:
MYTHIC TERMINOLOGY AUDIT
Known identifiers: 51
Verified mappings: 39
Unverified mappings: 7
Unknown identifiers: 5
UNKNOWN:
fylgja
hamingja
mimameidr
ratatoskr
andhrimnir
The system must never automatically mark an AI-generated guess as confirmed.
This section helps agents decompose compound names.
| Root / Stem | Meaning | Possible Engineering Association |
|---|---|---|
áss |
god / member of Æsir | high-level authority |
brunnr |
well, spring | knowledge source, datastore |
borg |
fortress | hardened boundary |
fylgja |
following spirit | companion process, attached agent |
garðr |
enclosure | boundary, namespace, domain |
heimr |
world, realm | subsystem, environment |
höll |
hall | registry, aggregation point |
hugr |
thought, mind | reasoning, cognitive state |
minni |
memory | persistence, recall |
mót |
meeting, encounter | junction, comparison |
rún |
rune, secret | encoded symbol, configuration |
ráð |
counsel | recommendation, decision |
seiðr |
magical practice | transformation, probability manipulation |
stafr |
staff, stave | reference, symbol, structural unit |
vél |
machine, contrivance | mechanism, engine |
vé |
sacred enclosure | protected scope |
vörðr |
guardian | monitoring, protection |
völva |
seeress | prediction, forecasting |
wyrd |
unfolding causality/fate | state evolution |
þing |
assembly | consensus, coordination |
örlǫg |
foundational causal layers | inherited state |
heimdallr |
divine watcher | monitoring / gateway guard |
When encountering an unknown compound:
- identify each root,
- determine the literal or historical meaning,
- determine whether the compound is historically attested or newly coined,
- inspect the implementation,
- explain the naming metaphor,
- document the actual function separately.
Never reverse this process by inventing functionality from the translation.
When creating a new mythologically named component, follow these principles.
The mythology should meaningfully relate to the engineering function.
Good:
Muninn → memory
Bifröst → bridge
Heimdallr → watcher
Weak:
Thor → random JSON parser
unless there is a documented architectural reason.
The best mythological architectures encode relationships.
Example:
Midgard
│
▼
Bifröst
│
Heimdallr
│
▼
Asgard
This communicates more than four unrelated names.
Do not create:
MuninnMemory
MimirMemory
SagaMemory
UrdMemory
OdinMemory
unless these actually represent different memory concepts.
Instead distinguish their semantics.
Example:
Muninn → active AI memory
Urðr → historical event ledger
Mímir → knowledge retrieval
Örlög → persistent causal state
The naming system should reduce cognitive load rather than increase it.
A developer who understands the glossary should gradually be able to navigate the architecture by mythology.
Not every component needs a mythological name.
Use ordinary engineering terminology when it is clearer.
Mythology is a semantic tool, not a naming quota.
When adding a new term:
- place it in the appropriate mythological category,
- use the established heading structure,
- document its historical or mythological origin,
- provide alternate source-code spellings,
- explain its general Mythic Engineering association,
- identify every known repository using it,
- verify each implementation independently,
- mark uncertain information clearly,
- update the project confirmation tracker,
- update the Etymology Quick Reference where appropriate.
If technical function is unknown, write:
Unknown — implementation has not yet been traced.
Never leave the field blank.
Add the repository to the tracker.
Then perform a complete mythological terminology audit.
Do not assume terms already defined elsewhere have the same implementation.
Preserve the old entry.
Mark it:
HISTORICAL
or:
DEPRECATED
and point to the replacement.
This prevents old documentation, commits, issues, and branches from becoming incomprehensible.
Source beats symbolism.
Verified documentation beats speculation.
Project-specific mappings beat ecosystem assumptions.
Unknown is a legitimate documentation state.
AI-generated interpretations must remain hypotheses until verified.
Never propagate an inferred mapping into:
- architecture diagrams,
- API documentation,
- agent instructions,
- capability ledgers,
- training data,
- generated code,
- developer onboarding,
- project specifications,
as though it were confirmed.
When mythology and implementation disagree, document the implementation.
Then optionally note that the name is metaphorically imperfect.
Do not rewrite reality to make the mythology prettier.
This glossary is a living semantic map of the entire project ecosystem.
Its job is not merely to explain Norse vocabulary.
Its deeper purpose is to preserve the relationship between:
MYTH
│
▼
CONCEPT
│
▼
ARCHITECTURE
│
▼
IMPLEMENTATION
The mythology provides a language.
The architecture gives that language structure.
The source code gives it reality.
As the ecosystem grows, this glossary should grow with it.
Every new repository, agent, protocol, engine, daemon, subsystem, database, hardware node, world-model component, memory layer, communication bridge, simulation system, or experimental architecture may add new terminology.
That terminology must remain discoverable.
It must remain understandable.
And above all, it must remain truthful.
Do not guess.
Trace the source.
Understand the myth.
Document the mapping.
Preserve the distinction.
Commit the knowledge.
Myth gives the architecture a language. Proof gives that language meaning.