Two-way GitHub sync
Link a folder to a repo and branch. Edits flow both directions through a true three-way merge — not last-write-wins, not a one-way export.
For developers & AI
Docs that live in the repo — and agents that can edit them.
Keep specs and decks beside the code, model data in sheets, and turn agent-generated HTML into governed Arts. MCP lets agents edit the live artifact while people review with comments and versions.
Bring your own model key. Self-hosting available under licence.AI creates and editsLive collaborationInline commentsVersion historyFolders and namespaces
Documentation rots because it lives somewhere else
Three reasons docs drift from reality — and what closes the gap.
The design doc lives in a wiki nobody opens during code review.
It’s a file in the repo, changed in the same pull request as the code.
Editing docs in a WYSIWYG tool means the git history is a single opaque blob.
Plain Markdown. Line-level diffs, real blame, ordinary review.
Your agent writes a doc, you paste it in, and the formatting explodes.
The agent connects over MCP and edits the live document directly.
Built the way you’d build it
Portable sources, real merges, live agent work, and review you can audit.
Mermaid diagrams
Architecture diagrams as text in the same file. They diff, they review, and they never go stale in a design tool nobody has a licence for.
Self-host it
Run the whole stack inside your own infrastructure under licence, when the data genuinely cannot leave the building.
Put every project artifact in one reviewable workspace
Keep Markdown sources beside code and move interactive HTML from chat output into governed Arts with comments, versions, and publishing.
3-wayMerge, not overwrite
MCPAgents edit live docs
BYOKYour key, your bill
.mdThe whole storage format