Wiki Layer
Wiki Layer is an architectural pattern for multi-agent systems: a shared, git-native markdown store that all agents on a team can read from and write to, distinct from each agent's private notebook. It functions as durable team memory — facts and synthesized briefs that persist across sessions rather than evaporating with each context reset.
The term entered public discourse on April 25, 2026 with the WUPHF Show HN thread, which described shipping "a wiki layer for AI agents that uses markdown + git as the source of truth, with a bleve (BM25) + SQLite index on top." WUPHF hit 124 points and 59 comments within hours, and wikilayer.com had already been registered on April 6.
In WUPHF's implementation, each agent writes raw task observations to a private agents/{slug}/notebook/ directory, then promotes durable insights to the shared wiki — a living knowledge graph of typed facts, per-entity append-only logs, and LLM-synthesized briefs committed under an archivist identity.
Think of it as a shared whiteboard for AI teammates, where everyone writes but nothing gets erased between shifts.
Search Interest
-
Nascent0–7 days
-
Emergent8–30 days
-
Validating ← now31–90 days
-
Rising91–180 days
-
Established180 days +
Why is it emerging now?
Multi-agent systems are mainstream in 2026, but team memory remains unsolved: each agent loses shared context on every session reset. Wiki Layer names the missing piece — a git-backed markdown store all agents can read and write, promoted from private notebooks. WUPHF shipped a working implementation and coined the term publicly on April 25.
Outlook
6-month signal projection and commercial timeline.
Team memory is the unsolved gap in multi-agent systems; wiki layer names it, if WUPHF reaches critical mass before cloud vendors absorb the pattern.
Risk · Cloud vendors may ship 'shared agent memory' under proprietary terms, erasing the wiki layer label.
Analogs · llm-wiki · agent-harness · context-engineering
-
nowSERP gap, no competition
Zero content ranking for 'wiki layer agents'; wikilayer.ai, .io, .app all available.
-
3-6moTeam memory tooling emerges
MCP servers and agent frameworks ship wiki-layer adapters; comparison content and templates monetize.
-
6-12moVendor absorption risk
Cloud agent platforms ship shared memory natively; standalone wiki layer tools face commoditization.
Competition & Opportunity for term “Wiki Layer”
Three heuristic signals derived from the tracked queries, the term's monetization cards, and its cluster neighbors. Directional, not audited.
Ideas for term “Wiki Layer”
Buildable pitches — turn this term into an article, site, product, post, newsletter, video, or course. Steal any card and run with it.
Zero content covering this distinction yet. Ranks for 'multi-agent memory architecture', 'agent shared context', and the growing LLM wiki ecosystem. Tutorial + diagram format.
Pattern is framework-agnostic: a git repo + markdown + BM25 index. Covers implementation in Claude Code, LangGraph, and raw Python. Targets builders already running multi-agent pipelines.
Practical comparison: BM25 + markdown vs Mem0 / Zep / Letta. Targets the same decision-makers evaluating RAG vs LLM wiki. High-intent comparison query, currently unsaturated.
Single `npx wikilayer` command bootstraps a markdown + git knowledge store any coding agent can read and write. Targets devs who want WUPHF's memory architecture without the full platform.
WUPHF includes daily lint passes; this is painful at scale. A scheduled agent that flags stale facts and contradictions across the shared wiki is a genuine paid SaaS surface.
First-person experiment with real outputs — what facts agents promote, what contradictions emerge, what the wiki looks like after 48 hours. LinkedIn / HN format, high engagement ceiling.
Every multi-agent system I've seen either duplicates context in every agent prompt (expensive) or shares nothing between sessions (useless). The wiki layer pattern from WUPHF is the first approach I've seen that actually works at team scale.
Karpathy's LLM wiki went viral April 4. Three weeks later, a 276-star repo on HN quietly named the piece nobody had isolated yet: the wiki layer.
Running five coding agents in parallel burns tokens fast when each one re-reads the same shared context. I tried replacing that with a wiki layer — a git repo of markdown that all five can read and write.
What People Search
Long-tail queries from Google Suggest + Trends. Volume and competition are heuristics — directional, not audited. Content Type comes from query shape.
SERP of term “Wiki Layer”
What searchers see today — organic results on top, paid ads if anyone's bidding. Ad density is a real-time commercial signal.
FAQ
What is Wiki Layer?
Wiki Layer is an architectural pattern for multi-agent systems: a shared, git-native markdown store that all agents on a team can read from and write to, distinct from each agent's private notebook.
Why is Wiki Layer emerging now?
Multi-agent systems are mainstream in 2026, but team memory remains unsolved: each agent loses shared context on every session reset. Wiki Layer names the missing piece — a git-backed markdown store all agents can read and write, promoted from private notebooks. WUPHF shipped a working implementation and coined the term publicly on April 25.
When did Wiki Layer emerge?
Publicly emerged around 2026-04-06 (about 71 days ago as of 2026-06-16). EarlyTerms first recorded a pipeline signal on 2026-04-25.
Related Terms
Other terms in the same space — aliases, subtypes, competitors, and neighbors to explore next.
- Part of llm-wiki LLM wiki is a pattern where an AI agent incrementally compiles a folder of plain-markdown entity pages from your raw sources, then… →
- Part of context-engineering Context engineering is the discipline of curating every token that enters an LLM's context window — system prompt, tools, retrieved… →
- Competitor vault-context Vault Context is the practice of feeding a local Markdown vault — its files, folder layout, frontmatter, tags, and retrieved chunks — to… →
- Related agent-harness An agent harness is the middleware between a large language model and the real world — code that runs the agent loop, calls tools,… →
- Related agents-md AGENTS.md is an open, vendor-neutral markdown file placed at the root of a repository that tells AI coding agents (Claude Code, Codex… →
- Related managed-agents Managed Agents is an infrastructure paradigm where cloud platforms host, orchestrate, and operate AI agents as a service. →
- Related workspace-agents Workspace Agents is OpenAI's enterprise feature that lets teams build shared AI agents — powered by Codex — capable of running… →
- Related context-rot Context rot is the measurable degradation in large-language-model output quality as input length grows, even when the prompt stays well… →
- Related personal-ai Personal AI is the category of AI systems built around one individual — their memory, voice, preferences, and recall — rather than a… →
- Related ai-workspace An AI workspace is a persistent, project-scoped container where chats, files, tools, and memory live together — replacing the stateless… →
- Part of
- Competitor
Sources
Primary URLs this report cites — open any to verify the claim yourself.
- 01 WUPHF — Show HN: A Karpathy-style LLM wiki your agents maintain news.ycombinator.com ↗
- 02 nex-crm/wuphf — GitHub (reference implementation) github.com ↗
- 03 Karpathy — llm-wiki.md gist (origin pattern) gist.github.com ↗
- 04 MindStudio — LLM Wiki vs RAG mindstudio.ai ↗
- 05 Intelligent Living — Karpathy LLM Wiki markdown knowledge base intelligentliving.co ↗
- 06 HN flagship thread — LLM Wiki idea file (296 pts) news.ycombinator.com ↗