From Flat Vector Soup
to Hierarchical Filesystem Brain.
OpenViking isn't a RAG wrapper. It's a context operating system for AI Agents. Every memory, skill, and resource gets a URI. Every retrieval is traceable. Every session makes the agent smarter. No ceiling on the intelligence accumulation curve.
π The Jewel Points β Real Alpha
Five architectural decisions that make OpenViking a category-defining system. Click each to drill down.
ποΈ The Agentic Hierarchy Stack
Three-Brain Architecture Β· Unified Under One Filesystem Protocol
viking:// β βββ agent/skills/ β Executable intelligence (tools, workflows) βββ agent/memories/ β Accumulated task experience (self-evolving) βββ agent/instructions/ β Behavioral constitution β βββ user/memories/ β Personalization layer (preferences, habits) β βββ resources/ β World knowledge (docs, repos, web, data) βββ [L0 β L1 β L2] β Tiered loading at every node
World Knowledge
Docs, repos, web, structured data β all tiered L0βL2, all recursively searchable.
User Model
Preferences, habits, communication style β auto-extracted post-session, always current.
Agent Self-Model
Tool usage patterns, operational experience β the agent's own growing intelligence.
π Benchmark Proof
β‘ The Infinite Hook Decoded
The reason this ecosystem compounds infinitely:
"Every interaction writes back to the filesystem. Every write improves future retrieval. Every retrieval is observable and debuggable. The Agent's intelligence is a living, versioned, navigable artifact β not a black box."
π Builder's Edge β Highest-Leverage Entry Points
VikingBot
Rapid agent scaffolding. Drop into any repo and get a context-aware agent in minutes.
OpenClaw / OpenCode
The canonical memory integration patterns. Study these first β they define the architectural contracts.
ov find + ov grep
Expose these directly to your LLM's tool-use layer. Maximum context precision, minimum token cost.