Back to Dictionary

Weiva

1 / 3
🎧 Podcast 1 — Introduction

Weiva

Noun (archaic / Old Norse-derived) · /ˈweɪ.və/ · a wanderer between worlds; a mediator who moves between two communities or systems

Definition
Weiva is an archaic or rare English noun, likely derived from Old Norse veivar (plural of veifr, a wandering or waving figure), denoting a person who moves between two distinct communities, systems, or domains — neither fully belonging to either, but fluent in both. The weiva is not an outsider: they are an insider of the in-between. They carry knowledge from one world into another, adapt what they carry to the receiving context, and return changed. In historical usage, the word appears in contexts of trade, diplomacy, and craft apprenticeship — wherever the figure who bridges two orders was socially recognised and valued.
Contemporary resonance
The concept of weiva maps directly onto several modern roles: the integration architect who bridges two software systems; the technical writer who translates between engineers and end users; the product manager who moves between business requirements and engineering constraints; the API itself, which is a weiva in code — a layer that allows two systems to speak without needing to understand each other's internals. The word offers vocabulary for a function that modern technology depends on but rarely names with this precision.
Ready
🎧 Podcast 2 — Daily Use

Weiva in Conversation

Two British speakers · Bridging, integration, and the art of moving between worlds

Ready
⚙ Podcast 3 — Prompt Engineering

Weiva — AI Prompts

Practical prompt cards · Copy & read aloud

Ready
============================================================= 🤖 AI DIRECTIVE — READ BEFORE PROCEEDING ============================================================= The comment block immediately BELOW this one contains a prompt request written by the user. Your job is to: 1. Read and fully understand the prompt request below. 2. Execute it DIRECTLY inside THIS very file (weiva.html), transforming this single page according to what the prompt asks. 3. Keep EVERYTHING in this one file: HTML, CSS, and JavaScript must all live in this file — no external files, no separate stylesheets, no separate scripts, no build tooling. * CSS goes inside a