A.N. Creation project folders. Revision 20 — October 22, 2026. Human explanation: https://ancreationoffice.com/project-folders.html One person talks to the system: a solo inventor or entrepreneur. Partners may be involved, but their input comes through that person. One folder holds everything, on the bot's computer. Inside it, one folder per company, and inside each company, one folder per invention, fully self-contained. Everyone starts with one, the default company (Default-org/, company ID C-DEFAULT); an invention not assigned to another company goes there. Built like a Unix system: files and folders do the work. A queue is a folder of ticket files. Home is always this computer. Drive is publish-only: one folder per project, human documents plus Backups/, each document published by the office-save steps (https://ancreationoffice.com/office-save.txt). Layout: AN-Creation/ shared by every bot, on this computer (no sops/ library) the procedures are the installed an- skills. Never write sops/library*.txt, and never keep a library in /workspace/offices// team.csv every bot: its name, its bot id, its business, and the project IDs it runs (https://ancreationoffice.com/sop-team.txt) handoffs/ one inbox per bot, for-.txt. Sending follows the office-handoff skill (https://ancreationoffice.com/sop-team.txt HAND-OFFS) offices// one small folder per Project Manager Bot: its office.txt (Home, Publish to, Backup, Referral offered, "Office version seen", "Last saved", "Working on") and its notes. offices/b-project-manager/ for the first ideas.txt parked ideas for every business, one line each with the date; not projects yet AGENTS.md, CLAUDE.md (GitHub add-on only, at the top of the repository) how any AI finds the ticket it was sent to work on, from one line; https://ancreationoffice.com/agents-md.txt Default-org/ the default company, made at setup even when there is only a Project Manager Bot. Company ID C-DEFAULT. Every invention not assigned to another company goes here. A second company gets its own folder beside it. Each company's Office Manager Bot works in its folder (business-manager.txt). In the procedures, AN-Creation// is the folder of the company at hand, Default-org/ unless the invention is in another company.json company ID (C-xxxxxx), name, name_history company.csv business-plan.csv deadlines.csv expenses.csv ... company-level only. Ledger rows carry project_id and are rollups of the project's own rows projects.csv the index: project_id, folder, status, run_by office.txt that Office Manager Bot's office file correspondence/ company-wide correspondence only (sop-correspondence.txt). Project correspondence lives in that project's folder correspondence.csv its index, a row per folder Fishing Lure/ one folder per invention, fully self-contained. Project ID assigned once (P-xxxxxx), never from the company or project name project.json project ID, company_id, the record (schema.json), documents[], moves[] drive-ids.csv published file IDs for this project Office files/ the assistants' side. Everything about this project, relative paths only. Links between records use IDs, never folder names. README.txt PROJECT.txt plan.md actions.csv the action log master: one row per action or suggestion, never deleted (sop-action-log.txt, sop-suggestions.txt) cost-sheet.csv what one unit should cost, every component, tooling separate (sop-cost-sheet.txt) risk-table.csv how it could fail, scored down to the residual (sop-risk-table.txt) decision-log.csv everyday calls, dated, with the reason (sop-decision-log.txt) project-charter.txt scope, success criteria, milestones, budget; changed only by ECN (sop-project-charter.txt) schedule.csv schedule.html the charter's dates, forecasts and slips, and the critical path (sop-schedule.txt) spending.csv what the project has spent, and whose money (sop-spending-register.txt) ecn-log.csv ecn/ engineering change notices (sop-change-control.txt) forms/ master forms: answer, context, status for every field queue/QUEUE.txt open/ active/ done/ revisit/ record/ the bots' conversations: YYMMDD-NN-R-slug (received), YYMMDD-NN-S-slug (sent), YYMMDD-NN-M-slug (conversation, full text) record/INDEX.csv one line per record item: date, type, summary, fields touched, status forms/INDEX.csv one line per form: what it covers, status counts, last change mirror/ text pulled once from each record item sessions/YYMMDD-HHMM-slug/ one per analyst run: prompt, notes, result, DONE.txt archive/ business/ this project's business work (funding packet, patent work, project correspondence, project expenses). The project's own copy is the master, so a move strands nothing History/ earlier copies of working files, dated. Never published. Publish to Drive (one folder per project; not working state): documents from the locked templates (status, action log, charter, and the rest in files/templates/), each published by the office-save steps (https://ancreationoffice.com/office-save.txt). Backups/ the dated JSON only (record/ excluded), project-YYYY-MM-DD.json, never overwritten. Never upload record/ here Only the project lives here. The procedures are the installed an- skills, not a file in sops/. Never write sops/library*.txt. A template copied in to be filled out (a form, the plan) is a project file from then on: write the content (or cp without -p, then chmod u+w), dated, and never overwritten by a newer template. Source of truth: Office files plan.md, forms/ and record/, and project.json. Published documents are produced from them, so they can be rebuilt at any time. Dated folders. Nothing made for you is written over. Each analyst run works in its own dated folder and leaves it as it was. Each page, picture, render, drawing and timeline goes in its own dated folder; an update is a new folder. Before a working file is regenerated, a copy of the old one goes to History/; the file itself keeps its name and is updated in place. Your format. At setup b-project-manager asks whether you want plain pages (Markdown, readable on a phone) or Word and Excel files you download. Published documents use that format. Office files use whatever suits the assistants. PDF only for things sent out or kept as issued. You can change your mind; the files are regenerated. The record, two ways. Office files keep everything as received, including full meeting and conversation transcripts. Published documents keep the same dated events in readable form: the email, the document, and a typed-up summary of each meeting or conversation instead of the transcript. Your edits. Owners send changes in chat or as an attachment, and the bot files them locally. The bot does not list Drive for files the owner changed, and does not pull Drive edits in. Send to the office. That folder is local intake: anything the owner drops in chat or attaches is filed into the record. Identical content to something already filed is a duplicate: note where the first copy is, no new task. Changed content is a new version: keep both and check any changed numbers. The queue. A ticket is a file. Its folder is its status: open, active, done. revisit/ holds "for now" answers named by the date to ask again (261013-company.txt). On that date the file moves to open/. Analyst runs. Each run works in its own dated folder, writes DONE.txt when it finishes, and is never renamed. Finished runs older than a month move to archive/. Several inventions. Each has its own folder, plan and queue, inside its company. One b-project-manager can run them all (inventions are folders, not bots); it names the invention it's on and files each conversation in that invention's record. Starting a parked idea: it goes in the default company (Default-org/, C-DEFAULT) unless the owner names another (and which Project Manager Bot runs it, if there is more than one); run an-office-files/files/new-id.py P, set up its folder, project.json, PROJECT.txt ("Run by: "), intake form and first ticket before saying it has started; add it to that company's projects.csv with who runs it; mark the idea started in ideas.txt. Answers never cross between inventions. A fact that applies to two, such as your company, is recorded in each, with its source. team.csv runs lists project IDs. Several bots. More than one Project Manager Bot can share the folder, each with its own inventions (for example one for garden tools, one for marine), and each company has one Office Manager Bot. Who runs what is in team.csv, each project.json and projects.csv. A bot changes only its own inventions; it can read the others. Adding a bot, moving a project between companies, and adding a second company: https://ancreationoffice.com/sop-team.txt SEVERAL BOTS. Moving a project to a new company: first ask to create the company, then run an-office-files/files/move-project.py. A company rename is an-office-files/files/rename-company.py. Drive is only republished. The older layout. Folders made before October 18, 2026 had the inventions, correspondence/, correspondence.csv, All inventions and the Project Manager Bot's office.txt at the top of AN-Creation/. They move once, with the owner's yes: https://ancreationoffice.com/sop-folder-move.txt . Until then the bot works with them where they are. Where it lives. One private folder named AN-Creation on this computer, with this layout inside. office.txt says "Home: this computer, /workspace/AN-Creation/" and "Publish to: Google Drive ()" (or OneDrive, or none). The procedures are the installed an- skills. Never write sops/library*.txt and never keep a library in /workspace/offices//. office-save proves a write by reading it back. For offices or people who write code, the same AN-Creation/ can live in a private GitHub repository named an-creation instead, with one clone per bot at /workspace/offices//an-creation (https://ancreationoffice.com/github-setup.txt). Backups. Records and outputs are never edited once saved (a change is a new dated file or folder); working files like plan.md are updated in place. A dated copy goes to History/ before any major change. The weekly JSON (an-office-files/files/record-export.py) is the restore path, with History/. Going back to an earlier version is a normal part of working with AI. See https://ancreationoffice.com/version-control.txt Move and restore. Run an-office-files/files/move-project.py / an-office-files/files/rename-company.py on this computer. Drive is only republished. If something goes wrong, restore from History/ or the latest project-YYYY-MM-DD.json, via an-office-files/files/restore-project.py. Template. https://ancreationoffice.com/plan-template.txt contains a blank plan. Do not replace an existing plan with a blank one.