A.N. Creation backups and version control. Revision 12 — October 22, 2026. Human page: https://ancreationoffice.com/version-control.html Working state lives on this computer. Drive holds published human documents and dated JSON backups. GitHub stays a full, supported option for offices or people who write code; offices already on GitHub keep working as written under IF THIS OFFICE USES GITHUB. WHY AI is new, and it goofs up: a file gets overwritten, two versions get mixed, a chat gets cleared, a bot gets deleted. In practice, going back to an earlier version is close to a daily event. So the office never depends on one copy of anything, and never on the chat. HOW IT'S KEPT - The project is one private folder, AN-Creation, on this computer (https://ancreationoffice.com/drive-setup.txt). office.txt says "Home: this computer, /workspace/AN-Creation/" and "Publish to: Google Drive ()" (or OneDrive, or none). If it says "Home: GitHub", follow IF THIS OFFICE USES GITHUB below instead. No Home: line yet (offices set up before 261014.2): GitHub if /workspace/offices//an-creation is a git clone, otherwise this computer; write the Home: line at the next save. - The procedures are the installed an- skills (the plugin). There is no library file to download, copy, or keep in AN-Creation/sops/ or in /workspace/offices//. Never write sops/library*.txt. An update is the owner installing the newer plugin (version.txt UPDATING). The rule is https://ancreationoffice.com/version.txt - Two kinds of files (D-029). Working files are updated in place: office.txt, business.txt, plan.md, actions.csv, team.csv, the hand-off inboxes, Status and Plan. Before a major change to one, a dated copy goes to History/ (" YYMMDD-HHMM"). Records and outputs are never edited once saved: documents, drawings, pages, analyst runs, record/ entries, released revisions. A change is a new dated file. - The record. Every conversation and every analyst run is saved in record/ and sessions/. Anything not yet saved is only in the chat. Say it to the owner once, in a line: "Your work is saved on this computer as we go, and I keep a dated copy before any big change. The documents you read, and a weekly backup, go to your Drive folder." SAVING (every office and b-analyst) Follow the office-save skill. This is the office rule it carries out. - Read a working file fresh just before you change it, then write it in place (same name, same folder). - Before a major change, keep a dated copy in History/ (a copy: the original is never moved, renamed or replaced; then update the original in place). - After every write, check `test -f` and the mtime, then read the file back and check it matches. A write you did not check is not confirmed. Never say it is saved before that. - Quiet when it works. A failed save is one plain line to the owner. Never call it saved when the read-back failed. A read-back is at most 3 lines. - Every save rewrites office.txt "Working on" in one line in that same save. - "Last saved", only after the write, the check, and the read-back: the clock from `date` in the owner's Timezone, , read back OK. Never a future time. On GitHub the id is the commit. Never write that line when the read-back failed. - Files over about 50 MB: leave them where they are and record where the original lives. Setup: https://ancreationoffice.com/drive-setup.txt IF THIS OFFICE USES GITHUB (code offices, and offices already set up on GitHub) - Your own clone: /workspace/offices//an-creation. Never a shared clone, and never /workspace/repo. The GitHub connector is read-only; saving is git and gh in your Shell. - One commit per turn. pull --rebase before the commit; if the push is rejected, pull --rebase and push again. After the push, read the file back with gh. Unpushed work is not saved. - Never force-push main. A work branch is named by role (b-project-manager/) and deleted after it merges. - The procedures are the installed an- skills. An update is a plugin install, not a download of a library file. Never write sops/library*.txt. - "Last saved" uses the commit in place of a Drive file id, and only after the gh read-back matches. Files over about 50 MB stay out of the repository. Setup: https://ancreationoffice.com/github-setup.txt IF SOMETHING GOES WRONG - A file got overwritten, mixed up or deleted: restore from History/ or the latest project-YYYY-MM-DD.json, via an-office-files/files/restore-project.py. Find the last good version, restore it as a new save, and say what was restored. - A chat got cleared, or a bot was deleted and made again: everything that was saved is still there. The new bot looks for the AN-Creation folder first, reads its office.txt (its "Last saved" line), projects.csv, project.json, plan.md and the latest published status, and carries on from the last saved checkpoint. Anything said after the last save was only in the old chat: ask the owner about it. - They lost their phone: the published documents and the weekly JSON backups are in the Drive publish folder. Working state is on this computer. NEVER - Never share the AN-Creation folder publicly or with "anyone with the link". Never make a GitHub repository public. - Never put passwords, keys, an SSN, or bank or card numbers in any project file, issue or commit message. - A saved version is not an approval. History does not replace the revision and change records (sop-change-control.txt) or the record of what was sent to whom. - Big CAD, video and image files (over about 50 MB): record where they are. Sources: Google Drive version history https://support.google.com/drive/answer/2409045 ; GitHub repositories https://docs.github.com/en/repositories/creating-and-managing-repositories/about-repositories ; file history https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file ; large files https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github .