In the attic all day: an owner-installer and an assessor share one job file.

An owner-installer's day is split between the attic and the desk, and in this illustration most of the desk work starts from someone else's report: an independent energy assessor has already run the blower door, scanned the walls and written a report, and the homeowner arrives holding it. The installer then has to turn that report into a proposal, show the right fact sheets, do the work and sign a receipt, without losing or quietly reinterpreting what the assessor found.

Between attic days, supervised AI assistants can carry the report through the file: extracting the findings, drafting the proposal against them, keeping the receipt checklist and assembling rebate packs. They do not reinterpret the assessor's findings, they make no ventilation or combustion call, and they sign nothing. What follows is an imagined week, sketched to show the design; no real business or result stands behind it.

In this illustration the owner installs with one helper, mostly attic air sealing and blown insulation. A local independent assessor, a separate business, refers homeowners who want the recommended work done. The assessor owns the test and the report; the installer owns the proposal, the install and the receipt. Neither works for the other, and neither can sign for the other.

In the One-Man Army approach, desk work is split between AI assistants with names of their own while every decision stays with the owner; the pillar article covers it properly. Here that means two Bots, Reports and Paperwork, with a third, Rebates, added when the season gets busy. The owner creates them in Grok Bot under Aevrion's pattern; the names are illustrations, and all of them work on one cloud computer.

The assessor is not on that computer, and should not be. Every Bot on an account shares its files and browser sign-ins, and the documentation says separate Bots are not a security boundary; two parties are kept apart by giving each its own user account. So the assessor's report reaches the installer the ordinary way, as an email attachment or a shared file, and the owner attaches it to the Reports Bot's conversation.

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.

The US Department of Energy's consumer guide to home energy assessments asks homeowners, before the assessor arrives, to list the indoor problems they have noticed, such as condensation and uncomfortable or drafty rooms, and to have copies or summaries of recent energy bills ready to share. It says the assessor should begin with a walkthrough of the home (as checked on 15 October 2026).

When the assessor books the visit, that request is the assessor's to make. When a homeowner contacts the installer first, the Paperwork Bot can draft a short preparation note from DOE's list, which the owner edits and sends; the Bot never contacts the homeowner itself. The same list becomes the first two fields of the job file: the problem rooms in the homeowner's own words, and which bills they shared. When the report arrives, the Reports Bot checks whether it addresses each problem room and lists any it does not, so the owner can ask the assessor rather than guess.

The model below follows a single house from the assessor's report to a closed file. The Bots hold only preparation states. Every state that commits the business, or puts a signature on paper, is held by a person.

1. 01

   Report received

   Owner

   The owner

   Advances when

   The owner attaches the assessor's report and images to the Reports Bot's conversation

2. 02

   Findings extracted

   Owner

   Reports Bot

   Advances when

   Each finding becomes a line with its report page; ventilation, combustion and gas items are marked for referral

3. 03

   Proposal drafted

   Owner

   Reports Bot, then the owner

   Advances when

   The owner sets the scope, target R-value and price, and edits the draft before sending it

4. 04

   Fact sheets shown

   Owner

   The owner

   Advances when

   The owner shows the fact sheet for each insulation type before the homeowner agrees, and records how

5. 05

   Attic checked

   Owner

   The installer

   Advances when

   Pre-job photos are reviewed against the owner's checklist

   Ends when

   Suspect material stops the job until the installer decides how to proceed

6. 06

   Installed

   Owner

   The installer and helper

   Advances when

   The install sheet is completed: each area, its depth and, for loose-fill, the bags used

7. 07

   Receipt checked

   Owner

   Paperwork Bot

   Advances when

   Every receipt field is compared with the install sheet and the manufacturer's data; questions go to the installer

8. 08

   Receipt signed

   Owner

   The installer

   Advances when

   The installer dates and signs the receipt

9. 09

   Rebate pack

   Owner

   Rebates Bot, then the owner

   Advances when

   The pack is assembled to the owner's checklist; the owner approves the submission, or hands the pack to the homeowner where the program requires

10. 10

    Closed

    Owner

    The owner

    Advances when

    The owner sends the invoice and files the signed receipt

    Ends when

    Closes only when a signed receipt is on file

An assessor's report is another professional's work, and the installer's proposal is only defensible if every line traces back to it. The Reports Bot works from the PDF and images attached to its conversation and returns a findings list as a reviewable document: each recommendation, the report page it came from, and whether the proposal draft covers it, covers part of it or leaves it out. Where the report says to seal the top plates and the attic hatch, the list carries those words, not a paraphrase that quietly adds rim joists.

Some findings never become proposal lines by themselves. DOE's guide notes that an assessor may test for natural gas leaks and check whether the home is properly ventilated; whatever the report says on those subjects is copied word for word and referred back to the assessor or to a qualified heating contractor, with no threshold of the Bot's own. Where the report and the attic disagree, the file records both and the installer talks to the assessor. The Bot does not pick a side.

Reports and Paperwork sit together in one group chat, which the documentation caps at six Bots and requires at least two; either can post work there or pass it along. A Bot can also message another Bot directly or hand it ownership of a task, which spares the owner from carrying work between them. Cursor's help pages say no switch turns off messaging between Bots; a Bot follows instructions about it. When Reports finishes a findings list, it posts a one-line handoff in the group and Paperwork starts the fact-sheet pack for the proposal.

The helper is not on the owner's account, so the helper sends the attic photos to the owner, who attaches them to Paperwork's own conversation; a Bot's handoff into a group can currently carry only text, though the owner's own messages there may include attachments. Paperwork's silence is not an all-clear: no install starts until the installer has written up an attic check in person. The group never shows approval cards or email drafts: the owner deals with each one in the drafting Bot's own one-to-one conversation. A Monday routine on Paperwork posts the week's open files, any report still waiting for an answer from the assessor, and drafts awaiting the owner. The documentation lets a coordinator Bot in a group assign work, but a Bot that supervises the others is Aevrion's pattern built from those documented pieces, not a product feature.

Where a job qualifies for a utility or program rebate, the paperwork follows that program's rules. Each program sets its own, including who submits, and those rules are not verified here, so the owner writes a checklist for each program from its current terms and revisits it every season. Where the program lets the contractor submit, the Rebates Bot assembles the pack for the portal; where the homeowner must, it assembles the same pack for the owner to hand over. Either way it holds the assessor's report, the signed receipt, the invoice, the photos and any forms the checklist names, with a note of anything missing.

The portal is filled in through the Bot's browser, under supervision, only where the portal's owner allows automated use and after a test run. Some sites refuse automation outright, and logins and two-factor codes are typed by the owner after taking control of the Bot's computer. In this illustration the program lets the contractor submit, and submitting waits for the owner's approval. An approval requested by an overnight routine goes stale after around ten minutes (Cursor's help pages say thirty) without running, so the routine stops at a completed form and the owner submits in the morning. Approving the submission does not undo anything already entered, so the owner reads the filled form before choosing Allow once.

Laid out by day, the pattern is steady: the Bots prepared, compared and assembled between attic days, and everything that committed the business waited for the owner.

The first Bot worth building is the one that turns the assessor's report into a findings list, because every later document copies from it. Give the Reports Bot last month's three reports and compare its findings lists with what you actually proposed; every line it adds or drops is a lasting rule to give it.

If most of your work arrives with someone else's report attached, Aevrion Ops can scope the job file with you: the referral rules, the receipt checklist, and any link to your job software that its vendor's API or terms permit, tested before use. Begin with the workflow automation readiness assessment.

1. When an installer works from an independent assessor's report, the job file has to carry each finding, with its page, into the proposal and the receipt.
2. DOE asks homeowners to list problem rooms and share recent bills before an assessment; those become the file's first fields.
3. Ventilation, combustion and gas findings are copied word for word and referred to the assessor or a qualified heating contractor, with no thresholds.
4. The assessor's business stays off the installer's shared Bot computer; keeping it apart would need its own user account.
5. A Bot's handoff into the group carries only text, so the owner attaches the helper's photos to the Bot that checks them, and approves drafts one Bot at a time, outside the group.
6. Rebate portals are filled under supervision where the portal allows it, and whoever the program names submits; where that is the contractor, the owner approves it.