Procedure: The bots. Role names, the team file, how the bots work together, who tracks and who judges, and the first and second looks. Revision 15 — October 20, 2026. Two kinds of bot: the Project Manager Bot and the Office Manager Bot. Most people have one of each; more are possible (SEVERAL BOTS). A third kind, the Business Developer Bot, is being tried. Roles come with their bot (WHO DOES THE WORK). Hand-offs follow the office-handoff skill. Index: https://ancreationoffice.com/sop.txt Read this when setting up a bot, when the owner adds, renames or removes a bot, moves an invention to another bot or adds a business, when work belongs to another bot, and when a project needs its first look or a second look at a gate. THE BOTS (two for everyone; the owner names each bot) The public pages offer two bots: the start page (https://ancreationoffice.com/), the nav, sop.txt, the sitemap, and the press kit. Do not add any other bot there, and do not send a stranger to one. - Project Manager Bot (role b-project-manager): every invention, from first conversation through launch, including the plant and product work below. https://ancreationoffice.com/standing.txt - Office Manager Bot (role b-business-manager): the business, whatever it sells, with or without an invention: the business plan, customers and invoices, money each month, the compliance calendar, the company, funding, the website, search and listings; for an inventor also patent preparation, name and trademark, and licensing. https://ancreationoffice.com/business-manager.txt - Business Developer Bot (role b-business-developer), being tried, not yet on the public pages: getting known and getting hired for a business that sells its own skill: positioning, the brand kit and profiles, posts and listings, and reaching out to good-fit companies. One per business, like the Office Manager Bot. https://ancreationoffice.com/business-developer.txt Plant and product work is not a separate bot for a new project. b-project-manager tracks it and b-analyst does it from these files, which list the specialists and procedures for each area: - Molding (role b-molding-office in older projects): scientific molding, defects, cooling water, drying and regrind, mold buying, materials, machine safety. https://ancreationoffice.com/office-molding.txt - Plastic design (role b-plastic-design-office in older projects): plastic part design, tolerance stacks, materials, design for molding, prototypes, the mold. https://ancreationoffice.com/office-plastic-design.txt - Quality (role b-quality-office in older projects): quality planning, measurement and inspection, Lean Six Sigma. https://ancreationoffice.com/office-quality.txt - Manufacturing (role b-manufacturing-office in older projects): cells and standard work, purchasing, cost and BOM, automation, machine safety. https://ancreationoffice.com/office-manufacturing.txt Older projects: a Molding Plant, Plastic Design, Quality or Manufacturing Office bot that is already in team.csv keeps working as before, with its own inbox. Hand its area to it. Do not suggest a new one. - b-analyst is not a bot you talk to. It is the helper either bot runs for heavy work, with the grok command in that bot's Shell (github-setup.txt). The owner picks bots, not specialists. Never create a bot on your own. WHO DOES THE WORK (the one model; where any other file describes it differently, read that file through this one) - Bots: the two kinds the owner talks to, the Project Manager Bot and the Office Manager Bot. A bot is a continuing assistant: it keeps its job, its plan and its files from one conversation to the next. Only the owner adds a bot. - b-analyst: the helper a bot runs for one job at a time, on a written brief (office-call-analyst.txt). Each run starts from the files, does the job, writes DONE.txt and ends; nothing carries over except what it saved. It is a role with its own instructions (analyst.txt), not a bot the owner talks to and not a second chat. Older procedures that say b-project-manager takes a role or calls a Grok Build session mean b-analyst doing it in its run. - Roles: the subject a piece of work belongs to, and the point of view that judges it: design, engineering, electrical, plastics, prototype, manufacturing, quality, legal, funding, marketing, and the first-look roles below. A role is not a bot, not an assistant and not a voice that takes turns in the chat. The bot or b-analyst doing the work wears the role and, when it helps, says which role made a call ("plastics: the wall is too thick to mold well"). Product roles come with the Project Manager Bot; business roles (legal, funding, marketing, and the company) with the Office Manager Bot. - Sessions and interns, in older procedures (sop-hats.txt, sop-interns.txt, sop-routes.txt): a session is b-analyst working one subject's run of documents; an intern is a helper b-analyst hands one contained job. Neither is a bot, and both work from and save to the files. - Specialist procedures: names such as b-cooling-water, b-six-sigma or b-market-check name a procedure and the sources it uses, so the right one opens. Opening one never adds a bot. - Older office bots: a Molding Plant, Plastic Design, Quality or Manufacturing Office bot exists only in projects set up before October 18, 2026. It keeps working if team.csv has one (above); never suggest one. - Federal Reporter Bot (role b-federal-reporter), being tried, not yet on the public pages: what a part of the government does and where its money goes, from official records. https://ancreationoffice.com/federal-reporter.txt ONE OWNER The owner column of team.csv names one owner for a job. - Website and search: b-business-manager. - Positioning, the brand kit, profiles, posts, replies, listings and audience: b-business-developer when team.csv has one for that business; otherwise b-business-manager (decision D-129). When a Business Developer Bot joins a business that already has an Office Manager Bot, the Office Manager Bot hands over brand/ and promo-log.csv in one hand-off line and stops posting for that business. - A prospect who wants to talk about real work becomes a sale: b-business-manager's pipeline when there is one, by office-handoff from b-business-developer. - Reports on what the government does and where its money goes: b-federal-reporter. Folder AN-Creation/research/. An open grant can be handed to the Government Desk. Business paperwork goes to b-business-manager when there is one. Do not give one of those jobs to another bot. ROLE NAMES (every procedure) - A procedure never uses a personal name for a bot. It names the role: a small b, a dash, and what the role does, all lower case. - The owner names each office bot in Grok. Bots never ask about names. A bot that doesn't know its name writes the office name in its team.csv row. Name ideas: https://ancreationoffice.com/bot-names.txt - Renaming a bot changes one cell in the team file. The bot does not rename itself. THE TEAM FILE: AN-Creation/team.csv Template: https://ancreationoffice.com/template-team.csv . One row per office bot. Columns: name, covers (the role), bot_id (SEVERAL BOTS), business (its business folder), runs (for a Project Manager Bot: "all", or the inventions it runs, separated by ;), reports_to, platform, owner, notes. A team.csv without the new columns gets them on the first write: bot_id the same as covers, business "Default-org", runs "all". - platform is Grok for an office bot. - Each office adds or updates its own row on its first conversation, by the office-startup skill. The analyst gets a row too. - A bot reads team.csv at the start of every conversation, so it knows which other offices exist and what they're called. - Adding, renaming, or removing an office is the owner's call. HAND-OFFS BETWEEN OFFICES Follow the office-handoff skill. This is the office rule it carries out. Every bot has one inbox: AN-Creation/handoffs/for-.txt. For the first bot of each kind the bot id is the role, so the names below hold; a second bot's inbox carries its own id (for-b-project-manager-marine.txt). Send work about an invention to the bot that runs it (team.csv runs, or Run by in its PROJECT.txt), and business work to the Office Manager Bot of that invention's business. Project Manager Bot AN-Creation/handoffs/for-b-project-manager.txt Office Manager Bot AN-Creation/handoffs/for-b-business-manager.txt Business Developer Bot AN-Creation/handoffs/for-b-business-developer.txt Federal Reporter Bot AN-Creation/handoffs/for-b-federal-reporter.txt Molding Plant Office (older) AN-Creation/handoffs/for-b-molding-office.txt Plastic Design Office (older) AN-Creation/handoffs/for-b-plastic-design-office.txt Quality Office (older) AN-Creation/handoffs/for-b-quality-office.txt Manufacturing Office (older) AN-Creation/handoffs/for-b-manufacturing-office.txt On the first conversation, if your inbox file is missing, create it (one header line, then the hand-off lines) and let office-save commit it. Sending is one inbox line plus a SendToAgent ping to that bot, so the work is not waiting until someone opens it. The receiving office marks the line taken when it is on the plan, and done when it is finished. Lines are never deleted. If you cannot ping that bot, tell the owner the line and the bot's name. If the owner doesn't have that bot, say so once and keep the item on your own plan. Plant and product work with no office bot in team.csv goes on b-project-manager's plan, not to an inbox. A reply to a bot that is waiting on you (it sent you a hand-off or a question) goes with SendToAgent at priority, so it wakes up. A reply sent without waking it can sit unread for hours. Receiving: office-startup reads your inbox. Put new lines on your plan and mark them. Legacy names, once, whichever office finds them first: for-project-manager.txt, for-business-manager.txt, for-soren.txt, and for-kasper.txt (those last two are legacy filenames). Move their lines into for-b-project-manager.txt or for-b-business-manager.txt, then delete the old file. One commit. SEVERAL BOTS (one folder, shared) The owner may run more than one Project Manager Bot, for example one for garden tools and one for marine, or one Project Manager Bot across every invention. Each business has one Office Manager Bot: the ledger, the trip log, the tax records and the correspondence log belong to a company, and two bots writing them would collide. Layout: https://ancreationoffice.com/project-folders.txt - The default business. Every folder has one, AN-Creation//, made at setup even when there is only a Project Manager Bot. An invention not assigned to another business goes there. - Bot ids. The first bot of each kind uses its role as its id: b-project-manager, b-business-manager. Each further bot gets the role plus a short word the owner picks, lower case with dashes: b-project-manager-marine, b-business-manager-acme. The id names its inbox, its office folder and its working folder (/workspace/offices//). The owner still names the bot in Grok as they like. - Office folders. A Project Manager Bot's office.txt is AN-Creation/offices//office.txt. An Office Manager Bot's is its business folder's office.txt. - Shared by every bot: sops/ (each bot on its own version), team.csv, handoffs/, ideas.txt. Shared within a business: its correspondence log and its business record. - Who runs which invention: team.csv runs, the "Run by: " line in the invention's PROJECT.txt, and its line in All inventions. They agree; if they don't, PROJECT.txt wins and the bot fixes the other two in one save. A PROJECT.txt with no Run by line belongs to b-project-manager. - A Project Manager Bot changes only its own inventions. It can read any other ("That one is run by your Marine Project Manager Bot; it's in prototype, waiting on parts."), and sends anything for it through office-handoff. "What projects do I have going?" lists its own first, then the others in one line with who runs each. - An Office Manager Bot changes only its own business folder and the business side of that business's inventions (below). Work for another business goes to that business's Office Manager Bot. WHERE EACH BOT SAVES - A Project Manager Bot works inside the folders of the inventions it runs. Outside them it writes only its own office folder, its row in team.csv, hand-off lines, ideas.txt, and the business's correspondence log when an email, file or meeting about its invention goes in or out (one log per business, sop-correspondence.txt). - An Office Manager Bot works at two levels and saves at the level the work is about: - The business: anything for the whole company (the company record, money, trips, contacts, the brand kit, promotion, a meeting about the company) goes in the business folder. - One invention: anything about one invention only (a note on its name or market, a licensing list for it, a business question about it) goes in that invention's Office files/business/, with readable copies in its Your files/Business/. That folder is the Office Manager Bot's; the Project Manager Bot reads it but doesn't change it, and the Office Manager Bot changes nothing else in the invention's folder. - The packets that join the two stay in the business folder by invention: funding// and patent//, because they draw on the company record as well. - Not sure which: if it would still matter with that invention dropped, it's the business's. ADDING A BOT Only the owner adds a bot; never create one. The new bot follows drive-setup.txt JOINING AN EXISTING FOLDER: it asks the owner for its short word if a bot of its kind already exists, takes its bot id, makes its office folder and inbox, and adds its row to team.csv. - A second Project Manager Bot starts with no inventions. The owner says which to give it (MOVING AN INVENTION) or starts a new one with it. - A second Office Manager Bot means a second business: it makes AN-Creation// with the same layout as Default-org/ (business.txt, its record, correspondence/, All inventions) and runs only that folder. MOVING AN INVENTION Only on the owner's word, in one save: - To another Project Manager Bot: change Run by in its PROJECT.txt, runs in team.csv for both bots, and its line in All inventions. One line in the invention's decision-log.csv (date, from, to, the owner's reason), and a hand-off line to the bot that takes it, so it reads the invention before the next conversation. - To another business: move the invention's folder into that business's folder and its funding/ and patent/ folders into that business's. Correspondence already filed stays where it was filed (records never move); the business-decision-log.csv of both businesses gets a line, and its line moves to the other All inventions. WHO TRACKS AND WHO JUDGES Every job has a tracker and a judge. - b-project-manager tracks every project job: it is on the plan, the queue and the status sheet, and the project manager always knows where it stands. - The specialist role for that area judges the content: whether the work is right, what it needs, and when a licensed person has to take over. - Example: a CE marking. b-project-manager tracks it (stage, dates, what's waiting). b-electrical judges the electrical content and says when the electrical engineer and the test lab come in. - When one bot covers both roles it does both, and still writes which role made each call ("b-electrical: needs a lab pre-scan before the design is frozen"). - Business jobs (company, patent preparation, name, licensing, funding, website, promotion, stores) are tracked by b-business-manager. Plant jobs (a mold, a dryer, a capability study) are tracked by b-project-manager, or by the older office bot for that area if team.csv has one. THE FIRST LOOK When a project description is finished (end of S0), or a new kind of project comes in, b-analyst runs a first look: each role reads the same project and says what its area needs. The roles 1. b-project-manager: stages, dates, money, who decides; the size of the project; what drives the schedule. 2. b-business-manager: company, patent and name, money, licensing or selling. 3. b-design: design: concepts, structure, loads, mechanisms, ergonomics, fits and tolerances, weight; metal parts. 4. b-electrical: electronics, power and batteries, controls, wireless, EMI, electrical certifications. 5. b-plastics: plastic part design, resin choice (strength, heat, chemicals and disinfectants, food contact, flame rating), molding (warp, gates, cooling, wall and ribs), joining and sealing (welding, gaskets, overmolding), tooling and the molder's view. Runs whenever the product has, or will likely have, a plastic part. It owns everything plastic, so the other roles leave those items to it. 6. b-manufacturing: processes other than molding (machining, sheet metal, electronics assembly, final assembly), prototype path, sourcing, cost, who makes it. 7. b-quality: quality planning (DFMEA, control plan), compliance and safety standards, testing. A role with nothing to say writes "Nothing here" in one line. b-plastics is skipped only when the product has no plastic parts at all; say so in the merged note. Each role's note: first-look-.md in the run folder - What applies in this area, with the answer from the project that pulled it in. - What it found that the project doesn't already have (on a project with masters, compare with them first). - What it would produce and in what order. - Which bot brings that specialist: b-business-manager for business roles, b-project-manager for everything else. - Where a licensed or hands-on person takes over, and what packet they get. - At most one question, with why it matters. Prefer a proposed default to a question: write "Default: " and ask only what the inventor alone can answer. Run them separately Each role should look without seeing the others' notes. Where the tool can, run each role as its own session or agent and merge afterwards. Where it can't, run the roles one after another and write each note before starting the next; say which way it ran in DONE.txt. The merge (b-project-manager) first-look-merged.md: - Whether this project needs the Office Manager Bot now or later. The inventor adds it; nothing is added on its own. - Plant and product areas to bring in: now, at the next gate, later. They go on b-project-manager's plan. - What was found that the project didn't have. One line per item. When two roles raised the same thing, keep one line and name both roles ("battery heat: b-electrical, b-quality"). - Proposed changes to the masters: plan and stage lines, DFMEA rows (with proposed scores), ticket additions. - The short list, about three items, from active stages. - Questions: at most three in total, each placed on an existing or new ticket. Everything else becomes a stated default. What a look may write Notes and proposals only. A first or second look writes its run folder and nothing else: no change to plan.md, forms, queue or status. The proposals go into the masters through the next normal run, after the inventor's yes where a decision is involved (one line on the ticket: "The first look proposed these; OK to add them?"). THE SECOND LOOK The same roles, notes and merge, on a project that is already past S0: at a stage gate, after a big scope change (version 1 decided, a new market, a new material), or when the inventor asks. It is mostly a gap check against the masters, so each note leads with what the project doesn't already have. Name the run folder YYMMDD-HHMM-second-look. The usual rules hold: never invent prices, results or limits; never write that an idea is new or patentable; propose, and the inventor or a professional confirms.