One file
Facts and standards in a single document. Works in any chat window.
Starter Kit
The AI Operating System Starter Kit
Build the layers that persist: the facts, standards, and checks your AI tools read before they draft, at whatever level your tools allow.
What this solves
The prompt resets. The system persists.
Most people improve their AI results by rewriting prompts. That works for a while and then stops, because the prompt is only one of the layers that produce the output, and it is the one that resets every time you close the window.
This kit builds the layers that carry over: your verified facts, how output should read, what never goes out, and the corrections you refuse to make twice.
Pick your level
Which level depends on the tool, not your skill.
A folder
Separate files for facts, standards, boundaries, and rulings. Point a project or connector at it.
Routing
An index that loads the right files for the work at hand. Needs a tool that reads files on demand.
Checks and automation
Rules that run before you read a draft, and a gate before anything goes out. Needs a tool you can configure.
Levels 1 and 2 are where most of the gain is. Levels 3 and 4 compound it.
The basic workflow
Decide once, write it down, let it apply.
- Write one file. Your verified facts and your standards, pasted into whatever tool you already have.
- Grow it into a folder. Facts, standards, boundaries, and a rulings log kept as separate files so each can be maintained.
- Add routing. An index that decides which files load for which kind of work, so nothing gets diluted.
- Add checks and automation. Mechanical rules that run before you see a draft, and a gate before anything goes out.
- Keep it clean. Audit for conflicts, staleness, and bloat, because context does not stay accurate on its own.
What you end up with
A small system your tools read before they draft.
ai-os/
05-routing.md
01-facts.md
02-standards.md
03-boundaries.md
04-rulings-log.md
06-checks.md
advanced/
automation.md
keeping-it-clean.md
example/
worked-example.md