💾 Backup and version control: protecting your assistant’s home

Your assistant’s folder isn’t an ordinary folder. It’s its home — where the CLAUDE.md (the brain with its permanent instructions, covered in module 0.4), the context notes it has accumulated, the preferences you adjusted phase by phase (Home, Life, Hands, Growth), and the decisions recorded over months. Losing that folder doesn’t mean losing “a few files”: it means losing an entire employee you trained with time and attention.

Think of the opposite of hiring someone and, three months later, that person getting hit on the head and forgetting everything they learned about your routine, preferences, and house rules. That’s rare with a human employee. With a folder of files on an ordinary laptop, it happens much more often than you might think—a corrupted hard drive, cloud sync that overwrites files, accidental deletion during a disk cleanup.

New here? You already used versioning without knowing the name: in Google Docs, every change is saved in a “version history” — you can open the document as it was yesterday or a month ago, and revert if something went wrong. Version control is exactly that, but for an entire folder of files: a system that saves every change, with the date and a summary of what changed, so you can roll back when you need to.

The tool most commonly used for this is called git — a version control (the technical name for the category). You don’t need to understand the engineering behind it: what matters is the concept—each time you “save a milestone” (this is called commit, a snapshot of the folder at that moment), git keeps that snapshot forever. If a context file gets messy, you can look at earlier snapshots and restore the good version.

Caption: each green dot is a commit — a saved snapshot of the folder on that day. If something breaks after “today,” you can return to the highlighted recovery point without losing everything that came before.

New here? Backup is just a backup — a second copy of the entire folder stored somewhere else, locally (on an external hard drive, for example) or in the cloud (an online storage service like Google Drive or Dropbox). It solves the "everything disappeared" problem: if the computer breaks or the original file is deleted, you have a copy to recover from.

Git version control is something else, and the two complement each other. A backup restores the entire folder after a total disaster; git gives you a line-by-line history—the “what changed and when” inside context and decision files, even if nothing has “disappeared.” Having only backups and never using version control is like having fire insurance but no way to know what you changed yesterday. Having only git and never backing up off the machine means trusting that the drive will never die—it will, sooner or later.

Caption: the folder at the bottom is the asset; the backup (middle) protects against “everything disappeared”; the version history (top) protects against “something changed and I don’t know what” — together, the two layers cover both risks.

You don’t have to know the terminal by heart to do this — Claude Code itself can configure both layers for you if you ask clearly. The steps below assume no prior knowledge.

Configure backup e versionamento para a pasta deste assistente.

Objetivo: proteger tudo que está aqui (CLAUDE.md, contexto,
decisões) contra perda, com duas camadas.

1. Inicialize um repositório git nesta pasta, se ainda não
   existir, e faça um primeiro commit com tudo que já está aqui.
2. Crie um arquivo .gitignore básico (excluindo segredos, chaves
   de API e arquivos temporários — nunca versionar credenciais).
3. Sugira um comando simples que eu possa rodar toda semana para
   salvar um novo commit ("checkpoint semanal").
4. Explique, em português simples, como eu faço uma cópia de
   segurança desta pasta inteira em <meu HD externo ou serviço
   de nuvem> (troque pelo que eu realmente uso).
5. Ao final, me diga como eu confirmo que o histórico de versões
   está funcionando (que comando roda para ver o histórico).

Backup and version control only work if they become routine — configuring them once and never touching them again is almost as bad as having nothing. The frequency below is INEMA’s recommendation for a folder used by an active assistant.

Most data disasters aren’t caused by a lack of tools — they come from a bad habit. The two pairs below cover the most common mistakes INEMA sees at this stage of the course.