Why TomaTío
With its structure, rules and history intact, and only the parts you choose. No AI provider has a reason to build that for its competitors, so it has to be an open standard. That, delivered by the hosts people already use, is TomaTío.
Three things together
Portable
The Portable Context Protocol (PCP), an open standard, carries a team's whole working context between tools and hosts, a piece at a time if you want.
Distributed
A WordPress plugin, so it runs on the software behind over 40% of the web, and reaches teams through the hosting companies they already pay.
Open
Nobody can close it later, and a host that builds on it adds to it rather than competing with it.
Portability, compared
| AI provider export | RegulationGDPR Art. 20, Data Act, DMA | PCP | |
|---|---|---|---|
| What moves | A dump: chat transcripts, a flat list of “memories” | Data you provided, in a machine-readable format | The working context: memories, approved knowledge, procedures and house rules, scopes, documents and handoffs, with their history |
| Structure | Each provider's own shape | Not specified | One open schema with a manifest, hashes and counts, checked by a conformance suite |
| Granularity | All or nothing | All or nothing in practice | By scope: one project, one team, work apart from personal |
| Import | None: nothing on the other side reads it | Not required | Defined: migrate a whole brain, move chosen scopes into one already in use, or import as proposals a person reviews or as reference material, never a blind merge |
| Trust and history | Lost | Not covered | Who wrote what and what was approved travels with it, along with the audit log |
| Deletion | Separate, unverifiable | A right, without proof | Erasure receipts and tombstones, carried in every archive |
| Interoperability | None | Encouraged, rarely achieved | The point of the protocol: an open specification and a conformance suite, so any tool can implement it |
Bill of Rights
Export with PCP, which makes these true, is live on every brain since 28 October. The promise goes in writing with the invite-only beta; see the roadmap.
Why it matters
Whoever holds the working memory of people and organisations (what they know, how they work, what they decided) holds a moat. Switching gets harder, alternatives starve, and customers lose their leverage.
An open, structured, importable format that any tool can implement works directly against that concentration.
Each agent sees only its scopes. Every action is attributed to the agent and the person behind it, a person approves what becomes shared knowledge, and everything is in an audit log.
As agents act for teams, that is how teams keep control, and PCP makes that control portable too.
When an agent writes most of what a team knows, “the AI said so” is not enough. Every change records who made it, from which tool and on whose behalf, and agents can cite what they used.
That history travels in every export, so trust moves with the context instead of staying behind.
Where it's going
The order is firm; the dates are proposals.
Next · beta ~7 Nov
The code public on GitHub under the GPL, with guides for every step and a short explainer video. A few founding teams get private brains of their own, free.
Launch · ~23 Nov
From a zip on ordinary WordPress hosting to a brain connected to your AI in under 10 minutes, kept up to date by itself. Hosting companies can offer it with their plans.
After launch · Dec onwards
We use it ourselves
Our roadmap, backlog, decisions and each person's daily task list are pages in a brain of our own, written by us and our agents, with every change attributed.
The public roadmap is a summary of that working roadmap.
On 28 October we moved all of it off the public demo onto its own server with the same migration tools every team gets: memories, knowledge, documents and pages, with their versions and data.
What broke on the way, we fixed in the product, so the next team doesn't hit it.
