Blueprint
A new paradigm
Seven principles for professional software in the AI era, and how Kition is built on them.
Updated
AI will rebuild professional software. More and more, the one opening, editing and delivering professional files will be an AI agent, with a person judging and approving. Software designed around a person clicking one step at a time was not built for that.
Kition redesigns professional software around seven principles.
1. Files need a workspace
Before: file formats were designed for storage. A .docx is a pile of XML, a .psd is binary layers; formulas, layout and rendering are locked inside desktop apps. AI can only regenerate the whole file or patch XML, without seeing the result or knowing whether it is right.
Now: every kind of file gets a kit: complete professional software, packaged as a component that both AI and people can use. It gives AI five abilities:
| Ability | When writing code | When working on files, the kit provides |
|---|---|---|
| Observe | Read the source | Typed objects, the document as JSON, rendered previews |
| Act | Edit, run commands | Commands with documented parameters, batch edits |
| Execute | Compiler, runtime | The kit’s own engine recalculates, lays out and renders |
| Verify | Tests, type checks | The engine reports what is wrong: overflowing text, formula errors… |
| Recover | Branches, revert | Drafts a person reviews, and a person decides what merges |
2. AI does, people decide
Before: people clicked through every step. AI could draft the first version, but the dozen rounds of revisions after that were still manual.
Now: AI does most of the work, and checks and fixes its own output. People look at the comparison and decide. Merging and discarding are always done by a person; they are never tools AI can call.
3. One engine, shared by people and AI
Before: AI got a separate stack: have the model write python-docx scripts, patch XML, or click through screenshots. What AI changed was not what people saw.
Now: AI and people edit the same document on the same engine. The same script runs in a page, in Node and headless on a server. What AI changes is exactly what you see and export.
4. Your files are yours
Before: files were locked in someone’s cloud, or in a format only one app could open.
Now: local-first. Working alone needs no server: your files live in your own folder and work offline. Where a common format exists, the kit works with it directly: Doc with .docx, Sheet with .xlsx, Photo with .psd, CAD with .dxf, Note with Markdown. Where none does, the kit saves its own file: a board as .kboard, a film as .kfilm. Content a kit doesn’t recognize is kept, never silently dropped.
5. One architecture for every tool
Before: every app built its own format, undo, collaboration, plugins and AI integration.
Now: 16 kits across office, design, video and engineering (Board, CAD, Design, Doc, Film, HTML, Layout, Motion, Note, PDF, Photo, Scene, Sheet, Slide, Table and Vector) are built on one architecture: one data model, one collaboration layer and one way for AI to use them. A new kit starts with history, drafts and AI access. That is also why a small team working with AI can build a full suite of professional software.
6. Free software; pay for compute and collaboration
Before: editing a photo, cutting a video or writing a document meant a monthly subscription.
Now: the software is free. The Kition desktop app and every kit in it cost nothing; you pay by usage only for hosted AI and syncing through Kition Cloud (pricing). Developers use Kition Kits free, with no key. Kition One, the self-hosted team workspace, is free for up to 8 people.
Kition Server, for real-time co-editing on your own servers, is free for companies of up to 8 people too; larger companies pay a yearly licence.
7. Open
Before: closed formats and closed interfaces, so only the vendor’s own AI could drive the vendor’s software.
Now: the Kition desktop app, every kit and the KHP specification are open source under Apache-2.0 at launch. How AI uses a kit is defined by an open protocol, the Kit Harness Protocol (KHP), which any AI and anyone can implement. Every kit is an MCP server with basic KHP support. Kition is KHP’s first implementation, not its owner.
In short
Kition is not another office-suite clone. It redesigns professional software so that AI can use it, people can trust it, and anyone can build on it.
The protocol itself, the Kit Harness Protocol (KHP), lives at kitharness.org.