Switching tools should not mean starting from scratch. When context is locked inside a conversation, each new session requires rebuilding decisions, preferences and the state of the project.
A knowledge base solves part of that problem: files preserve the work, while assistants help interpret it and carry it forward.
The knowledge stays. The tool can change.
Projects, decisions and lessons need a place of their own. Procedures, settings and integrations belong to the layer that lets assistants work with that knowledge base.
This separation guides our structure: IA Trabalho and IA Configuração. The goal is to keep a single source of truth in common file formats, without creating a separate version of the knowledge for each tool.
The file holds the context. The conversation moves the work forward.
ia-trabalho/
projetos/
conhecimento/
passagens/
ia-configuracao/
skills/
agentes/
integracao/This map summarizes the separation of responsibilities; it is not an instruction to rename existing folders. Compatibility depends on how each assistant finds the files.
Three records that help you pick up the work
- Context: what the project is, its limits and the decisions already made.
- Procedure: how to perform a recurring task and verify the result.
- Handoff: what has been done, what remains and the next concrete step.
Organization needs verification too
Sharing files does not mean every AI tool will load them automatically. Each tool’s access and instructions need to be checked. The same applies to backups: a locally saved file is only protected on the remote once the upload is confirmed.
A useful structure lets you resume a project without relying on the memory of a single conversation.
Draft for Davi Wallace’s review. This article is part of the website proposal and has not been published yet.