Keep experience outside one model
A model upgrade should not require re-entering every project decision. Keeping durable context outside the model lets supported tools draw on the same stored experience.
That requires capture, retrieval and identity wiring in each tool. An open interface is not automatic compatibility with every application.
What can leave thinqOS
Mind exports support a signed .tqmind archive and open representations: JSON-LD, YAML-LD and a Vault-LD Markdown folder. These encode selected Mind data in forms that other software can inspect.
Test an export with your own records. Check identifiers, relationships, sources and included layers before relying on it for an exit plan.
What an export does not recreate
A data file does not reproduce the ranking logic, runtime, permissions, credentials or integrations that made an agent work. Another system may understand some fields and ignore others.
The cognition implementation remains part of the product. Portability should be judged by what you can actually recover and use, not only whether a download exists.
Connections are a separate layer
MCP connects capabilities and data. A2A supports agent-to-agent interaction. Export formats carry stored information. These solve different parts of moving work between systems.
Choose the interface for the job and verify both sides. Standards reduce unnecessary dependence; they do not erase every migration cost.