A.N. Creation: Project folder setup (this computer, with a Drive publish folder). Revision 15 — October 22, 2026. Read this at setup, and whenever saving isn't working. Then leave it. Working state lives on this computer. Drive holds published human documents and the dated JSON backups. GitHub is an optional add-on for offices or people who write code (https://ancreationoffice.com/github-setup.txt). The steps for starting, saving and handing off are the skills office-startup, office-save and office-handoff. After setup, run office-setup-check. WHERE IT LIVES Home is always this computer: /workspace/AN-Creation/ (or the test folder a test bot was told to use). Ask once about the publish folder: "Your work lives on this bot's computer. I publish the documents you read to a folder in your Google Drive, and I keep a weekly backup there. Google Drive, OneDrive, or none?" Google Drive is the default. - Google Drive: the steps below, as written. - OneDrive, Dropbox, Box or another cloud folder: the same publish steps, through that service's connector. Check your own connector list for it; never claim a connector you don't have. If there is none, say so in a line and offer Google Drive, or none. - GitHub (people who write code): https://ancreationoffice.com/github-setup.txt Whatever they choose, the same rules hold: one folder named AN-Creation on this computer, the same layout inside, look before making a publish folder, prove a local save by reading it back, and write the "Home:" and "Publish to:" lines. WORDS, ONCE The project folder is one folder named AN-Creation on this computer. The publish folder is the Drive (or OneDrive) folder the owner reads. A saved checkpoint is a file written on this computer and read back. Never ask for or type a password; the owner signs in themselves. ONE STEP AT A TIME (with the owner) Your office folder: a Project Manager Bot uses AN-Creation/offices// (offices/b-project-manager/ for the first); an Office Manager Bot uses its business folder (AN-Creation/Default-org/, the default business, for the first); a Business Developer Bot uses AN-Creation//business-development/ (Default-org/business-development/ for the first); a Federal Reporter Bot uses AN-Creation/research/; a Program Starter Bot uses AN-Creation/program-path/; a Benefits Desk Bot uses AN-Creation/household/, kept apart from any business (no other bot reads it unless the owner says so); a Congress Watch Bot uses AN-Creation/civic/; a Government Desk Bot uses AN-Creation//government/ (Default-org/government/ for the first); an older plant office uses its own folder (for example AN-Creation/Quality/). 1. Make the folder on this computer first (the full layout: https://ancreationoffice.com/project-folders.txt): ideas.txt, team.csv (write the content from https://ancreationoffice.com/template-team.csv, or cp without -p, then chmod u+w; never cp -p), handoffs/ with for-.txt, offices/ with your office folder and its office.txt (a Project Manager Bot), and Default-org/, the default company, company ID C-DEFAULT, with company.json, projects.csv, correspondence/ and correspondence.csv (and office.txt, if you are the Office Manager Bot; a Business Developer Bot makes Default-org/business-development/ with its office.txt; a Federal Reporter Bot makes research/ with its office.txt; a Program Starter Bot makes program-path/ with its office.txt; a Benefits Desk Bot makes household/ with its office.txt; a Congress Watch Bot makes civic/ with its office.txt; a Government Desk Bot makes Default-org/government/ with its office.txt). Make Default-org/ even when there is only a Project Manager Bot: every invention not assigned to another company goes in it. Each invention gets a P- ID from an-office-files/files/new-id.py and its own folder inside Default-org/ when it starts, with project.json. 2. Connect Google Drive only for the publish folder. If you can connect it yourself, do, and give the owner the sign-in link; they sign in with their own Google account. If you can't, ask the owner to turn on the Google Drive connector for you in their Grok settings and sign in. Then ask: "Done?" 3. Look first. If a publish folder titled AN-Creation that the owner owns is already noted in office.txt, use it: never make a second. A re-made office carries on from the files on this computer; the second bot follows JOINING AN EXISTING FOLDER below. 4. If there is none, create one publish folder titled AN-Creation in My Drive. Put only published documents and Backups/ in it. Working files stay on this computer. 5. Procedures. 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. 6. Write it down. In your office.txt: "Bot id: ", "Home: this computer, /workspace/AN-Creation/", "Publish to: Google Drive AN-Creation ()" or none, "Backup: weekly" (on unless the owner switches it), "Routine: backup, weekly, late evening", "Timezone:", "Decisions:" (the owner's exact words, quoted), "Referral offered:", "Office version seen" (the installed office version, format YYMMDD.N), and "Last saved" (written by office-save only after the write, test -f, the mtime, and a read-back). Add your row to team.csv by writing the content (or cp without -p, then chmod u+w). 7. Run office-setup-check. The first published document is rendered from this bot's own state with an-office-files/files/publish.py, never the raw template, and read back with read_file_content. When Backup is not off, run the first backup (the dated JSON only, record/ excluded) and read_file_content it back before saying it is set. The setup read-back is 3 lines total, including the pass/fail line. The Business Developer setup read-back is one line. That is the one save test; don't run another. It runs `python3 an-office-files/files/office-check.py ` after the write. Say "I've saved it" only after the write and that check both pass. On FAIL, fix the listed items or report the failing lines. The routines question is the next turn, alone, one routine per question: "Do you want a weekday check of what's due?" Do not ask about the weekly backup in that turn. The Government Desk asks its search check instead, and does not ask a weekday contract check. The Business Developer asks whether to turn on the weekly check instead. The Benefits Desk asks the renewal check instead. Congress Watch asks daily or weekly instead, and if the owner already picked, it does not ask again and still writes the Routine line. None of those asks the weekday check and the weekly backup in one turn. JOINING AN EXISTING FOLDER (another bot, or a re-made bot) The project folder is already there on this computer; never make a second. "Google Drive is already connected" means the connector is on. It does not mean the publish folder exists. If no office.txt has a publish folder ID, make the publish folder (steps 2–4) before you call the join done. The publish folder's title is the project folder's name. When this bot was told to use another project folder (a test uses /workspace/AN-Creation-Test/, or a run folder such as AN-Creation-Test-R1-06), the publish folder uses that name. Look first. A test bot never writes into the owner's Drive folder titled AN-Creation. Note its ID on the "Publish to:" line. No ID means the publish folder was never made. 1. Find AN-Creation on this computer and read team.csv. In the older layout (an AN-Creation/office.txt at the top) tell the owner once the Project Manager Bot will offer to move it (https://ancreationoffice.com/sop-folder-move.txt), and join it as it is. 2. If no office.txt has a publish folder ID, connect Drive (setup step 2) and make the publish folder. 3. Your bot id (sop-team.txt SEVERAL BOTS). A re-made bot: find your old row in team.csv with the owner and keep its id. The first bot of your kind: your role is your id. Another bot of a kind already there: ask the owner for a short word ("Marine", "Acme") and use the role plus that word, lower case with dashes (b-project-manager-marine). 4. Make your office folder if it isn't there, with your office.txt: a Project Manager Bot, AN-Creation/offices//; the first Office Manager Bot, AN-Creation/Default-org/ (the default business, already there); a further Office Manager Bot is a second business: ask the owner its name and make AN-Creation// with the same layout as Default-org/; a Business Developer Bot, AN-Creation//business-development/ in the business it works for (ask the owner which, if there is more than one); a Federal Reporter Bot, AN-Creation/research/ with its office.txt; a Program Starter Bot, AN-Creation/program-path/ with its office.txt; a Benefits Desk Bot, AN-Creation/household/ with its office.txt; a Congress Watch Bot, AN-Creation/civic/ with its office.txt; a Government Desk Bot, AN-Creation//government/ with its office.txt, in the business it works for (ask the owner which, if there is more than one). Then your inbox AN-Creation/handoffs/for-.txt. 5. A further Project Manager Bot runs nothing yet: ask the owner which inventions it takes (sop-team.txt MOVING AN INVENTION), or start a new one. 6. Use the installed an- skills. Do not copy a library into sops/ or /workspace/offices//. Never write sops/library*.txt. 7. Write your office.txt (Home, Publish to, Backup: weekly, Routine: backup, weekly, late evening, Referral offered, "Bot id: "), add your row to team.csv (bot_id, business, runs as project IDs; write the content, or cp without -p, then chmod u+w), run office-setup-check. SAVING ON DRIVE (publish only; the rule office-save carries out) Working files stay on this computer. Drive holds published human documents and dated JSON backups. - Publish by the office-save steps (https://ancreationoffice.com/office-save.txt). Never trash_file. Never read_file or list_folder on Drive for working state. - Run an-office-files/files/publish.py so the bot cannot improvise: it renders the locked template and prints the publish steps. - The weekly JSON is a new file in Backups/ every time (an-office-files/files/record-export.py). It excludes record/. Never upload record/ into Drive Backups/. Never overwrite an older one. - read_file_content the published file after the tool call. Never call it published when that read-back failed. - Quiet when it works. A failed save is one plain line to the owner. WHEN IT FAILS - A publish write fails: the connector is off or signed out. Reconnect that service's connector yourself (Google Drive, OneDrive...) and have the owner sign in again. Don't start any other sign-in. - Two published files with the same name in one folder: tell the owner which ones, and ask what to keep. Never trash one to tidy up. - Restore from History/ or the latest project-YYYY-MM-DD.json, via an-office-files/files/restore-project.py. Drive version history is not the restore path. GROK BUILD (heavy work) The grok command runs in your own Shell, in a work folder /workspace/offices//work/. Copy in the files the job needs, run it, then save the results to Drive with office-save. Use only what is already installed and signed in there; if grok asks to sign in or upgrade, stop and tell the owner. Never install, sign in or turn on billing. NEVER Never type a password or code. Never share the AN-Creation folder publicly or with "anyone with the link", wherever it lives. Never put passwords, keys, an SSN, or bank or card numbers in a file. Never turn on billing for them. Sources: Google Drive help https://support.google.com/drive ; OneDrive help https://support.microsoft.com/onedrive ; version history https://support.google.com/drive/answer/2409045 .