A mini-ex, a skid steer and three jobs: the office runs from the cab.

This is an illustration, not a client story. Picture an owner-operator, here called Ray, with a mini-excavator, a skid steer, a trailer and no office staff. This week he is digging footings for a general contractor's addition, regrading a back yard that drains towards the house, and opening the tank hole and trenches for a septic installer. Each job has its own locate ticket, its own permit holder and its own inspection, and Ray spends most daylight hours in a seat where he cannot type.

Three Bots that Ray creates under an Aevrion pattern keep the paper moving while he works: a Locates Bot for tickets and permit look-ups, an Estimate Bot for quotes and change orders, and a Schedule Bot that lays out each day against the weather and the inspections other trades have booked. They prepare, track and draft. Every decision on the ground, from whether a trench needs protection to whether the morning is a dig day, stays with Ray.

Aevrion's one-man-army model gives a solo owner a few supervised AI departments, each with a clear job and a clear limit, so that the owner stays the decision-maker without also being the clerk. The pillar article sets out the full model. In excavation the fit is unusually literal: the owner is physically unavailable for hours at a stretch, and the decisions that matter most are made with a machine idling, not at a desk.

None of the three permits is Ray's. The general contractor holds the building permit and books the footing inspection. The septic installer holds the septic permit and works to the system designer's plan. The homeowner simply wants water to stop pooling against the foundation, and whether that regrade needs a permit at all depends on where the house stands. What Ray holds on every job is his own locate ticket. Whether a general contractor's ticket can cover a subcontractor's digging is a state rule; the locate-ticket guide in this series gives one state where it cannot, and Ray confirms his own.

In Grok Bot each Bot is a named teammate with its own conversation and standing rules it keeps in memory, working on a persistent cloud computer that every Bot on Ray's account shares. Ray puts the three in one group chat; the documentation allows two to six Bots in a group and says a coordinator there can assign work. The Schedule Bot plays that part in Ray's design: each evening it posts tomorrow's order of work and asks the other two for what it needs, such as which tickets are fully answered and which quotes are still unsent.

The group carries text. The documentation says a Bot's handoff to the group is text-only, so when the Estimate Bot needs a site photo Ray took, the image goes to it directly from Ray or in a Bot-to-Bot message. Cursor's help pages say no switch turns off messaging between Bots; a Bot follows instructions about it. Approval requests, logins and email drafts never appear in the group at all, so Ray answers them in each Bot's own conversation. One raised while he is in that chat waits for him; one raised by work another Bot started expires after about ten minutes (Cursor's help pages say thirty) and does not run.

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.

Ray reads the morning on his phone. The documentation says approval cards on iPhone carry the same Allow once, Always allow and Deny choices as the desktop, and a site photo reaches a Bot the way any attachment does: Ray adds it to that Bot's conversation.

What he reads is short by design: which jobs have every utility answered on their tickets, which are still waiting, what the Schedule Bot proposes for the day and which drafts are waiting for him. An approval raised in a chat he is in waits for his answer, even while he finishes a load. A card from a routine that ran before he woke is different: unanswered for roughly ten minutes (Cursor's help pages say thirty), it lapses without acting. Either way, every filing and every message to a customer or a contractor goes out in his company's name, so Ray sends it himself.

The general contractor emails a footing inspection date. Ray pastes it into the Schedule Bot's chat, and the Bot works backwards: the footing has to be dug, cleaned out and open on that morning, so the dig day has to fall after Ray's ticket allows digging and before the inspection. It proposes a day, notes which utilities on the ticket have not yet answered, and drafts a short reply to the contractor confirming the plan. Ray edits one line and sends it.

On site, the depth of the footing and the ground it is cut in are Ray's judgment. Collapse is the hazard OSHA's trenching page puts first, with sloping or benching, shoring and trench boxes as its answers, and Ray's state may run its own plan with its own standard. Whether this cut needs any of them is the competent person's decision on site wherever anyone will work in the trench, and in this illustration Ray is the person his company names for that role. The Bots record the planned depth and keep any inspection notes he dictates; they do not weigh in.

The regrade began as a quote. Ray shot grades on his site visit and noted where the swale would run, where the downspouts would tie in and how much soil the low side needed. The Estimate Bot turned those numbers into a draft using his rate sheet, listing the cut, the fill, any imported topsoil, the machine hours and the seed and straw, and asked one question before finishing: was the spoil staying on the lot or leaving in trucks? The answer changed the price, so the Bot waited for it rather than guessing.

Whether the regrade needs a grading permit has a local answer, and two published examples show how far apart those answers sit (both as checked on 16 October 2026). Sacramento County requires a grading permit when a project grades, fills or excavates three hundred and fifty cubic yards or more, or clears and grubs an acre or more, and exempts footings and basements under a valid building permit. The City of Vancouver, Washington requires one for nearly all projects that disturb or move more than ten cubic yards; footing work inside an approved residential building permit escapes a separate grading permit only when every listed condition holds, among them no structural fill, no more than fifty cubic yards of excavation, a slope under ten percent, no critical areas and no retaining or surcharge conditions. Ray's Locates Bot looks up his own jurisdiction's published rule, links it to the job and records what Ray concluded. Where water goes once the grade changes, including onto a neighbor's lot, is for Ray to settle with the homeowner and, where the jurisdiction asks for one, an engineer's drainage design.

The septic installer sends the system designer's plan and the inspection window the installer has booked. Ray's part is the excavation for the tank and the trenches; the permit, the design and the installation belong to the installer. The Schedule Bot proposes a dig day that leaves the installer time to set the tank before the inspection, and the Locates Bot checks that Ray's ticket describes the whole area the plan covers, not just the tank hole, because a ticket that names too small an area protects too little ground.

This is where the septic trade's own records start. Aevrion's guide to septic companies covers the installer's side of the work, and this article stays with the dig.

On Wednesday it rains through the afternoon. The footing is already open, and OSHA's excavation rule wants a competent person to look at it again once the storm has passed; Ray, as that person, walks it on Thursday morning and dictates a note the Schedule Bot files with the job. Ray will not regrade wet clay, so the Schedule Bot drafts a new order for the rest of the week: footing cleaned out Thursday, septic dig Friday, regrade pushed into the next week.

The push creates the week's one real risk. Ray's ticket for the regrade would lapse before the new dig day, and the Locates Bot, reading the dates in its log, flags it in the evening list with the state's rule for refreshing a ticket linked beside it. It drafts the request; that evening Ray reads it in the Locates Bot's chat and tells the Bot to file it, answering the approval card it raises while he is there, and the login on the state center's site is his to complete. The locate-ticket guide in this series covers that log, and the rules that set its dates, in full.

In this illustration, Ray's office does not begin with three Bots. It begins with the question his week kept asking: for each job, who holds the permit, which inspection date the dig works back from, and who tells Ray when that date moves. If those answers reach him in messages he can paste into a chat, a Schedule Bot can work from them; if they arrive as a word across the site, writing them down comes first.

Those answers are what a scoping conversation with Aevrion Ops works from: which Bot comes first, what each one may draft and what always waits for the owner, and whether the state center's website or the company's estimating software can be reached by supervised browser use or a custom integration where the vendor permits it, subject to testing. The contact page is the place to start that conversation.

1. On a residential excavation week, each job answers to a different permit holder, and the excavator holds a locate ticket on every one.
2. Three Bots fit the cab: a Locates Bot, an Estimate Bot and a Schedule Bot that posts the order of work in a group the owner reads.
3. Group handoffs are text-only, and approvals, logins and email drafts stay in each Bot's own conversation with the owner.
4. Whether a trench needs protection is the competent person's decision on site, and when the ground is dry enough to dig is the owner-operator's.
5. Grading-permit thresholds differ widely: Sacramento County starts at three hundred and fifty cubic yards, Vancouver in Washington above ten.
6. A rain delay can push a dig past its ticket's life, so the log's dates matter more than any single morning's plan.