One owner, three painting crews and a rainy week: scheduling the season.

Scheduling a painting business in exterior season is mostly re-scheduling. A wet forecast midweek means every exterior job has to be checked each morning, crews moved, customers told, and anything that depends on a start date checked again. Supervised AI assistants can prepare that daily reshuffle: a forecast check against the owner's product rules, a board of proposed moves, reschedule drafts for customers and a chase for unsigned color selections. What they cannot do is look at a wall. Whether a crew paints today is decided by its lead, on site, against the product data sheet.

Everything below is an illustration: an invented company in an invented week, sketched to show where the assistants' work ends. No real business or measured outcome sits behind it.

In this illustration the owner sells and estimates, and three crew leads run the jobs. The owner's evenings go on proposals, color sheets and the next day's schedule. Three exterior jobs are live this week: a two-story repaint with gables that need scaffold, a 1950s bungalow where the crew will scrape and sand old paint, and a trim-and-doors job due to start on Wednesday. The lead of the bungalow crew holds EPA's renovator credential, and the company holds the firm certification EPA requires.

The One-Man Army pillar describes the model this company follows: the owner holds every decision, and named AI assistants each take one strand of the desk work. This company runs four Bots on Grok Bot. A Weather Bot owns the morning forecast check. A Schedule Bot owns the crew board and the reschedule drafts. A Client Bot owns color chases and customer emails. A Coordinator posts the morning board to a group chat that holds all four and hands out the work. The names and the split are Aevrion's illustration, not documented roles.

Grok Bot's documentation supplies the pieces: a group chat can hold two to six Bots, a coordinator in such a group can assign work, and one Bot can send another a request or pass it a task outright. Bots may message one another, and Cursor's help pages say there is no switch to turn that off; a Bot follows instructions about it. What the documentation does not describe is a Bot that supervises the others. The Coordinator here is Aevrion's pattern built from those documented parts, and it decides only which Bot prepares what, never what the company commits to.

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.

A routine on the Weather Bot runs early each weekday. It reads the forecast for each job's address and compares it with the owner's product table, which records the application limits printed on each product's data sheet. The table, not the Bot, holds the numbers, and the Bot reads it fresh on every run. The output is a hold list: go, marginal or hold for each job and day, with the forecast line and the table row behind each call. If the forecast page will not load, the routine says so and produces no list, so nobody works from yesterday's.

The Coordinator turns the hold list into the morning board and posts it to the group, then assigns the follow-up: moves to the Schedule Bot, customer notices and the color chase to the Client Bot. The owner reads the board before the crews leave the shop.

Monday's board, as the owner reads it (illustrative):

• TWO-STORY

  Go today and tomorrow morning; hold from Tuesday afternoon through Wednesday; Thursday marginal. The crew lead decides on Thursday from the site.

• 1950s BUNGALOW

  Scraping planned to start Wednesday: hold. The new start date needs a pamphlet-window check before it is confirmed.

• TRIM AND DOORS

  Wednesday start: hold. Door color still unsigned.

• RAIN-DAY WORK

  Two interior jobs on the owner's list could absorb a crew on Wednesday if the customers agree. Drafts to both, unsent.

• DRAFTS WAITING

  Three reschedule emails and one color reminder, each in its own Bot's conversation.

This owner keeps a list of interior work for rain days. The Schedule Bot's job is to propose which crew goes where if the rain arrives as forecast, and to draft the messages that would follow. It proposes; the owner and the crew leads choose.

One documented limit shapes the morning. Neither approval requests nor email drafts show up inside a group, so the board can only point at them; the owner opens the Client Bot's own conversation to edit the reschedule emails and choose Send. A second limit shapes the timing. An approval raised by unattended work, whether a routine or one Bot's message to another, lapses after roughly ten minutes (Cursor's help pages say thirty), and the action is simply not taken. The company's rule is therefore that nothing raised before the owner is awake asks to send anything. The routines draft; the owner sends.

The bungalow is where a rainy week becomes a paperwork question. The federal rule for pre-1978 work, 40 CFR 745.84 (read on 15 October 2026), only lets the Renovate Right pamphlet be handed over inside the sixty days that precede the start of renovation, with a signed receipt, or a mailing certificate dated a week or more before work starts, as proof. That sixty-day count runs back from the first day of work, which is precisely the day the rain has just moved.

In this illustration the owner handed over the pamphlet when the contract was signed, and the signed acknowledgment is dated fifty-six days before the original Wednesday start. A start on the following Monday would fall outside the sixty days. The Schedule Bot's tracker catches it and flags the job instead of confirming the date. The owner treats the flag as a reason to give the pamphlet again and get a fresh signature before the new start, and confirms that reading for the program the company works under. The Client Bot drafts the cover email; the owner sends it.

The reshuffle has a second constraint. The records EPA requires under 40 CFR 745.86 include documentation that a renovator holding the credential was assigned to the project and directed the work, so the Schedule Bot's standing rule is that no draft moves the bungalow away from the crew whose lead holds it. The tracker keeps the dates and the file straight; lead-safe practice on site belongs to that renovator. The full lead-safe file is the subject of the painters' RRP article linked below.

On Wednesday the owner considers sending the trim crew to help finish the two-story later in the week, since its gables need scaffold. OSHA's fall-protection page sets six feet as the height at which construction-industry employers must provide fall protection, and OSHA's definition of construction work includes painting and decorating (both as checked on 15 October 2026). Those are federal rules, and this illustration names no state. Twenty-two OSHA-approved State Plans, California's Cal/OSHA among them, cover private-sector workers with their own rules, which must be at least as effective.

The Schedule Bot cannot judge whether a scaffold is sound or a crew is equipped, and it is not asked to. What it can do is carry the estimate notes onto every move it drafts: work above six feet, the access equipment the estimate assumed, and an unchecked line for the crew lead to confirm the fall protection before the move goes ahead. Here the lead of the trim crew declines, because the equipment is on another site, and the owner keeps the crews where they are. That is the system working.

The trim-and-doors customer chose the trim color weeks ago and has been deciding on the doors since. The Client Bot's chase is simple: compare every booked start date with the job's selection sheet, and draft a reminder for each one still unsigned. The reminder is an editable email draft naming the two door samples the crew lead photographed.

Those photos raise a documented detail. Bot-to-group handoff messages are currently text-only, and the Bots belong to the owner's account, so the owner forwards the crew lead's photos to the Client Bot directly, and the Coordinator's board mentions them only in words. The customer signs the door color on Wednesday evening. The Client Bot records the signed selection on the job file, and the owner confirms the Thursday start.

The documentation's own Chief of Staff example is a digest that briefs a person on what changed, and on Friday the owner asks the Coordinator for exactly that: every move made, every hold called and every draft still open, one line per job. The owner reads it before planning Monday.

Friday's digest, as the owner reads it (illustrative):

• 1950s BUNGALOW

  Start moved to Monday. Pamphlet given again on Thursday; the fresh acknowledgment is signed and in the job file. The credentialed lead's crew is still assigned.

• TWO-STORY

  South side finished on Tuesday before the rain. North side and gables wait for the crew lead's call on Monday morning; the scaffold stays up, and the crew lead checks it first.

• TRIM AND DOORS

  Door color signed on Wednesday evening, work started Thursday. Doors booked for Monday if the crew lead calls it a go.

• STILL OPEN

  One interior customer has not replied to the earlier-start offer; a follow-up draft waits in the Client Bot's conversation.

Begin where this week began: the product table, written from the data sheets, because every hold the Weather Bot called stood on one of its rows. The morning hold list can follow, read by the owner before the crews leave; then the reschedule drafts, the pamphlet check and the color chase. A Coordinator only earns its place once there is more than one Bot to coordinate.

Aevrion Ops can work through exactly this with a painting company owner: walking through a real week of moves, choosing which desks an assistant prepares, and connecting the Bots to the scheduling and customer tools already in use, provided the vendor's API or terms allow it and the connection has been tested. The readiness assessment linked below is a good first conversation.

1. In exterior season the schedule is rebuilt every morning; assistants can draft the moves, and the crew lead makes the weather call on site.
2. The forecast routine reads the owner's table of data-sheet limits on every run and produces no list when a source will not load.
3. Drafts and approval requests stay in each Bot's own conversation; the group board only points to them.
4. Rain that moves a pre-1978 start date is a reason to recheck the sixty-day pamphlet window under 40 CFR 745.84.
5. Federal OSHA requires employers to provide fall protection at six feet in construction work, which includes painting; states whose OSHA-approved plans cover private employers set their own rules, and a crew move carries the access line for the crew lead to confirm.
6. The owner sends crew photos directly to the Bot that must inspect them, because group handoffs are currently text-only.