Floxar, documentation and knowledge
Most organizations already have a great deal written down: procedures in documents, answers in a wiki, policies in shared folders, and a knowledge base that people and AI tools search. Floxar does not ask you to throw any of that away. It changes one thing: the part of your documentation that describes how work is done becomes something people and agents run, instead of something they read.
Documents describe; flows direct
A written procedure is read once, half remembered, and followed from memory. Nothing records whether it was followed, which version was used, or where people departed from it, and a change reaches some readers and not others.
A flow holds the same knowledge as steps to carry out. Whoever runs it, a person or an agent, is shown one step at a time, gives the answers the step asks for, and chooses among the paths your authors defined. The procedure is followed because following it is how the work gets done, and every run leaves a record. When the procedure changes, the next run follows the new version.
Three kinds of knowledge, three homes
| Kind of knowledge | Example | Best home |
|---|---|---|
| How work is done | Handling a refund request, onboarding a supplier, closing the month | A flow in Floxar |
| What a step relies on | The refund policy, a definition, a checklist of acceptable documents | A reference in Floxar, linked to the steps that need it |
| General background | Product manuals, history, broad guidance, past cases | Your existing documentation and knowledge base |
References keep supporting material next to the step that needs it: while running a flow, the person or agent opens the linked reference without losing their place. Broad background can stay where it is today; a step can point to it when it matters.
Why a knowledge base alone is not enough for AI agents
An AI agent given a whole knowledge base has to decide, every time, which documents apply and in what order to act on them. It may find an outdated page, combine two procedures, or skip a check nobody wrote down clearly. Afterwards there is no reliable way to show what it did or whether it followed the procedure you approved.
Searching documents is the right tool for answering questions. Carrying out a procedure needs something else: the approved steps, in order, with the answers each step requires and a record of each run. That is the part Floxar provides. Your knowledge base keeps answering questions; Floxar carries the procedure. The AI Assistant brings the two together inside Floxar, answering questions from your flows, bits and references.
Moving existing documentation into Floxar
You do not need to convert everything at once. Start with the procedures that matter most: the ones done often, done by many people, done wrongly at a cost, or that you want AI agents to take on.
- The Flow Designer can draft a flow from a document you already have, for you to review and accept.
- An AI client connected to your account can write flows for you from your documents, in your own words.
- Policies and definitions that several steps depend on become references.
- Everything else can stay where it is.
For how to write steps that work well for both people and agents, see What makes a good flow and Writing effective bits.
Last reviewed: 2026-10-06