The week demolition finds something: a remodel with the family upstairs.

Communication with homeowners on a remodel is easy in the weeks when nothing happens. It is tested in the week demolition finds something, when the family living upstairs needs to know what changes for them, the crew needs to know what it may touch, and the paperwork has to catch up before the work does.

A small design-build firm can give most of that paperwork to a few AI assistants: the log of what was found, the change-order description, the notice about tomorrow's power cut. What it cannot give them is any part of the stop. Whether work halts on a suspect ceiling, whether the material is tested, what the wiring needs and what the change costs are decided by people, and in California, where this illustration is set, the state licensing board's rule (as checked on 15 October 2026) is that both parties sign the change order before the change.

Demolition week in a house still lived in is where the One-Man Army model is easiest to see: the owner makes every promise to the family and every commitment on price, and each assistant keeps one desk's paperwork ready. The pillar article sets the model out in full.

In Grok Bot, the product used throughout this illustration, every Bot carries a name, a single responsibility and a conversation of its own, while all of them run on one shared cloud computer. A Bot can message another and pick up the answer later, or transfer ownership of a task outright; Cursor's help pages say there is no switch to stop that messaging, and a Bot follows instructions about it. A group chat of two to six Bots can include a coordinator that hands out work. The documentation describes no telephony and names no connector for remodeling software, so phone calls stay with people, and linking the firm's estimating or scheduling tools means a custom integration or supervised use of the vendor's website, if its terms permit, tested before anyone relies on it.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

What follows is invented for illustration; it describes no real firm, client or job. A California design-build firm: the owner holds the contractor's license and does the estimating, a lead carpenter runs the site with one helper, and electrical and plumbing go to trade partners. The job opens up the ground floor of a two-story house built in 1962. The wall between kitchen and dining room comes out, and the family room ceiling comes down for new lighting. The family lives upstairs, with a kettle, a microwave and a fridge in the spare bedroom. This is the board on Monday morning:

• DEMOLITION, DAYS ONE TO THREE

  Kitchen cabinets out, the dividing wall opened, then the family room ceiling.

• LEAD-SAFE WORK

  Because the house predates 1978, the pamphlet was acknowledged before the job and demolition runs under the firm's lead-safe practices, directed by its credentialed renovator. Its records have their own article in this series.

• SHUT-OFFS THIS WEEK

  None planned. The kitchen is already out of service.

• SELECTIONS

  Floor tile to be chosen by Friday so it can be ordered in time.

On Wednesday morning the lead carpenter opens the dividing wall and finds older wiring than the drawings assumed, with a splice and no box. Twenty minutes later the helper starts on the family room ceiling and the carpenter stops him: the ceiling has a textured finish that the drawings did not show.

The ceiling is the stop. The federal Consumer Product Safety Commission's home asbestos guide (CPSC, as checked on 15 October 2026) includes textured paint and joint patching compounds among possible asbestos sources, records that their use was banned in 1977, and tells readers not to saw, sand, scrape or drill such material; sampling is a job for a professional. A house built in 1962 predates that ban. The carpenter's job is to stop and tell the owner. The owner's job is to decide whether the material is tested, by whom, and what happens to the room meanwhile.

The assistants' part is small and deliberate. The site-log Bot records the ceiling as an entry marked 'stopped: owner decision', with the carpenter's photo and words and nothing else. It does not describe the texture, guess at its age or suggest a test. It prepares no change order for that ceiling until the owner has written down what was decided.

The documentation favors a short roster that grows only when a role becomes stable and distinct, so in this illustration the firm brought its Bots in one at a time, over several jobs:

• SITE LOG

  Turns the carpenter's daily photos and notes, saved to the job folder the owner has given it, into discovery-log entries, and drafts change-order descriptions with no price.

• CLIENT DESK

  Drafts the family's notices, the weekly update and the cover email that goes with a change order. The owner sends every draft, after checking site details with the carpenter.

• SCHEDULE

  Keeps the crew and trade-partner calendar and works out what is off, and when, for each day of the coming week.

• COORDINATOR

  Posts the morning list in the group chat and assigns each item. This is Aevrion's pattern, assembled from the documented group coordinator and direct Bot-to-Bot handoffs. The documentation's own Chief of Staff example is narrower: it is described as a source-linked digest for a person, and directing other Bots is not part of it.

The group chat has two documented gaps. It never shows approval requests or email drafts, which therefore arrive in each Bot's private conversation with the owner. And messages handed to the group carry text only for now, so the carpenter's photo of the opened wall travels from the site-log Bot straight to whichever Bot must look at it.

Every step below ends with something a person decided or did. The Bots close the gaps between steps; they are never the step.

1. 01

   Wednesday, late morning

   Decides

   Does work stop on the ceiling, and is it tested?

   Output

   The owner's decision recorded on the log entry, with the time and the name of who made it

2. 02

   Wednesday, midday

   Decides

   What does the wiring need?

   Output

   The electrical trade partner's site note: what to replace and why, in the partner's own words

3. 03

   Wednesday, afternoon

   Decides

   Is the change-order description accurate?

   Output

   The site-log Bot's draft, corrected by the carpenter, with price and signatures blank

4. 04

   Wednesday, evening

   Decides

   What does the change cost?

   Output

   The owner's price on the change order, sent to the clients in an email the owner chose to send

5. 05

   Thursday morning

   Decides

   Have both parties signed before the rewiring starts?

   Output

   The signed change order on file; only then does the schedule show the electrician

6. 06

   Thursday afternoon

   Decides

   What is off for the family, and when?

   Output

   A notice that ground-floor power is off on Friday morning, checked with the carpenter and sent by the owner

7. 07

   Friday

   Decides

   What is still open?

   Output

   The weekly update: the ceiling decision and next step, the signed change, the tile still to choose

In California the rule is direct. The Contractors State License Board's page on home improvement contracts (as checked on 15 October 2026) requires changes to be written, and says that altering the price or the scope takes a written change order that homeowner and contractor both sign ahead of the change; the signed order is then part of the contract. That is why step five sits where it does. The electrician can be booked; the work cannot begin until the paper is signed. Firms outside California work under their own state's rules, which the owner confirms with a lawyer rather than with an assistant.

The site-log Bot's draft is plain: where the wiring was found, what the trade partner proposed in the partner's own words, what in the original scope changes, and the schedule effect the carpenter expects. It leaves out what the Bot cannot know, including whether the old wiring is dangerous. That judgment belongs to the electrician, and the price belongs to the owner.

Meanwhile the schedule Bot drafts a re-sequenced Thursday so the crew keeps working on the kitchen side rather than standing at the dining wall. The carpenter decides whether to use it.

In this illustration the stair wall that meets the opened dining room is plaster on wood lath, not drywall, and so is the upstairs hallway the family walks through every day. Neither appears on the drawings.

That changes three things in the office. The discovery log records which walls are plaster, so the change order describes the right repair rather than a drywall patch. Whether to restore the plaster or cut back and replace it with drywall is a choice for the clients, priced by the owner and possibly carried out by a plaster restoration specialist, so it goes on the selections list with a date. And because patching compounds are on the CPSC list, an old patch or textured skim on that wall gets the same stopped entry as the ceiling before anyone sands it.

Remodeling project communication with homeowners works best when the family knows what each message will contain. In this illustration there are three kinds. Logistics: what is off, when, and which door the crew uses. Decisions: what the clients need to choose or sign, and by when. Discoveries: what was found and what it means for them. The client-desk Bot drafts the first two. For a discovery involving a possible hazard, the owner writes the key sentences, and the Bot only arranges them around the logistics.

Every message is an editable draft that a person reviews and chooses to send. That matters for timing: an approval raised by a routine or by another Bot's message lapses after about ten minutes (Cursor's help pages say thirty) if nobody answers, and the action never runs, so the Friday update is prepared as a draft and waits for the owner. Whether anything pauses for approval in the first place turns on which tool is involved, how risky the step is and what rules the firm has set, and approving never reverses a step already taken.

The site-log Bot is the safest first assistant. Give it the photos and notes from a remodel that is already finished, compare its entries with what the carpenter remembers, and correct the procedure where they differ. That read-and-prepare stage is the documentation's recommended first step. The client desk follows; the coordinator comes last, once there are enough Bots to need one.

Aevrion Ops can help a small design-build firm write the log format and the stop rule, design the Bots and their approval boundaries, and build custom integrations to the scheduling and estimating tools it already uses, where the vendor's API or terms allow, once tested. For a firm this size, a sensible first step is the workflow automation readiness assessment.

1. In an occupied remodel, the week demolition finds something is where communication with the homeowners is really tested.
2. A suspect ceiling texture stops work; the owner decides whether and by whom it is tested, and the assistant only records the stop.
3. The wiring change order is drafted without a price, priced by the owner and, in California, signed by both parties before the rewiring begins.
4. A coordinator Bot is Aevrion's pattern; approvals and drafts stay in one-to-one conversations, and photos go directly from Bot to Bot.
5. Plaster walls are logged as plaster, offered to the clients as a repair-or-replace choice and given the same stop rule before sanding.
6. Family notices are drafts a person sends; unattended approvals lapse, so nothing the family needs waits on a quick tap.