Hi, I'm Jimmi.

Why DocZoid exists

For years I watched the same thing happen on every project I worked on. The architects drew the system in a diagramming tool. The business drew it again in PowerPoint, badly, from a screenshot. Somebody wrote a page about it in a wiki that linked to neither. Three descriptions of one system, and no way to tell which one was current.

The obvious fix is one workspace where a document, a diagram, and a presentation share the same live content. That is what DocZoid was at the start, and PortalSnips are how it works: a passage or a region of a canvas, created once, inserted anywhere, updated everywhere when the source changes.

That fixed the copying. It did not fix the deeper problem, which is that the source of truth was still a person remembering to update a picture. People do not remember. They leave, they get busy, they move teams, and the diagram quietly stops being true while continuing to look authoritative. That is the worst possible failure mode for documentation.

Connecting repositories is what closed the loop. The code is the one description of a system that is never out of date, because it is the system. So now the diagrams come from there, they regenerate when you push, and every doc and every slide that embeds one gets the correction for free.

Adding a full MCP server was the same idea pointed the other way. Your AI already reads the repository. Now it can read what you wrote about the repository, and write back to it, so the documentation is part of the loop instead of a thing you update afterwards and then do not.