2026-10-12
Why everything we set up is yours to keep
A vendor sells you a hosted assistant — a service that runs on their side, not yours. It is well made, it answers well, and within a quarter it has changed its name, its price or its terms. What your organization put into it — its rules, its documents, its habits — leaves with it.
We install the same thing a different way, and we run it ourselves every day. The difference is not the software. It is where what you know lives, and who holds its keys.
Two words first
A language model is software that predicts the most probable continuation of a text. ChatGPT, Copilot and Claude are language models. It is not trying to be correct; it is trying to be probable. That is exactly why it needs rules around it, written by you.
Markdown is a plain-text format, readable by humans and by software alike (the specification). Git is a version control system that keeps every change with its author and its date (git-scm.com). A git repository holding markdown files is the only knowledge-base format that survives replacing whatever software reads it.
The models are disposable. Check.
This is not an opinion; the vendors document it themselves. OpenAI keeps a deprecation page where last year’s models are retired on a schedule. Anthropic does the same for Claude (model deprecations). An assistant tuned to a named model has to be tuned again every year, and the tuning belongs to someone.
So the question that matters is not “which model?”. It is: when the model changes, what remains?
What remains: three things
Markdown files, in a git repository of yours, governed by an AGENTS.md —
a plain-text file at the root of the repository that tells any agent (software that
reads and modifies your files) how to work with what is there. It is a simple, open
format, adopted by over 60,000 open-source projects: think of a
README written for agents rather than for humans.
The model is disposable. What is yours is not: the next model reads the same files, follows the same protocol, and nobody has to export anything.
The two halves of the argument
You own it. No export, no migration, no dependence on someone else’s dashboard. The day we stop, you keep the repository, the machines, the keys and the written protocol.
We run it ourselves. The same setup runs at noopsys every day: our knowledge base, our assistants, our rules. We do not recommend what we do not live in — and we answer “not yet” as often as “yes”.
Three questions for any vendor
Ask them before signing. The answers tell you whether you are buying a tool or a dependence.
- If you shut down, what remains on our side, and in what format?
- Where do our rules live — in our files, or inside your product?
- Can we read everything, export everything, and redo it all without you?
An honest tool answers each question in one sentence. A dependence answers with a paid migration plan.