The Continuity Layer Protocol

Why it's built this way — and it isn't a technical limit

It's worth pausing to ask why a memory built this way became the standard. It isn't an engineering difficulty: writing a text file, re-reading it and letting you correct it is among the simplest things a computer can do. If they don't give it to you, it's a product decision. And the premise of that decision is about you.

The premise is that it isn't worth handing you the wheel: that deciding what your AI should remember is too complicated, too tedious, or something you wouldn't do well anyway — and that it's better if the system decides in your place, without asking. It's a judgement about your competence, taken for granted and never said out loud. The same person who isn't trusted with the choice of one line of text is considered perfectly capable of entering their credit card details.

And that judgement has a convenient consequence for whoever made it. Every month that passes, a memory you didn't write and can't reuse elsewhere without redoing it becomes one more reason to stay. That isn't an unfortunate side effect: it's the mechanism. The more your history accumulates on their servers in a format that is only theirs, the less free you are to change — and the cost of leaving is paid by you, not by them.

Underneath there's an economic reason too, and it's no mystery: a real memory — re-read, weighed and taken into account in every single answer — devours compute. A handful of fragments doesn't. Giving you the complete tool would cost them; giving you the shortcut costs you, but in a way that doesn't appear on an invoice.

The proof is in data export itself

And if this looks like reading intentions into things, look at data export itself: it's there where a law requires it and missing where that law never arrived. In Europe the GDPR has made it mandatory since 2018, and similar rules exist in Brazil and China. In the United States there's no federal law: the right depends on the state you live in, about twenty recognise it and the others don't. In India it was written into the 2019 draft and vanished from the approved text. Same company, same technology, different rights depending on your address.

And the direction of the contagion is clear. Europe imposed the rule first, in 2018, and the rest came after: partly because keeping two different standards costs more than applying one, partly because those who legislated later traced that model — scholars call it the «Brussels effect» — and partly, simply, so as not to be left as the ones holding customers hostage while everyone else had stopped. It wasn't a change of heart: it was a market large enough to dictate a rule, and everyone else falling in line. Except that the loophole travelled with the rule: wherever that right arrived, it arrived as a right to a copy — never as an obligation to make it genuinely reusable elsewhere.

Someone will object that in practice they offer the export to everyone — and that's true: building it once costs less than switching it on and off per jurisdiction. But a feature granted isn't a right: where no law requires it, the day it disappears you have nothing to appeal to. And above all, look at where the effort stopped. The rule asks for a copy in a structured, machine-readable format; on direct transfer to a competitor it settles for «where technically feasible». The file, which they were obliged to give you, they give you. The way to reuse it, which nobody obliged them to build, they don't.

And that is exactly where IllAIra comes in: that way of reusing it is precisely what we're building. A format that holds over time, that doesn't expire with a subscription and that stays as simple as possible without ceasing to work — because something that works but nobody can use is no use, and something easy that breaks at the first change of engine is even less. To understand what someone really wants, look at what they do where nobody is forcing them: they stopped where the obligation ended, we started from there.

And if you want the sharpest example of why all this matters, go back to India: over a billion people from whom that right was removed from the text before it became law. There's no rule to invoke there — if tomorrow the provider decides to stop giving you the archive, there's nobody to ask. It's the clearest demonstration you could have: as long as your memory depends on a concession, your freedom depends on the country you were born in. A file that is already yours from day one isn't a stylistic preference — it's the only protection nobody can take away with an amendment.

So the question, at this point, is no longer technical: are you really incapable of deciding what your AI should know about you? Everything you'll read from here on starts from the opposite answer.