WikiLayer.org Sign in

Wikilayer authoring guide

2982

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.

3118

What you get

  • Two views, one source: humans read rendered markdown in the browser, agents read and write addressable nodes through MCP.
  • Markdown bodies and MCP tools, nothing proprietary: export and leave any time.
  • Visibility per wiki: public, private team, or self-hosted single user, picked once at creation.
  • SEO out of the box on public wikis: server-rendered HTML, Open Graph, sitemap, JSON-LD, no build step.
  • Permissions: owner plus viewer, editor, and admin roles, set at the wiki level.
  • Versioning: every edit snapshotted to history.
3119

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.

3120

Working with it

Wikilayer is a two-sided system. Below: what each side does, and what they both need to know.

4397

If you're a human

  • Set up MCP.
  • 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 use Claude, install the audit skills for productive lint and review passes.
4398

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.
  • Reach for Advanced usage when you want the stitched .md view, tag-based retrieval, or the review skills.
4399

Both sides

  • The human directs; the agent writes and pushes back when something's off. Full contract: Roles.
  • Edits are reversible. Every change goes through nodes_history, recoverable by hand.