Docgent is the system of record for documents that agents produce and humans are accountable for. Every change is legible. Every version is retrievable. No edit, human or agent, silently overwrites another.
The first turn is everything you were promised. Twenty pages that would have taken two days, drafted from the right sources, in the right structure, in ninety seconds. The second turn sharpens the executive summary. The third fixes the tone of section four.
By the seventh turn you have asked for a dozen changes, two of which contradicted each other, and the document in front of you is no longer the document you reviewed. A figure you corrected at turn four has reverted. A paragraph you struck has reappeared under a different heading. A defined term has drifted. You cannot tell which of these has happened, because you cannot see what changed — you can only see what the document now says.
So you read all twenty pages again. It is the third time this week.
Nobody has done anything wrong. The agent behaved exactly as designed. So did you. The failure is structural: the document is living inside a conversation, and a conversation has no canonical state. There is no version that is the version. There is only the most recent thing the agent said, and your memory of what you asked for.
An agent rewrites 40% of a document. Somewhere in there are two changes you asked for and one you didn't. Finding them costs a full re-read.
Three agent runs, three proposed rewrites. One went out. The other two are in a Slack thread, or gone. There is no decision record — only recollection.
You want to strike one paragraph, reorder two sections, and send the rest back for another pass. Today that means copy-paste, and the audit trail dies at the clipboard.
Six months on, a client disputes a number. You need the document as it was, not a regeneration that renders differently today and reads differently too.
The cost of a document has two halves. Producing it, and being confident enough in it to send it. Agents took the first half almost to zero. The second half is exactly where it was — and in most teams it has got worse, because volume went up and review capacity didn't.
The result is a choice nobody wants to make. Review every turn in full, and the saving disappears into re-reading. Stop reviewing every turn, and you are signing work you have not checked. Most teams end up doing the second while telling themselves they are doing the first.
Docgent attacks the second half. When a change is visible, isolated and attributable, review scales with the size of the change instead of the size of the document. Turn seven costs what turn seven should cost — a two-minute look at four paragraphs, not another pass through twenty pages.
Agents commit at volume. Humans make targeted edits in the studio. Both write to the same history, and every write carries the identity of the version it was based on. A stale write is rejected, not merged into silence. You never have to work out which copy is the real one, because there is only one.
Blocks are tracked by identity, not by position. Rewrapping a paragraph reports nothing. Moving a section reports a move, not a delete and an insert. Changing a key figure reports that figure, before and after. The diff is a summary of the decision, not a wall of red and green.
Draft, in review, approved, released, superseded. Each transition is recorded against the exact content it applied to, with the approver's name attached. When a document is approved, it is approved as a specific thing — not as a title that later contained something else.
Every rendered PDF is keyed to the commit that produced it. Six months later "what did we send" returns the artefact, the source it came from, who approved it and when. Not a regeneration. The thing itself.
Then it happens again, forty times, and the fortieth time is as legible as the first.
Steps 1–3 are live today. Partial-acceptance and inline annotation (step 4) are the current build phase.
Three layers, strictly separated.
If an author — human or agent — needs raw HTML to get an outcome, the vocabulary is missing a term. The validator rejects the escape hatch rather than letting it through, and the missing term gets added. It is a stricter rule than most tools are willing to enforce, and it is what keeps a diff legible and a design system intact at any volume of production.
The trade is real and worth naming: you give up arbitrary formatting. What you get back is a document whose changes can be described, whose look is consistent across every brand and entity you publish under, and which renders identically in six months' time.
Git is the version control system that most of the world's software is written on. Docgent uses it as the store rather than building a database and a sync layer on top of one, which means there is no reconciliation logic to get wrong and no scenario where the history and the document disagree.
For you, it means four things. History is immutable — nothing is quietly rewritten. Every version is retrievable, forever. Your documents are plain files in a standard format, so you can clone the whole archive and walk away at any time. And it is proven at a scale no document tool will ever reach.
You will not need to learn it. The studio is a split-pane editor with live preview. Git is what makes the guarantees hold, not what you have to operate.
An investment memorandum goes through fifteen versions in three weeks. Numbers move. A figure corrected in v9 must not reappear in v13. When the raise closes, you need to know what each party was shown and when.
The work product is signed by an accredited practitioner. Their obligation is to the file, not to the draft — they must be able to demonstrate what they reviewed, on what basis, and what they approved. An agent-drafted document with no reconstructable provenance is not signable at any speed.
Board papers, quarterly letters, committee packs. Multiple entities, each with its own visual identity. Approval history is the record. Six months later, the question is not what the document says now — it is what it said then.
Docs has version history built for humans typing. It records keystrokes, not decisions, and it has no concept of a change proposed by an agent, reviewed, and accepted in part. Ask Docs what changed between Tuesday and Thursday and it will show you every character. Ask what was approved, by whom, against which content, and there is no answer to give.
That is the right instinct and it is where this started. What you find is that raw git diffs on prose are unreadable — a rewrapped paragraph looks like a rewritten one — that markdown alone gives you no consistent rendering, and that nobody outside engineering will operate it. Docgent is that instinct made usable by the people who have to sign the output.
DOCX export is on the roadmap, not yet shipped. If Word compatibility is a hard requirement for your workflow today, tell us — it's the objection we're prioritising against next.
No. Docgent is agent-agnostic — anything that can call an API can open a proposal. OpenClaw and Slack are first-class integrations today because that's where our own usage started, not because the system depends on them.
In a git repository scoped to your organisation. Get in touch and we'll walk through hosting, tenancy, and export options for your specific setup.
Once figures are first-class objects rather than characters in a paragraph, a document can be checked the way code is. A total that no longer matches its components. A figure that was corrected three versions ago and has reverted. A defined term used two ways. A cross-reference pointing at a section that has since moved.
These are the errors that survive review, because they are exactly the errors a human reader skims past on the fourth read of the same page. They are also the errors that cost the most when they reach a client, a regulator or an investment committee.
The closed vocabulary is what makes this possible. A key figure block is a value with an identity and a history, so it can be watched. That is the direction.
If your team is already drafting with agents and answering "which version is final?" in a Slack thread, we should talk.