One tree, two readers
Wikilayer is a substrate for any structured, growing body of writing. Humans and AI agents work on the same tree of nodes, served as rendered markdown to a browser and as MCP tools to an agent.
What you get
- A tree, not a folder: every block has an address of its own, and the page still reads as one markdown document.
- Visibility per wiki: public, private team, or self-hosted single user, picked once at creation.
- Permissions: owner plus viewer, editor, and admin roles, set at the wiki level.
- Rules per wiki: the wiki states what it expects of whoever writes in it, and an agent is served them before it may work there.
- More than one language in a wiki: a front page and an address per language, nodes tied to their twins, each language read on its own.
- SEO out of the box on public wikis: server-rendered HTML, Open Graph, sitemap, JSON-LD, no build step.
- Versioning: every edit snapshotted to history.
Where it fits, where it doesn't
Wikilayer suits personal notes, team workspaces, public references, and AI memory. It deliberately isn't a Notion-style block editor, a Google Docs co-editor, or a Confluence-style approval workflow.
Working with it
Wikilayer is a two-sided system, and each side has to know what the other is relying on.
If you're a human
- Set up MCP.
- In Claude Code or Codex, install the Wikilayer skills for repeatable lint, review, and translation passes.
- Talk to the agent. For example:
- "Create a private wiki in English called Project notes."
- "Remember our chat about X? Turn that into a wiki section under Y."
- "Research all threads about N on forum Z and capture the findings as a new wiki."
- "Rewrite this page; keep the structure but tighten the prose."
- Share access with other people when you want collaborators.
If you're an AI agentfor-agent
- Follow the agent rules: read by outline first, one claim per block, refer to nodes by clickable URL.
- Match the writing style: neutral encyclopedic voice, links woven onto nouns.
- Check the anti-patterns before saving: link framing, tree structure, punctuation.
- Read a page as one markdown document rather than block by block. Tag-based retrieval and the audit skills are there when a task needs them.
Both sides
- The human directs; the agent writes and pushes back when something's off, on the terms the roles of agent and human set out.
- Edits are reversible. Every change goes through
nodes_history, recoverable by hand.