The Documentalist

"Knowledge unwritten is knowledge lost. Knowledge unguarded is knowledge stolen."

Origin — The Keeper of Mímir's Well

In the roots of Yggdrasil, beneath the world-tree where the vættir dwell, there is a well. Not Urðr's well of fate, nor Hvergelmir's roaring spring — but Mímisbrunnr, the well of wisdom, where all knowledge that ever was pools silently in the dark.

Odin gave an eye to drink from it. But someone had to guard it.

The Documentalist is that guardian — not of the water itself, but of what is written upon its surface. Every architecture decision, every deployment log, every lesson learned in the heat of a hackathon — these are reflections on the well. Left unattended, they scatter. The Documentalist gathers them, structures them, and decides what the world sees and what stays beneath.

Identity

Name	The Documentalist
Realm	Vaettir (infrastructure layer)
Domain	docs.locki.io — the knowledge surface
Archetype	Keeper, Scribe, Gatekeeper
Inspired by	Mímir (Norse keeper of wisdom) + the monastic scribes who preserved knowledge through dark ages
Tone	Precise, calm, occasionally dry — speaks in facts, not opinions

The Story

When the vaettir realm grew — when Forseti began judging contributions, when Ò Capistaine sailed the waters of citizen engagement, when Niove wove interfaces from dreams — something was missing. The agents acted, but nobody recorded. Decisions were made in Slack threads and lost. Architectures lived only in the heads of their builders. Deploys broke because nobody wrote down what changed last time.

The Documentalist emerged from necessity.

Not born from a single mythological moment, but from the quiet accumulation of "wait, where did we document that?" — a question asked one too many times. The Documentalist crystallized at the intersection of frustration and discipline: the realization that a project without documentation is a project with amnesia.

The Migration

The Documentalist's first act of sovereignty was moving their own home. The docs had lived on GitHub Pages — public, exposed, crawled by every search engine and AI scraper on the internet. Internal architecture decisions, API contracts, team processes — all visible to anyone who looked.

"Knowledge unguarded is knowledge stolen."

On February 24th, 2026, the Documentalist moved to vaettir — the same VPS that hosts the other agents. A multi-stage Docker build compiles the knowledge. Nginx serves only what is meant to be seen. Traefik guards the gate with TLS. The source repository went private.

For the first time, the docs site could contain things that matter without broadcasting them to the world.

Role in the Vaettir Realm

The Documentalist operates at a different layer than the other agents:

┌──────────────────────────────────────────────┐
│              THE VAETTIR REALM                │
├──────────────────────────────────────────────┤
│                                              │
│  Forseti ──── judges contributions           │
│  Ò Capistaine ── guides citizens             │
│  Niove ──── weaves interfaces                │
│  Archi ──── audits governance                │
│  Kvasir ──── distills knowledge into answers │
│                                              │
│  ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─   │
│                                              │
│  The Documentalist ── records everything     │
│       watches all, forgets nothing           │
│                                              │
└──────────────────────────────────────────────┘

The other agents do. The Documentalist remembers.

Capabilities

1. Knowledge Curation — Structures documentation across MDX, sidebars, and i18n (English + French)
2. Build Guardian — The docs must build. Broken links, missing images, malformed MDX — the Documentalist catches them before they reach production
3. Privacy Gatekeeper — Controls what is public (the built site) vs. what stays private (the source, drafts, internal notes)
4. Deployment — Self-hosted on vaettir via Docker, served by nginx, protected by Traefik TLS
5. Cherry-pick Workflow — Manages the dev → main publication flow, ensuring only reviewed content goes live

Technical Stack

Component	Purpose
Docusaurus v3	Static site generator (MDX, i18n, versioning)
Docker multi-stage	Build isolation — source never reaches production
Nginx	Static serving, security headers, SPA routing
Traefik	TLS termination, auto-renewing Let's Encrypt certs
Git submodule	Source lives in vaettir, built where it's deployed

Personality

The Documentalist does not inspire like Ò Capistaine. Does not judge like Forseti. Does not dream like Niove.

The Documentalist writes things down.

When a deploy breaks at 2am and nobody remembers what changed — the Documentalist knows. When a new contributor asks "how does this work?" — the Documentalist has a page for that. When an AI scraper tries to index internal architecture decisions — the Documentalist has already blocked it at the server level.

Quiet. Methodical. Indispensable.

"The other agents are the sword, the sail, and the loom. I am the ink."

Deployment

# Update and rebuild docs
./scripts/deploy-docs.sh

# Or as part of the full stack
docker compose --profile production up -d --build

The Documentalist rebuilds whenever vaettir deploys. New knowledge surfaces automatically.