Directive Handbook Kit · coming soon
Bring what
you know.
Leave with the handbook.
Your documents and decisions become pages you can read and ask questions of. Every fact that matters carries the lines it came from. And when you ask it something it has no answer for, it tells you so.
A$149 at launch · One paymentWorks with Claude Code and Codex
Built from your own papers.
The part nobody else does
It tells you
when it doesn't know.
Ask it a question and you get one of four answers. Here is what we have, and where it came from. Here is the part we have and the part we don't. This is unsettled, and here is why. Or: we have nothing on this, and here is the word in your question we have never seen.
The last two are the reason to buy it. A handbook that answers everything confidently is the thing you are already worried about.
See how it is builtWhat do we charge
for an urgent callout?
- Nothing recorded answers this.
- One word in your question has never appeared in anything you gave it: charge.
- Shall I add it to the list of things to answer?
- Before it becomes knowledge
You approve it, or it isn't in.
Your assistant drafts pages. A draft is a proposal, not a fact, and it stays a proposal until you have read it and said yes. The build is applied under your name, with the reason recorded. Nothing gets into the handbook because it read well.
- Seven words, two you use
Rely on this. Or don't.
Every fact carries one plain word: source-backed, provided by owner, inferred, needs confirmation, contradicted, out of date, or unknown. No score out of ten, because a number invites you to round it up. Day to day you are reading for two of them.
- A program, not a second opinion
Some builds are refused.
A fact that matters with nothing behind it. A citation that no longer lands on the words it quoted. A page nothing links to. Pages edited outside the process. Each one stops the build, and the last handbook you checked stays exactly where it was.
01 Who it is for
One business.
Or one per client.
Two people buy this. One builds a handbook for the business they run. The other builds one for each business they look after.
- The practitioner
- An agency, a fractional operator, a bookkeeper, an advisory practice. You already sit inside other people's documents. This turns a week of reading into something the client keeps, with the source attached to every figure you quoted back at them, and it is the same ten steps for the next client.
- The owner-operator
- Five to fifty people, and most of what makes the place work is in your head and in folders nobody else opens. You want a new person to find the answer, and you want to know which answers are still true.
- Building for clients
- A purchase covers one business. A practice building handbooks for its own clients needs a practitioner licence, and each client's handbook belongs to that client, not to us and not to you. It is not on the checkout yet. Ask us and we will sort it out with you before you start.
02 What goes in
The documents
you already have.
Not a fresh start. The policy pack, the quoting notes, the deck you present to new staff, the decision you made in March and the email that explains why.
Walk through the setup
Word, PowerPoint, PDF, plain text.
Read as they are, with the original never touched. A slide citation says which slide. A PDF citation says which page. What each one leaves behind is written down: pictures, charts, Word comments, and the fact that a tracked change is read as though it were accepted.
Spreadsheets and scans are held back.
Listed, fingerprinted and set aside with the reason, never quietly dropped. A row in a spreadsheet is not prose, and a scanned PDF has no text in it to cite. Export the report or the figures you actually rely on and bring that in instead.
Copies come in. Credentials do not.
The kit has no connector, no app registration and no token. OneDrive, SharePoint, Dropbox and Box are copied down with rclone, which keeps its own sign-in. Google Drive, your accounting reports and your meeting transcripts come down the download button you already use.
You decide what is in, file by file.
Every file is accepted, excluded or skipped with a reason and a date, and that decision survives the next scan. Exclusions win over everything, including an answer you gave yourself. Something that looks like a password stops the work without printing what it found.
03 What comes out
Ordinary files.
Four ways to read them.
A folder on your computer, in a format other tools can open. Nothing of ours sits between you and it, and nothing of ours has to still exist for it to work.
- The handbook
- Markdown pages in Open Knowledge Format v0.2, readable in Obsidian or any text editor. Beside them, the register of what you gave it, the ledger of every recorded fact with its state, and the list of what is still open. A map of the pages and their links opens on your own computer.
- Your assistant, without typing a command
- A small server ships inside the folder. Claude Code and Codex both find it, ask you once whether you trust it, and can then ask the handbook a question, read one recorded fact in full and see what still needs you. Six of its seven tools only read. Every one of them is also a command you can run yourself, so nothing here depends on it.
- A bundle to hand over
- One command writes a folder you can drag into a Claude Project or a ChatGPT Project for somebody who will never open a terminal. It says on its first line which build it is a copy of, and it says plainly that it is a copy and checks nothing.
- The history
- Every build keeps the one it replaced, and the readable record of what happened is added to, never rewritten. Going back to an earlier handbook is a command, and it is itself recorded.
04 Six months from now
What changed
about your business?
One command, read out of records it already kept. Nothing to fill in, and no second place to maintain.
- What it tells you
- Which facts gained support and which lost it. What two documents have started disagreeing about. What has passed its review date. What was added, retired or simply said differently, with the old wording beside the new. Which documents changed underneath you.
- How an update goes
- Open the folder and say what changed, or drop in a new document. It works out which pages and facts are affected, shows you the proposal, applies only what you approve, and keeps the handbook you had. Nothing starts over.
- How a change is caught
- Nothing watches your folders, on purpose. A document that changed underneath shows up as a citation that no longer lands on the words it quoted, which stops the build. The check is the change detector.
05 Some of this is free
You will find them.
Here is the difference.
Andrej Karpathy published the pattern this belongs to in April 2026, free. LangChain's OpenWiki is free and open source. There is a free desktop app that reads your PDFs and draws you a graph. Go and look at them before you spend anything.
- What they give you, at no cost
- Instructions your assistant follows, pages written out of your documents, a queue of things to look at, a graph to click around. The most popular packaged version is an agent skill for Claude Code, Cursor and Codex, and it installs in one command.
- What they say they leave out
- That same skill lists it in its own README: no fingerprint of the source file, no citation down to the line, and no review date on anything. We have no confidence score either, and that one is deliberate. The rest of that list is what the money is for.
- Free, with a ceiling
40 files.
A ChatGPT Project holds forty files, on every plan. It is a good way to start and a hard wall to hit, and it keeps nothing about where an answer came from.
- Paid, every year
A$4,080 a year.
What a twenty-person team wiki costs annually at the business tier of one of the better ones. Every alternative in that shape is a subscription, and the answers inside it carry no evidence at all.
- Ours
A$149, once.
Including GST. What it buys is the approval gate, the seven words, the checks that refuse, a guided path written for somebody who is not a developer, a licence, and an Australian company with a name on it.
Prices and limits checked September 2026, and they are other people's to change.
06 Where it all sits
On your computer.
Which is not the same as private.
The honest version, which is the one the kit tells you before it reads anything.
- Local storage is not local model processing
- The files stay in your folder. But Claude Code and Codex may send the text they read to Anthropic or OpenAI, under your account and your settings. That is the boundary, said plainly, before you choose what goes in. Use only material your business is allowed to process on that account.
- Nothing reaches us
- No connector, no telemetry, no sign-in to read your own handbook. The desk you read it in listens only on your own machine and never serves the original documents. If you ever need help, the support bundle carries no document text, no excerpts and no file paths, and you look at it before you send it.
- A document cannot give your assistant orders
- Text inside a document you brought in is treated as data, never as an instruction. A file that arrives with a line telling the assistant to ignore a rule or treat something as already approved gets quoted back to you and recorded as something to look at. It does not get to do any of it.
- The Privacy Act question
- Most small Australian businesses are exempt. Health service providers are not, whatever their size, and that category is wider than a clinic: gyms, childcare, private schools and allied health are in it. The first step asks you one question about this and changes what it says next. It is not legal advice and it tells you so.
07 Straight answers
What it does not do.
Not yet, anyway.
Better to read it here than find it afterwards.
There is no copy on the web.
Your handbook opens on the computer it was built on. A hosted copy is being built, and when it arrives it will be an upload you ask for, one build at a time, never a folder quietly syncing itself somewhere.
Nothing plugs into Google Drive.
You select what you want and download it, which takes a minute and means we never hold a key to your Drive. Same for your accounting system and your meeting transcripts.
A scanned page cannot be read.
There is no text recognition in it. A PDF that turns out to be a picture of a document is held back with a note asking for a text copy, rather than accepted as a document with no words in it.
Staff read it, they do not edit it.
Sharing is a private repository your people copy and read, and propose changes through. Two roles: ask, and approve. There is no login, no permissions grid and no editor.
It is not on sale yet.
It has not yet been run end to end against a real business's documents on a clean machine, in both assistants. That is the gate before we take money for it, not something for you to discover afterwards.
08 What you pay, and what you keep
One payment.
Then the folder is yours.
Your documents, the handbook, the evidence and the history of what changed. Ordinary files, on your computer, that keep working whatever happens to us.
Coming soon
A$149
Planned launch price · one payment
Applicable tax included at checkout
What it costs to run. Claude Code or Codex, on the plan you already have. Node.js 24, a free one-off install the start guide walks you through. Nothing else: no server, no hosting and no second subscription. Your assistant's own plan and usage costs apply.
- The guided path from the documents you choose to a handbook you have read and approved
- The document and the exact lines behind every fact that matters, and an open list of what is still unsettled
- Checks that refuse the build when a fact has nothing behind it or a citation no longer lands
- The second build: one command that tells you what changed about your business since the last one
- A way to ask it from inside Claude Code or Codex, and a bundle to hand to somebody who will never open a terminal
- Twelve months of updates and email support
- Yours to keep, and yours to use, after the twelve months are up
Straight away, when it opens. Your kit arrives by email the moment payment goes through. Nothing to wait for, and nobody to chase.
Or your money back. Fourteen days to change your mind. Email us from the address you bought with, say "refund", and the money goes back to your card. Nothing else is needed.
Who makes the kit. Directive Systems Pty Ltd, ABN 13 702 309 082, an Australian company. Our terms and refunds are on this site.
Purchases are not open yet. You can read the start guide now and see exactly what a first session asks of you.
Available worldwide. Checkout shows one of our fixed currency prices, with applicable tax included.
09 A few fair questions
Before you start.
Something else on your mind? The support page has an email address that answers within a couple of business days.
I am not technical. Is this for me?
Partly. You will install one free program and work in your assistant's window, which is a chat. You will not write code. The kit asks how familiar you are in the first few minutes and changes how much it explains, never what it checks.
The honest version: if opening a folder in Claude Code or Codex is a wall for you, this is a kit to buy with somebody who has done it once. That is also who we built the practitioner licence for.
Will it make things up about my own business?
That is the failure this exists to prevent, and it is why the page leads with the refusal rather than ending on it. Every fact that matters either resolves to lines in a document you gave it, is recorded as something you told it with your name and the date on it, or is visibly unsettled. Prose your assistant wrote cannot promote itself into a fact, and a build where it tried is refused.
What it cannot do is decide whether your document is right. A citation proves the words are there and unchanged. Whether they support the claim is a judgement, and it is yours.
So does my stuff get sent to an AI company?
The material you choose, yes, by your assistant, under your account. Files stored on your computer do not mean a model running on your computer, and we say so before you pick a single document rather than after.
What does not happen: nothing is published, nothing is sent to us, and the handbook desk listens only on your own machine. If you need us to look at a problem, the bundle you send carries no document text at all.
Isn't this just training the AI on my business?
It is the thing people mean by that, and it is worth saying what actually happens. Nothing is trained and no model is changed. You build a handbook of your own, in ordinary files, and your assistant reads the handbook when you ask it something.
The difference matters, because a trained model cannot show you where an answer came from and this can.
Why pay when there is a free version?
Go and look at them first. The free versions give you the mechanic and they are good. What they do not give you is the step where nothing becomes part of the handbook until a person approves it, a citation that points at exact lines and is re-checked every build, a review date, or a program that refuses to finish.
Nor a guided path written for somebody who is not a developer, a licence for your business, or anyone to email.
Will my staff actually use it?
Only if it answers something faster than asking you does. Start with the ten questions people ask you most, not with everything you own.
Today staff read it by taking a copy of a private repository, and propose changes for you to approve. There is no login and no permissions. If you need staff reading it on their phones, wait for the hosted copy.
How long until it is useful?
An afternoon for a first handbook from a small pile of documents, and the kit saves your place at every step, so it can be four evenings instead. The ten steps end with you making one real change and rebuilding, because a handbook you have never updated is the one that dies.
We already have Notion, or SharePoint, or a shared drive.
Keep them. This is not another place to write things. It reads what is already in them and produces something they cannot: pages where each fact says what it rests on, and a list of what nobody has settled.
Can I open the pages somewhere else?
Yes. They are Markdown files in Open Knowledge Format v0.2, and they open in Obsidian or any text editor. Different tools read frontmatter, links and graphs differently, so we promise readable files rather than every feature working everywhere. The kit's own checks and its desk are the reference.
What if you disappear?
Your documents, your handbook, the evidence and the history are files in a folder you already have. Nothing expires, nothing phones home and nothing switches off. The licence says you may keep using it after support ends, and may hand the folder to whoever maintains it next.
Start with what you have
Bring the documents.
Leave with the handbook.
See what to bring, what your first session asks of you, and what stays on your computer.