How it works

Why we work this way

The structure is there to make it easier to keep going, remember what matters, and check the work. Here's the reason behind each of the main habits.

Why write the plan as we talk?

New questions and ideas arrive faster than a project can finish them. Writing them down keeps them from vanishing when the conversation moves on. Your Project Manager Bot keeps agreed work, possible ideas, blockers and finished work apart in plan.md.

A plan records the work still needed. It doesn't turn every suggestion into a commitment, and it doesn't prove a task happened. See the plan layout.

Why keep the bots' instructions apart from the project?

You may change bots, tools or people. Your company records and product designs should stay easy to find. A formation filing goes under the company. A CAD model goes under CAD. The bots' instructions live apart, in their own sops/ folder.

Someone looking for the LLC filing shouldn't need to know which bot prepared it. See what's in your project folder.

Why give the work roles?

Concept design, engineering, legal preparation and manufacturing ask different questions and use different references. Naming the role a piece of work belongs to keeps each subject focused, and it shows what a change has to be checked against.

Roles aren't more bots. The Project Manager Bot works the product roles and coordinates what's next. The Office Manager Bot works the business ones. Meet the bots, or read about temporary helpers for a single task.

Why instructions and checklists?

Instructions say what the bot's job is. A checklist helps it notice missing inputs and unfinished steps without leaning on a long conversation. Each step should have a reason and a result you can look at.

A checked box isn't evidence on its own. Link it to the drawing, decision, calculation or test result behind it. If a step doesn't apply, write down why.

Why go back to the original source?

Standards, programs and professional directories change. Our resource list points to the organizations that maintain them. The bot picks what applies, checks the current version, and records what it used.

That beats keeping a second, incomplete copy here. Browse the resources.

Why one owner and a visible handoff?

Two bots shouldn't quietly overwrite each other's changes, any more than two people should. A named owner, a clear revision, and a handoff that points to the actual file keep everyone on the same information. The next person can see what changed and what's still open.

Why track who had which revision?

You may be looking at Rev 5 while the vendor has Rev 3. You both describe what you see, so you can't agree until you realize the files differ. Keep each issued version, and record who was sent it, when, and why.

Start with "We're on Rev 5. Do you have that copy?" Confirm the revision on the actual file before you talk about a change. Version control, with or without Git.

Why are saved records never changed?

Bots make mistakes, and going back to an earlier version is common. So a change to a drawing, page or analysis is a new dated file, and the old one stays exactly as it was. Working files like the plan stay current, and earlier versions are kept. You can always trace a result back to where it started.

Your Project Manager Bot links matching revisions in a release list. How your project is kept safe.

Why do McMaster-Carr part numbers keep showing up?

Because much of the CAD is already done, and the selection is huge. When McMaster-Carr has the hardware you need and a model of it, your designer can drop it into the design instead of drawing it from scratch. That saves work and gives you a specific part to talk about.

You can buy from any supplier you like. Don't be surprised if a drawing house sends back a parts list full of McMaster-Carr numbers. They're handy design references, not a requirement to buy there.

To save your designer time, find the hardware on McMaster-Carr and send the link and part number. If you already have a preferred part or supplier, send that instead.

McMaster-Carr is also handy for first samples. As quantities grow, your Project Manager Bot can compare Fastenal and other suppliers. The engineering role checks that an alternative meets the design before it replaces the original. The design reference and the purchasing source are recorded separately.

McMaster-Carr's CAD models · Hardware sources and the sourcing steps

How it works · About Advance Now LLC

The tools behind that why 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.