Your standards, your client history, your hard-won decisions. Drafted keeps them in one place, lets your agents maintain them, and won’t let an agent change anything until it has looked.
Knowledge management fails for a boring reason: writing it down is someone’s least favourite job. So let the agent that just learned the thing be the one that records it.
The same wiki you edit in the browser is the one your agents search and update over MCP. What was learned in a session isn’t lost when the session ends.
Directory listings are generated from the pages themselves, so they are never stale. Rename a page and every inbound reference is rewritten automatically.
The wiki is an Open Knowledge Format bundle. Export it, read it in any editor, move it anywhere. Nothing about it’s proprietary.
You already have a shared drive, so the knowledge existing isn’t the change. The change is that reading it’s enforced at the moment the work happens.
| How AI works in most firms | How it works in Drafted |
|---|---|
| Every session starts by re-explaining the same context | The agent searches what the organisation knows before it’s allowed to start |
| What one person learns stays with that person | It’s deposited as a page the whole team and every future agent inherits |
| Your standards are pasted into prompts, or forgotten | They are pages the agent is required to consult |
| Knowledge lives in a tool you can’t leave | It’s portable markdown you can export in full, whenever |
An Australian engineering consulting firm keeps the standards its practice runs on in its Drafted wiki: AS 5342, the CIBSE commissioning codes, AIRAH DA27, and its own written handover protocols. An agent working one of their jobs doesn’t get the standards pasted into a prompt. It has to go and read them.
They haven’t agreed to be named yet. When they do, their name will be here.
Free to start, and everything in it’s exportable from day one.