The document is being quietly rebuilt, and the version that wins will have three properties: it will be easy to edit by hand, it will travel freely between tools, and it will be native to the web rather than locked in one company's file format. AI is the force driving this, but the shape of the outcome is not really about AI. It is about who controls the output once the AI has done its bit.
For thirty years the document meant a proprietary file you opened in the program that made it. The format was the moat. Your work lived inside a vendor's box, and moving it out meant conversions, broken formatting and lost fidelity. That model is now under real pressure, because the way documents come into existence has changed.
AI makes generation cheap, so control gets scarce
When producing a first draft took an hour, the value was in the writing. Now a decent draft appears in seconds. That does not make documents less important. It moves the scarce, valuable work downstream, to editing, judgement and control. When anyone can generate ten versions of anything, the person who can quickly shape the right one has the advantage.
This is why the future document has to be genuinely editable by a human, not just re-promptable. Re-prompting is coarse. It swaps the whole thing when you wanted to change a line. A document you can put your hands into, adjust precisely and leave otherwise untouched, is a document you actually control. As I have argued in the case for editing over regenerating, that last mile of handwork is where the value now sits.
Portable beats proprietary
The second property is portability. AI does not respect your vendor boundaries. It will happily generate a document, then hand it to another tool to restyle, then another to publish. That pipeline only works if the document is in a format everything can read and write. A proprietary format is friction at every handoff. An open one is a clean pipe.
This is a straightforward prediction: the documents that thrive will be the ones that move without permission. No export step, no fidelity loss, no "please upgrade to open this file." Just a format that every tool, every browser and every model already understands.
Why HTML is quietly winning
Here is the slightly unfashionable claim: that format is HTML. It is not new or exciting, and that is exactly why it works. HTML is already the most universal document format on earth. Every device renders it. It styles beautifully. It carries structure, links and layout. And AI models are extremely comfortable producing it, because the web is what they learned from. When you ask a model for a nicely formatted document, HTML is often what it reaches for naturally.
HTML is, in other words, already AI-native and already portable. It ticks two of the three boxes without anyone planning it. The missing box has always been the editing experience. Raw HTML is hostile to normal humans. If changing a heading means finding the right tag in a wall of markup, the format fails the hand-editable test, and people fall back to re-prompting or copying into a word processor and losing the formatting.
Close that gap and HTML becomes the complete package. This is the specific problem htmlEdit exists to solve: it lets you edit a rendered HTML document by pointing, clicking and typing, the way you would in a word processor, so you get the portability and AI-friendliness of HTML without ever touching the code. The document stays open, editable and yours.
What this adds up to
Put the pieces together and the future document looks like this. It is generated with AI assistance, so it starts fast. It is HTML, so it is portable and universal. It is editable by hand without code, so you keep control of the final result. And increasingly it is handled locally and privately, because as the volume of AI output rises, so does the value of not shipping every draft to someone else's server.
None of this requires a grand new standard. The pieces already exist. What is changing is which properties matter. For years we optimised documents for the program that made them. We are about to optimise them for movement, editability and the open web instead. That is a better set of priorities, and it puts you, not the vendor, back in charge of your own work.