One crew and a storm week: the evening desk of an owner-arborist.

An owner who holds the ISA credential and runs the only crew spends the day under trees and the evening on three pieces of paper: the photo estimates waiting to be priced, the check on whether a tree is protected, and the booking for a crane or lift. Each one feeds the briefing the crew lead reads the next morning. Storm week lengthens both the day and the pile.

Assistants can take the reading, sorting and drafting off that desk. They can lay out estimates, apply a city's measuring method to the owner's measurements, draft the crane inquiry and assemble the pack. They do not price, decide that a tree is unprotected, book anything or sign. Nothing below happened: the company, its jobs and its storm are made up to show a design, and no results are claimed.

Picture an Austin yard. The owner holds the ISA credential and appears, by choice, in ISA's public Find an Arborist directory, where listing is voluntary. The crew is a crew lead who climbs and two ground workers. The company owns a bucket truck and a chipper, rents a stump grinder, and hires a crane by the lift from a local crane company when a removal needs one. There is no office staff. Texas does not run an OSHA State Plan, so federal OSHA covers the crew, according to OSHA's State Plans page as checked on 16 October 2026.

Put briefly, the One-Man Army model keeps every decision with the owner and hands each recurring stack of paperwork to a named Bot of its own, as the pillar sets out. In tree work, part of that paperwork fixes where people stand when a trunk comes down.

These four are Bots the owner built in Grok Bot to an Aevrion design. Each has a name, a job, standing rules it has been told to remember, and a seat on one shared persistent cloud computer. The documentation's advice is to start with the fewest Bots that cover the work and add one when a role has settled, so Estimates came first and the rest followed one by one. The four roles are Aevrion's design, not product features.

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.

Crew Day coordinates a group chat of all four. Groups take between two and six Bots, which can post and pass work inside them, and the documentation's own example has a coordinator that can assign work. Week Digest borrows from the documentation's Chief of Staff example, which is a digest that briefs a human; it directs no other Bot, since a supervising chief-of-staff Bot is not documented.

Approval cards, sign-in requests and email drafts stay out of the group and show up in the owner's one-to-one chat with the Bot concerned. Handoffs posted to a group are text-only for now, so Estimates passes a photo to Tree Check in a direct Bot-to-Bot message. Cursor's help pages say no switch turns that direct messaging off; a Bot follows instructions about it. Pictures the crew lead takes travel via the owner, or via a shared folder the owner points the Bots at.

A line of thunderstorms on Monday night leaves the owner with far more estimate requests than one evening can price. Wires, injuries and damaged houses have already gone through the storm triage rules in this series; what reaches Estimates is the ordinary work storms create, such as a split leader, a hanger over a lawn or a tree the customer no longer trusts.

Estimates lays out a sheet for each, in the design the tree services overview describes, and groups them by street so jobs on one road can be priced together and visited in one loop. The owner marks each request as priceable from the photos or needing a visit. For a visit, Estimates drafts an email reply with no date in it; the owner adds a time once the crew's week is known, then sends. Prices go into the job software, which Estimates reads back on the next run rather than remembering, through a custom integration or supervised browser use where the vendor permits it, once tested.

Austin's City Arborist pages, as checked on 16 October 2026, regulate any tree on a one- or two-unit residential lot that measures nineteen inches or more in diameter four and a half feet above the ground. Heritage Trees, which start at twenty-four inches and cover all oaks, pecans, bald cypress and a few other species, have stricter rules. Removing a regulated tree needs an approved Tree Ordinance Review Application first, even when the tree is dead, diseased or an imminent danger, and pruning a regulated tree is capped at a quarter of its canopy without a permit.

The city's method for a multi-stemmed tree is to take the largest stem and add half of each other stem. Suppose the owner measures a storm-damaged live oak at fifteen and ten inches. Neither stem reaches nineteen, but the city's arithmetic gives fifteen plus five, or twenty. Tree Check shows that working, quotes the page it came from and marks the job as likely regulated, for the owner to confirm. The tape measure and the conclusion are the owner's.

If the owner decides to apply, after confirming with the city and the customer whose name goes on the application, Tree Check prepares the packet the city's page lists: each tree's species and diameter in matching order, a photo of each tree from root to crown labeled with species and diameter, and a place for the sketch of the proposed work. Filling the city's portal form by supervised browser use works only where the site allows it; the owner takes over to sign in and presses submit. After a completeness check the city runs a ten-business-day review and may ask to see the tree, so the Bot tracks the status and keeps that oak off the crew's week until a permit exists.

England's rules differ in kind, as the government's guidance (checked on 16 October 2026) shows. A tree under a Tree Preservation Order needs the local planning authority's written consent before it is cut down, topped, lopped, uprooted or wilfully damaged, applied for on the standard form with reasons and evidence; the authority aims to check an application is valid within three working days, and a consent normally lasts two years. Work on a dead protected tree needs five working days' written notice instead, unless there is an immediate risk of serious harm, and dead branches can come off a living tree without notice.

A tree in a conservation area that has no Order needs a section 211 notice six weeks before certain work, unless an exception applies. The notice has no set form, but it must describe the work, identify the trees and carry its date. The authority may make an Order, say the work can go ahead, or let the six weeks run out, after which the work may be done within two years of the notice.

There, Tree Check would draft the notice from the owner's description and track the end of the six weeks and of the two years. The owner sends it and confirms the position with the authority.

One storm removal, a cracked pine leaning over a carport, needs a crane. From the owner's lift notes (the pick sequence, where the crane can set up, what the drop zone must clear) Crew Day drafts an email to the crane company proposing two dates, which waits in the owner's conversation as an editable draft to send or discard. A narrow Ask first rule on external email backs up the remembered rules, as the documentation recommends for sending messages; approving never undoes work already done.

Crew Day marks the booking confirmed only when the owner forwards the crane company's written reply, and any deposit is paid by the owner, taking over the computer if a site asks for payment. Cursor's help pages add that a card saved in the Bot's Vault can be used at checkout without asking each time, so this design saves no card there. The crane company's own booking system has no documented connector; reading it would be a custom integration or supervised browser use where the vendor permits it, subject to testing. When Friday's forecast pushes the slot back a day, Crew Day redrafts the briefing pack for the new date rather than editing the old one.

The briefing pack follows the overview's design, built on OSHA's supervisor list, from the rigging decision and the line distance to a drop zone at least twice the tree's height. In storm week what matters is versioning. A moved crane slot, a new hazard the owner saw on a revisit or an application still pending all produce a new version, and the old one is marked superseded.

The crew lead reads and signs the current version at the yard. If the crew lead finds something at the tree that changes the plan, the work stops on the crew lead's judgment, not the pack's, and the owner records the change and has the pack reissued. The crew lead can be asked about anything in a draft, but drafts from the owner's Bots are sent by the owner.

Week Digest runs as a routine early on Monday, well clear of the documented rule that schedules are at least five minutes apart. It lists the estimates still unpriced, the applications and notices with their next dates, the crane and equipment requests with no written confirmation, and any pack signed in an older version than the latest. Nobody is at the screen for that run, and an approval request from unattended work like it expires after roughly ten minutes (Cursor's help pages say thirty) without the action running, so the digest asks for nothing. Because the documentation describes neither automatic retries nor failure alerts, a missing digest means the owner opening the routine's run history.

Each Bot rereads the job software and the city's status emails the owner forwards every time, because the documentation is explicit that changing facts belong in the source system. The bank and payroll stay off the shared computer, and the owner signs out of the city portal after each submission, because every Bot on it can use every sign-in there and separate Bots are not a security boundary.

Scoring comes before building. The workflow automation readiness assessment rates one workflow on twelve fixed dimensions and answers straight away with one of four results, the blockers behind it and a next step. For this owner the workflow to score is the protected-tree check. Without a written list of the jurisdictions worked in and the page stating each rule, expect rule clarity and data availability to score low; a low rule-clarity score caps the result until the list exists.

An owner who already has that list and wants the four Bots built around it can ask Aevrion Ops for a scoping conversation through the contact page, covering the jurisdiction list, the four Bots' lasting rules and any link to the job software that the vendor's API and terms allow, once tested.

1. In a one-crew company the evening's photo estimates, protected-tree checks and crane bookings decide the next day's briefing; assistants draft and lay out, and the arborist decides.
2. Austin regulates residential trees from nineteen inches at four and a half feet, counts multi-stemmed trees by its own formula, and wants an approved application before removal.
3. In England a Tree Preservation Order needs written consent, and a conservation-area tree needs a section 211 notice six weeks ahead; the Bot tracks the dates and the owner files.
4. Crane inquiries are drafts the owner sends, and a slot counts only when the crane company confirms it in writing.
5. The crew lead signs every version of the briefing pack, and the check at the tree overrides it.