# Why everything we set up is yours to keep

2026-10-12 — https://noopsys.com/en/blog/why-you-keep-everything/

Language models change every few months. Your files, your rules and your protocol do not.

<p>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.</p>
<p>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.</p>
<h2 id="two-words-first">Two words first</h2>
<p>A <strong>language model</strong> 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.</p>
<p><strong>Markdown</strong> is a plain-text format, readable by humans and by software alike (<a href="https://daringfireball.net/projects/markdown/">the
specification</a>). <strong>Git</strong> is a version
control system that keeps every change with its author and its date
(<a href="https://git-scm.com/">git-scm.com</a>). A git repository holding markdown files is the
only knowledge-base format that survives replacing whatever software reads it.</p>
<h2 id="the-models-are-disposable-check">The models are disposable. Check.</h2>
<p>This is not an opinion; the vendors document it themselves. OpenAI keeps a
<a href="https://platform.openai.com/docs/deprecations">deprecation page</a> where last year&rsquo;s
models are retired on a schedule. Anthropic does the same for Claude
(<a href="https://docs.anthropic.com/en/docs/about-claude/model-deprecations">model deprecations</a>).
An assistant tuned to a named model has to be tuned again every year, and the tuning
belongs to someone.</p>
<p>So the question that matters is not &ldquo;which model?&rdquo;. It is: <strong>when the model changes,
what remains?</strong></p>
<h2 id="what-remains-three-things">What remains: three things</h2>
<p><strong>Markdown files</strong>, in <strong>a git repository</strong> of yours, governed by an <strong><code>AGENTS.md</code></strong> —
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, <a href="https://agents.md">adopted by over 60,000 open-source projects</a>: think of a
README written for agents rather than for humans.</p>
<p>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.</p>
<h2 id="the-two-halves-of-the-argument">The two halves of the argument</h2>
<p><strong>You own it.</strong> No export, no migration, no dependence on someone else&rsquo;s dashboard.
The day we stop, you keep the repository, the machines, the keys and the written
protocol.</p>
<p><strong>We run it ourselves.</strong> 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
&ldquo;not yet&rdquo; as often as &ldquo;yes&rdquo;.</p>
<h2 id="three-questions-for-any-vendor">Three questions for any vendor</h2>
<p>Ask them before signing. The answers tell you whether you are buying a tool or a
dependence.</p>
<ol>
<li><strong>If you shut down, what remains on our side, and in what format?</strong></li>
<li><strong>Where do our rules live — in our files, or inside your product?</strong></li>
<li><strong>Can we read everything, export everything, and redo it all without you?</strong></li>
</ol>
<p>An honest tool answers each question in one sentence. A dependence answers with a paid
migration plan.</p>