Muriki Docs
Where the decision lives — and stays true.
docs keeps what was agreed: the technical decision, the approved brief, the proposal you sent. The difference is that the task cited inside the text is alive: when it closes, the document knows. A document that ages on its own becomes a lie, and written lies are expensive.
Get accessDecision: CRDT on the client
The document is the local source of truth. The migration is being handled inMUR-25Offline sync with Yjs— when it closes, the paragraph below stops being true.
What was written, findable.
Collaborative documents
Two people in the same paragraph without one overwriting the other, online or not.Live cited tasks
The task mentioned in the text shows its current state, not the one from the day it was written.Search by subject
Find it by what the document says, not by the name someone gave the file.Team wiki
What matters to everyone lives somewhere with hierarchy, not attached to a message.Personal documents
What you write for yourself lives alongside, without cluttering the team's space.Version history
See what changed, when and by whom — including what was decided and then reverted.Templates
ADR, brief, meeting notes and proposal start in the shape the team agreed on.
What it will reach.
Integrations arrive with the module. All of them go through MCP, the open protocol the rest of the market is adopting.
- Google Drive
The final file lands where it always lands, and the old doc is found by subject.
- Slack
A long thread becomes a written decision, with the tasks it produced already created.
- Email
The proposal you sent is kept in the exact version that went out.
- Any MCP
The knowledge base your team already has plugs in the same way.
Is your team in the next wave?
Access opens in waves, as the modules become ready. People on the list go first.