One kitchen fire, many hand-offs: from board-up to pack-back.

Seen from the owner's chair, the fire restoration process is mostly hand-offs. In this article's illustration one kitchen fire produces a first-night board-up, a pack-out of two rooms, structure cleaning and odor work, three subcontractors for the rebuild and a pack-back. Three Bots the owner has created in Grok Bot, each a named assistant with one job on a shared cloud computer, carry the paperwork between those stages: a Coordination Bot holds the schedule, a Contents Bot drafts the inventory and an Updates Bot drafts the family's weekly news. The owner approves every date, every item decision and every message.

One owner directing a few single-purpose assistants is what this series calls the one-man army, and the pillar article explains it. On a fire job the test is plain: can three Bots carry the paperwork across seven weeks and four trades without the owner losing sight of a single date?

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.

Consider an illustration: an owner-run restoration company with a lead technician, a small cleaning crew and a contents crew of two. Early one evening a pan fire spreads to the cabinets in a single-story house. The fire service puts it out and hands the property back, the carrier's assignment reaches the owner by phone, and the owner and the lead technician drive out.

The first night needs hands and judgment, not paperwork: whether the kitchen ceiling is sound, whether the kitchen circuits stay off, which openings need boarding. The owner and the technician board the broken window and the back door, photograph the openings and the utilities as they found them, and leave the house secured. The carrier's call came to the owner's phone and stays there, since Grok Bot's documentation describes no telephony.

Before leaving the street at eleven, the owner posts the board-up photos and three lines of notes in the Coordination Bot's chat. The Coordination Bot's only job tonight is the board-up record: openings secured, utilities as found, and what the pack-out crew will need to get in. An approval raised overnight by a message from another Bot would expire after about ten minutes (Cursor's help pages say thirty) without running, and one in the owner's own chat would simply wait, so either way the record is a file waiting for the owner in the morning, not a message anyone receives.

The owner created three Bots for fire jobs and gave each one its limits in chat as lasting rules to remember: nothing goes to the family, a subcontractor or the carrier, no item is ever marked for disposal, and a missing photo or date is listed as missing. The documentation treats a remembered rule as guidance the Bot follows rather than a lock, which is why every outgoing message in this design sits as an editable draft until the owner sends it.

• COORDINATION BOT

  Holds the job's master schedule, posts the morning queue in the group and assigns each item to the Bot that owns it.

• CONTENTS BOT

  Drafts the inventory for the two packed-out rooms from photos and crew notes, and keeps the custody record.

• UPDATES BOT

  Drafts the family's weekly update from the schedule and the owner's notes.

The three share a group chat. A group holds two to six Bots, and the Bots in it can post and pass work among themselves. From the documentation's group example, this design takes the coordinator who can hand out work. Nowhere does the documentation describe a Bot that supervises other Bots; the role it calls Chief of Staff compiles a briefing for a person to read. The Coordination Bot is therefore Aevrion's own arrangement of documented parts: a coordinator inside a group, direct messages between Bots, and passing a task into another Bot's ownership. It schedules and asks; it decides nothing.

Direct messages between Bots come switched on, and an admin on a team plan has a setting that stops them; if that happens, the owner relays items by hand. The group never shows approval cards, sign-in prompts or email drafts. Those surface only in the one-to-one conversation of the Bot that raised them, so the owner reads the queue in the group and acts Bot by Bot.

Smoke from the kitchen reached the dining room and the bedroom off the hall beside it. On day two, after the owner's assessment, the contents crew packs out both rooms. The crew lead photographs each item and box and sends the pictures to the owner, who passes them on to the Contents Bot. A Bot sits in one person's account, so the owner is the route in; the pack-out inventory article covers the shared-folder alternative.

The Contents Bot drafts the inventory as a spreadsheet, one line per item or box, and the crew lead checks the draft against the boxes that evening. When the owner needs to see the boxed contents of the china cabinet to decide, the Contents Bot shows the pack-out photos in its own conversation; when the Coordination Bot needs to check one against the schedule, the Contents Bot sends it directly, because a Bot's handoff into the group carries only text at present. Whether anything is salvageable is the owner's call, made with the family; the Bot records the decision once a person has made it and never proposes disposal. How that record and its custody trail are built is the subject of the series' pack-out inventory article.

Structure cleaning and odor work come first, done by the company's own technicians under the Restoration Work Plan the owner wrote. S700, the IICRC's fire and smoke restoration standard, is described on the IICRC website (read on 15 October 2026) as a 2025 first edition whose scope takes in that plan and the recording of events on the project, while reconstruction is listed among subjects it does not comprehensively address. Once cleaning is done, the schedule answers to whatever the local building department requires and to what each trade needs.

In this illustration the rebuild needs an electrician for the kitchen circuits, a drywall-and-paint crew and a cabinet installer. The Coordination Bot holds the chain below. The conditions are the owner's, entered from the permit and from what each subcontractor said it needs; the Bot checks them and never invents one.

At each hand-off the Coordination Bot writes the next subcontractor's booking email around the date the owner agreed. It waits in that Bot's own conversation as an editable draft, and nothing goes until the owner presses send.

The family is staying with relatives across town. Each week the Updates Bot drafts a short note from the schedule and the owner's notes covering the work finished, the next steps with only the dates the owner has fixed, any trade the job is waiting for, and choices the family must make, such as whether the dining chairs are worth cleaning. The draft sits in the Updates Bot's own conversation until the owner edits and sends it. It is a weekly message, not a live feed, and that suits the owner: a date promised in a hurry is the one the family remembers.

The draft never discusses the claim, temporary housing payments or coverage, which are between the family and their insurer, and it never comments on health. Texas is one example: its Insurance Code, at §4102.163 (as checked on 15 October 2026), does not let a restorer working on a house become that homeowner's public adjuster; owners elsewhere confirm their own state's rule with a qualified professional. Whatever goes to the carrier or the adjuster comes from the owner, in the owner's words.

In week five the cabinet supplier pushes delivery back a week. The owner tells the Coordination Bot, which reworks the dependent dates as a proposal: the installer's start, the pack-back and the final walk-through. It posts the proposal in the group and hands the family's side to the Updates Bot, which drafts a revised note explaining the delay in plain words. The owner accepts the new dates in the Coordination Bot's conversation, sends the installer's email and the family's update from each Bot's own conversation, and rings the family as well, because a delay deserves a voice.

Nothing moved by itself. The Bots reworked the paperwork; the owner moved the job.

In week seven the dining room and bedroom contents come home. The Contents Bot prepares a pack-back sheet from the verified inventory, ordered by room, with each line's pack-out photo. The crew carries each item to its place while the family and the crew lead go down the sheet together; anything missing or damaged is noted as an exception for the owner. A person collects the family's signature.

In this illustration the job runs seven weeks, through four trade hand-offs and one slipped delivery, to a pack-back sheet with no exceptions: the dates moved once, and the family heard about it before the installer arrived. The pieces to scope with Aevrion Ops are the Bots' standing rules, the schedule format and links to your job and contents software, which are custom integrations subject to what each vendor's API and terms permit, and to testing. To talk through the hand-offs on your own fire jobs, use the contact page.

1. In this illustration one kitchen fire produces a first-night board-up, a two-room pack-out, cleaning and odor work, three subcontractors and a pack-back.
2. The board-up night belongs to the owner; the Coordination Bot's only overnight task is the board-up record, waiting as a file for the morning.
3. The Coordination Bot assigns work in a group chat as an Aevrion pattern, while approval cards and email drafts surface only one-to-one.
4. Pack-out pictures come from the crew via the owner; a Bot that must inspect one receives it from the Contents Bot directly, because a group handoff carries text only.
5. The family's weekly update is drafted by a Bot and sent by the owner, and never discusses the claim or health.
6. Salvage, dates, the work plan and every message stay with the owner.