THE MESH
Shared context base

Where thinking with Claude becomes shared knowledge.

The Mesh is an extension of Claude as a thinking tool — the step after the conversation. The ideas, decisions, and structured knowledge you generate with Claude now land somewhere permanent, visual, and shared with the whole team.

A network graph inside a human head silhouette — the Mesh as shared intelligence
What this is

Plan mode on steroids for knowledge creation.

Claude Code's plan mode is the structured reasoning phase — Claude thinks through a problem carefully before acting. That thinking produces something valuable. The Mesh is what happens when that output stops being ephemeral: instead of a plan that lives in a conversation and disappears, you get a living artifact — visual, web-based, instantly shareable with the team, and continuously updated as your thinking evolves.

The process stays the same. You think with Claude, Claude produces structured output. But now that output lands somewhere real: expressive, collaborative, browsable by anyone on the team, and queryable by every agent. Knowledge creation as a first-class outcome of the Claude workflow, not a side effect of it.

The format insight

HTML is the format that works for both.

When agents do the writing and humans do the reading, markdown falls short — it can't carry visual hierarchy, navigable structure, or diagrams. HTML can. And agents get the same content as Markdown, via Cloudflare HTMLRewriter at request time. One document, two audiences, no dual format to maintain — the HTML is canonical and the Markdown is derived on demand.

The Unreasonable Effectiveness of HTML →

Two surfaces

Agents · MCP
mesh.smplrspace.com/mcp
12 MCP tools. Load sections as context, search, edit, create. Content is returned as extracted Markdown — token-efficient, access-gated, selective.
Humans · Web
mesh.smplrspace.com
Browse, search, share. Claude edits any page directly from a conversation — no GitHub account needed to contribute. External share links are scoped and revocable.

What's in it

01
Who we are
Company story, mission, product overview, team structure. The essentials before anything else.
02
How we work
Processes, norms, communication patterns, decision-making. How the team operates day to day.
03
How we present
Brand guidelines, tone of voice, visual identity. Anything that shapes output facing the outside world.
04
How agents operate
Skills, tools, reference patterns, and constraints written specifically for agent consumption.
05
What we're working on
Project-level context. Per-engagement briefs, goals, decisions, and shared state that agents and teammates need to stay aligned.

Built on Cloudflare — Workers, R2, D1, KV. HTML is canonical; Markdown is extracted on demand. GitHub syncs automatically on every write as a read-only safety net. Three scope levels: org-wide, team, and individual. If it isn't in the Mesh, it isn't shared knowledge yet.

Where this is going — The end state is immersive: a split screen with the Claude conversation on one side and the live Mesh page on the other, updating in real time as Claude writes. Not a tab you switch to. Not a commit you push. The thinking and the knowledge base side by side, in one continuous experience.