Every written procedure the bots work from, in plain text. Nothing hidden: click any file to read exactly what the bots are told to do. You don’t need any of this to start; your bot opens what it needs.
How procedures work here
A procedure is a written way to do one job. A bot doesn’t carry every procedure in memory. Each one keeps a short standing file and opens a procedure only when its subject comes up, then leaves it. Lines in the procedures are marked “Mike” (his practice), “published” (with the source) or “office”.
The index the bots read is sop.txt. Every file is plain text, linked to the others, so any assistant that can read a web link can follow it.
By office
Project Manager Bot
- Standing instructions: standing.txt
- Project management: standing.txt · project-manager.txt · sop-office.txt · sop-team.txt · sop-focus.txt · sop-stages.txt · sop-graph.txt · sop-action-log.txt · status-template.txt · plan-template.txt · ticket-template.txt · sop-review-page.txt · sop-change-control.txt · revisions.txt
- Market Check: sop-market-check.txt · sop-gateways.txt · sop-launch.txt
- Design: sop-design-loop.txt · design-principles.txt · design-review.txt · design-risk.txt · check-sheets.txt
- Prototyping: sop-prototype-loop.txt · template-prototype-control-plan.txt · template-trial-log.txt
- Design for Manufacturing: manufacturing.txt · design-review.txt · check-sheets.txt
- Product Safety and Listing: compliance-matrix-template.csv · test-plan-template.txt
Office Manager Bot
- Standing instructions: business-manager.txt
- Business management: business-manager.txt · sop-gateways.txt · sop-company.txt · sop-website.txt · sop-presence.txt · sop-promotion.txt
- Company Setup (LLC): sop-company.txt · sop-gateways.txt · forms-catalog.csv
- Patent Prep: sop-gateways.txt · forms-catalog.csv
- Trademark and Naming: sop-gateways.txt · sop-presence.txt
- Licensing: sop-licensing.txt · sop-gateways.txt · sop-launch.txt · forms-catalog.csv
- Funding: sop-funding.txt · sop-gateways.txt · sop-launch.txt · forms-catalog.csv
- Launch and Promotion: sop-promotion.txt · sop-presence.txt · sop-website.txt · sop-launch.txt
- Retail Selling: sop-launch.txt
Molding plant procedures
- Standing instructions: office-molding.txt
- Scientific Molding: sop-scientific-molding.txt · scientific\_molding.py · sop-tooling-loop.txt · template-trial-log.txt
- Molding Defect Troubleshooting: sop-molding-defects.txt · sop-scientific-molding.txt · sop-drying.txt · sop-cooling-water.txt · design-risk.txt · toolbox-improvement.txt
- Mold and Machine Cooling Water: sop-cooling-water.txt · cooling\_water.py
- Material Drying and Handling: sop-drying.txt · drying.py
- Mold Buying and Qualification: sop-mold-buying.txt · sop-tooling-loop.txt · sop-qualification.txt · template-fai-report.csv · template-apqp-file.csv · template-trial-log.txt
- Plastic Material Selection: sop-material-selection.txt · design-review.txt
- Machine Safety and Guarding: sop-machine-safety.txt
Plastic design procedures
- Standing instructions: office-plastic-design.txt
- Plastic Part Design: sop-plastic-part-design.txt · sop-design-loop.txt · design-review.txt
- Tolerance Stack and GD&T: sop-tolerance-stack.txt · tolerance\_stack.py · design-review.txt
- Plastic Material Selection: sop-material-selection.txt · design-review.txt
- Design for Manufacturing: manufacturing.txt · design-review.txt · check-sheets.txt
- Prototyping: sop-prototype-loop.txt · template-prototype-control-plan.txt · template-trial-log.txt
- Mold Buying and Qualification: sop-mold-buying.txt · sop-tooling-loop.txt · sop-qualification.txt · template-fai-report.csv · template-apqp-file.csv · template-trial-log.txt
- CAD with computer intelligence: sop-ai-cad.txt
Quality procedures
- Standing instructions: office-quality.txt
- Quality Planning: sop-stages.txt · sop-tooling-loop.txt · sop-qualification.txt · sop-quality.txt · product-development.txt · control-plan.csv · critical-quality.csv · template-apqp-file.csv · design-risk.txt · test-plan-template.txt · test-matrix.csv · toolbox-improvement.txt
- Measurement and Inspection: sop-qualification.txt · template-fai-report.csv
- Lean Six Sigma: sop-six-sigma.txt · template-a3.txt · six\_sigma.py · toolbox-improvement.txt
Manufacturing procedures
- Standing instructions: office-manufacturing.txt
- Manufacturing: sop-manufacturing-cell.txt · manufacturing.txt · sop-launch.txt · sop-qualification.txt · sop-tooling-loop.txt · control-plan.csv · toolbox-improvement.txt
- Purchasing: manufacturing.txt · forms-catalog.csv · template-spending-register.csv
- Cost and BOM: template-spending-register.csv · forms-catalog.csv
- Automation and Auxiliaries: manufacturing.txt
- Machine Safety and Guarding: sop-machine-safety.txt
- Lean Six Sigma: sop-six-sigma.txt · template-a3.txt · six\_sigma.py · toolbox-improvement.txt
Shared and supporting procedures
Getting started
- version.txt · profile.txt The office version, and how to update a bot when you ask it to.
- business-manager.txt The Office Manager Bot (b-business-manager): company, patent preparation, name and trademark, licensing, funding, website and promotion, getting into stores.
- start-on-your-phone.txt For a first-time user, on a phone: start here.
- sop-team.txt · sop-office.txt Set up the Project Manager Bot and b-analyst. Each one is its own Grok bot. More than one Project Manager Bot, or a second business, share the same folder.
- sop-folder-move.txt Moving an older project folder into the business layout, once, with your yes.
- sop-team.txt The offices: roles, role names, the team file, hand-offs between offices, who tracks and who judges, and the first and second looks.
- toolbox-improvement.txt The improvement toolbox: Lean, 5S, Six Sigma and TPS tools, picked by the problem.
- drive-setup.txt The project home: asking where the owner wants the project folder (a cloud folder is best), the AN-Creation folder, saving and read-back, and the analyst (Grok Build).
- office-startup.txt · office-save.txt · office-handoff.txt · office-call-analyst.txt · office-setup-check.txt The five shared skills: start a conversation, save, hand work to another bot, call the analyst and check it came back, and check that setup can write and read back.
- sop-reminders.txt · sop-several-inventions.txt Reminders and parked ideas; several inventions with one Project Manager Bot.
- github-setup.txt Optional add-on for people who write code: private GitHub repository, clones, the analyst, and troubleshooting.
More for the Office Manager Bot
- sop-business-plan.txt · sop-sales.txt · sop-monthly-money.txt · sop-compliance-calendar.txt · sop-contractors-and-hiring.txt · sop-weekly-review.txt For any business, with or without an invention: the one-page plan and pricing, customers and invoices, money each month, the compliance calendar, contractors and first hires, and the weekly review (examples: plan, pipeline, month, calendar).
- sop-business-record.txt The business record: seven required documents, including the trip log and the expense ledger for tax time; the bot insists on hearing about trips, meetings and costs (tax-year.py, example ledger, example trip log).
- sop-meeting-prep.txt Meeting prep: who is across the table, what they want to see, the packet and a prep sheet.
- sop-packet-buyer.txt The buyer packet (example).
- sop-packet-manufacturer.txt The manufacturer packet, a request for quote (example).
- sop-packet-lender.txt The lender packet (example).
- sop-packet-investor.txt The investor packet, for family and friends or an angel (example).
- sop-packet-accountant.txt The accountant packet: the year's ledger, trips and questions (example).
- sop-packet-patent.txt The patent attorney packet: the invention disclosure, prior art found and who has seen it (example).
- sop-packet-licensee.txt The licensee packet: a sell sheet, why it sells, the terms to discuss (example).
- sop-packet-insurance.txt The insurance packet: the product, how it could hurt someone and what was done, questions for the agent (example).
- sop-packet-attorney.txt The business attorney packet: the documents to look at, earliest first, ownership and questions (example).
- sop-packet-partner.txt The partner packet: the project honestly, what it needs, how working together could look, and no promises in the room (example).
- meeting-packet.py Builds the buyer, manufacturer and lender packets from the sheets.
- principles-bm.txt The Office Manager Bot's principles: the core eight and the entrepreneur's twelve, one file each.
- sop-company.txt b-business-manager: the company. Name checks, forming an LLC, tax ID, bank account, insurance, licenses, yearly upkeep.
- sop-website.txt b-business-manager: domain, website, business email, Google Search Console and Bing, the weekly search check.
- sop-presence.txt b-business-manager: the brand kit and profiles. Logo, descriptions, fact sheet; LinkedIn, X, Facebook, YouTube and more.
- sop-promotion.txt b-business-manager: promotion and listings. Where to promote, the approval loop, pace and honesty, the patent check, directories.
- sop-funding-packet.txt b-business-manager: the funding packet a lender or advisor reads (example).
- sop-business-risks.txt b-business-manager: the business risk register.
- funding-packet.py Builds the funding packet from the sheets.
- template-funding.csv Funding facts: price, volumes, uses of funds, milestones.
- template-business-risks.csv Business risk register template.
More for the Project Manager Bot
- sop-schedule.txt The schedule and the critical path: planned, forecast and slip, and which slips move the end (schedule.py, example).
- playbooks.txt Playbooks: whole jobs strung from the procedures: the design loop, concept to freeze, then the first tooling quote, with the quote comparison sheet.
- sop-project-record.txt The seven required documents every invention keeps (example).
- sop-project-charter.txt The project charter: scope, success criteria, milestones, budget.
- sop-spending-register.txt What the project has spent, and whose money.
- template-project-charter.txt Charter template.
- template-spending-register.csv Spending register template.
- template-ecn-log.csv Engineering change notice log template.
- principles-pm.txt The Project Manager Bot's principles: the core eight and product development's fourteen, one file each.
- sop-focus.txt Keep the project focused: risks as questions, decisions, "for now" and circling back.
- ticket-template.txt The ticket format b-project-manager runs.
- agents-md.txt AGENTS.md for the inventor's repository: how any assistant finds its ticket from one line.
- intake-001.csv The first form, always: the invention and the screening questions.
- sop-cost-sheet.txt What one unit should cost, every component, tooling separate.
- sop-risk-table.txt The risk analysis table: how it could fail as proposed, the actions taken, and what risk is left.
- sop-decision-log.txt Everyday calls, dated, with the reason.
- sop-suggestions.txt Suggestions until they have an owner and a date.
For the analyst (the heavier work)
- sop-correspondence.txt The correspondence log: a dated folder for every email, file sent, meeting or call with someone outside the company, kept as it was (example index).
- sop-document-life.txt Living and parked documents: which are updated every time something happens, which are done for a purpose and parked until a trigger, and how to dust one off (example PARKED list).
- sop-source-check.txt The source check: every spec traces to an actual document, never a bot's memory, and is checked when it goes into a sheet (check-sources.py, the principle, example).
- screening-questions.csv Screening: 26 questions that narrow the standards to the few that matter.
- sop-resource-map.txt Map the library to this project: in, later, out, ask.
- sop-gateways.txt Gateways: the one fact before each side road.
- sop-graph.txt Which form opens next. The flowchart.
- project-description.txt What fact-finding delivers: the project description, twelve sections, each with "done when".
- sop-stages.txt Stages and tracks: S0 fact-finding, S1 design loop, S2 prototype loop, S3 tooling loop, S4 qualification, S5 launch. Quality planning (APQP) sized to the product and its risks; every stage ends with go, hold or drop.
- sop-design-loop.txt · compliance-matrix-template.csv The design loop: industrial design then CAD, DFM from the first pass, the compliance matrix, recorded reviews.
- sop-prototype-loop.txt The prototype loop: build, test, refine, at whatever prototype levels it needs, to design freeze.
- sop-tooling-loop.txt The tooling loop: tool trials, design changes for tooling, final specs from measured parts and the stack-up.
- sop-qualification.txt Qualification and production approval: first article, process trials, qualifying what's needed, the approval package.
- sop-launch.txt Launch: first order, packaging and labels, the buyer packet, honest listings.
- sop-change-control.txt Revisions and change control: C, X and A/B/C revision names; the change record and what a change must re-check.
- template-apqp-file.csv · template-review-record.txt · template-prototype-control-plan.txt · template-trial-log.txt · template-fai-report.csv · template-change-record.txt · template-spending-register.csv Templates b-analyst fills.
- sop-quality.txt The quality chain.
- sop-checklists.txt Fill a form from what is already known.
- sop-routes.txt Roads in detail: patent, funding, company, standards, power, stores.
- analyst-after-intake.txt · analyst-refill.txt Prepared prompts.
- forms-catalog.csv Formal forms and documents each road produces.
Shared by every office
- project-folders.txt The project folders: Your files and Office files. Dated folders; records are never edited once saved.
- sop-review-page.txt · review.py Review pages: a local web page per invention for timelines, risks, pictures, documents and short walkthroughs.
- terms.txt Terms: the plain-language glossary to explain terms from (about 200, with read-more links).
- sop-action-log.txt · template-action-log.csv The action log: who owes what, kept for the inventor and shown as Your list on the review page.
The same jobs, written as tools a bot can follow, are in the hotbotspot tool library.
Everything here is a starting point. Work with artificial intelligence always needs tuning, so test it and dial it in for your own work, data and model before you rely on it.