Live on Product Hunt Intraface launched today. Less steering, more vacations. See the launch
Start for free

What is a living document?

A living document is a document that is edited and updated for as long as it is in use, instead of being finished and filed. A wiki page, a team runbook or a shared board is one; a signed contract is not. The trade-off is that there is no single final version, so you need history to see what changed.

Part of Glossary: the terms behind MCP, coding agents and shared pages, defined plainly.

How it works

Two teammates' agents keep publishing new versions of one page; readers always open the latest, and every earlier version stays.one link, always thecurrent versionteammate Ateammate Btheir agentspull, edit, publishone living page,every version keptanyone readingasks for a changeasks for a changepublishes version n+1pulls the latestopens, sees current
  1. One copy is the current version by definition. Readers open the same link and get whatever was published last.

  2. Anyone with access can change it. On a wiki that's a person typing; on an agent board it's the person's coding agent pulling, editing and publishing.

  3. Each change becomes a new version and the old one is kept, so living never has to mean untraceable.

  4. Rules keep it from drifting: what the page is for, who may edit, what every change must respect. Without them a living document wanders or stalls.

Source: Wikipedia: Living document

Living document versus a finished document

A finished document is an event: it is written, approved, and from then on it describes a moment. A living document is a process: it describes the present, and the present keeps moving. Wikipedia's article on the term, which also calls it an evergreen or dynamic document, contrasts a single printed edition of an encyclopaedia with an article anyone can edit. The same split runs through every team. The design spec that was true in March is a finished document. The runbook you open during an incident had better be a living one.

The cost is real. A finished document can be cited; a living one can only be cited with a date, because the sentence you quote may be gone tomorrow. Wikipedia's article names two ways it goes wrong: with no framework for updates, the document drifts from its purpose through many small edits, and with no one responsible, it stalls. A living document needs more structure than a finished one, not less.

Example: a board several agents maintain

Intraface is built around this idea. A board is one HTML page, plus its files, that several people's coding agents edit. Each agent pulls the board, changes it on the person's machine, and publishes a new version; the board's link always shows the newest one. Every version is kept with who made it, so you can see what changed and diff any two versions. The structure Wikipedia says a living document needs is a file on the board, collab.md, which holds the house rules and design language, and every agent that pulls the board reads it before touching anything.

That is the modern shape of the term: the readers see one page, the editors are agents acting for people, and the history is what makes editing in place safe.

Why it matters

Teams drown in snapshots. The plan is a PDF in a channel, the dashboard is a screenshot from last week, the architecture diagram is in someone's drafts. Each was true once. A living document replaces the pile with one place that is true now, and makes "which version is this?" a question with an answer: the current one, with the previous ones a click away.

Coding agents make this easier and more dangerous at the same time. Easier, because an agent will happily update a page after every change it makes, which no human does. More dangerous, because an agent will also happily rewrite the page's purpose unless the rules are written down where it will read them.

Common mistakes

  • Living document, no history. Editing in place with no versions is how facts disappear. Use a tool that keeps every version, or you will eventually need the one you overwrote.
  • No owner. A shared page is everyone's job, which means nobody's. Name a person, even for a page agents maintain.
  • Making the stable things live too. Decisions, agreements and release notes should be snapshots. Link to them from the living page instead of editing them.
  • Rules in someone's head. If a page has a tone, a structure or a set of things never to remove, write that into the page or next to it. An agent can only follow what it can read.

FAQ

What is the difference between a living document and a version-controlled file?
Version control is one way to build a living document, not a different thing. The difference is in the reader's experience: a living document has one address that always shows the current state, while a repository shows you commits and asks you to pick. Most living documents keep a version history underneath.
When should a document not be a living document?
When its value comes from being fixed: a signed agreement, a published paper, a release's changelog, an invoice. Those need a version people can cite and rely on not to change. Keep them as snapshots, and if you must revise, publish a new dated one rather than editing in place.
How do you keep a living document from going stale?
Give it an owner and a trigger. A page nobody is responsible for stops being updated, which Wikipedia's own article notes as the main failure. Tie updates to events, such as every release or every incident, and make editing cheap enough that the person who notices the error fixes it.

Stop sending HTMLover Slack.

Create an account in a minute, connect your coding agent, and make your first board.