When Git Grows Up
Git-based knowledge management has always been too complex for content teams. Agents change that, and the implications for governance-heavy organisations are worth watching.
The problem with git was never git. It was the assumption that everyone working with content could think like a developer.
Version control is a sound idea for knowledge. Track changes, branch, merge, roll back. For organisations managing legal, financial, or medical content at scale, that discipline is exactly what is needed. The tooling just never matched the people. Authors are not engineers. They do not want to commit, push, or resolve merge conflicts. They want to write, review, and publish with confidence that nothing disappears.
The interface problem
What changes when you add agents to a git-based knowledge system is the interface between the system and the person using it. Branching becomes a guided act rather than a technical one. An agent can explain what a branch means in the context of a document review, prompt the right action, and flag when something looks inconsistent with the rest of the knowledge base.
Editorial standards are where this becomes interesting. In most content organisations, style guides and governance rules live in a wiki page or shared drive folder that someone remembers to check. Complying with them is a personal responsibility, which means compliance is uneven. When an agent carries those standards into the editing environment itself, the guidance becomes active. It surfaces at the moment it is relevant, not when someone remembers to look it up.
Governance as the use case
This matters more in some sectors than others. For organisations where content carries legal weight, where a document version can be cited in a court or audit, the distance between "we have a process" and "the process is enforced" is significant. Version control closes part of that gap. Active editorial guidance closes more of it.
The clients who need this are not looking for a productivity tool. They are managing risk. The question they are asking is not whether their teams can write faster, but whether the organisation can demonstrate that what was published, when, and under what review, is traceable and defensible.
European footing
For organisations in regulated European industries, where content is held, and by whom, is not a neutral question. A knowledge platform with European hosting and ISO 27001 certification in progress is not a marketing differentiator. It is a procurement requirement waiting to be formalised.
The certification path matters here in a specific way. For public sector and governance-heavy clients, ISO 27001 is the entry point to a longer chain: certification enables insurance, insurance enables enterprise contracts, enterprise contracts carry SLA penalties that in turn require the certification to hold. Once you commit to this path, you commit to maintaining it. The liability is real and personal. That is precisely why most smaller technology companies avoid it, and why those that do pursue it can credibly operate at a different scale.
The combination of git-based versioning, agent-assisted authoring, and European infrastructure with serious certification underway is a specific answer to a specific problem. It is not the most obvious stack. But for the organisations that need it, it fits in a way that general-purpose tools do not.
Rob Hoeijmakers
Rob Hoeijmakers