Two trucks and six hundred program lawns: rounds around rain and rules.

A program lawn company sells each customer a season of treatments and then has to deliver every round inside its window. When rain stops the trucks, the round slides, and the stops at the end of it land on later days. Those later days may fall under a different local rule: in Pinellas County, Florida, nitrogen and phosphorus may not go on turf from the first of June, as checked on 16 October 2026. A pushed round is therefore a new plan, and every stop in it has to be checked again.

Supervised AI assistants can do that checking. In the design below, five Bots re-propose the round, read each moved stop against the company's confirmed rules calendar, flag quotes whose lawn size does not add up, draft renewal letters and summarize the week. None of them chooses a product, decides to apply or sends anything. The company is invented to show a design; it is not a client and reports no results.

Picture a lawn program company in Pinellas County. The owner holds the licenses the state requires for what the company applies and drives one truck; a second licensed applicator drives the other. The book is six hundred residential program lawns, each on six rounds a year, plus aeration and other add-ons sold in the cooler months. There is no office: quotes, round sheets, renewals and customer emails happen in the evenings, from the lawn-care software the company already uses.

Six hundred lawns on two trucks makes each round a few weeks of driving, planned street by street. Three wet days push three days of stops into the next week, and that week's stops after them.

The One-Man Army idea behind the design fits in a sentence: decisions never leave the owner, while every repeating paperwork task is handed to its own named assistant. The pillar sets the model out at length; here it meets a trade where the calendar itself is regulated.

Each one was built by the owner in Grok Bot to Aevrion's design: it has a name, lasting rules it has been told to remember, and a place on the single persistent cloud computer the account provides. The documentation's advice is to begin with the fewest Bots that will do and to add one only when a job has its own goal, tools or schedule, which is why the owner brought them in one by one. The roles belong to Aevrion's design for lawn rounds; none is a product feature.

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.

In this illustration the late-spring round carries nitrogen, chosen by the applicators for that window. It is due to finish on the twenty-ninth of May. Rain stops both trucks on the Tuesday, Wednesday and Thursday of that week, and the last three days of stops have nowhere to go but the first days of June.

The Round Planner works from the stop list in the company's own software, read through a tested custom integration where the vendor's API or terms allow it, or by the Bot working in the vendor's web app under supervision where the vendor permits that. It never works from what it remembers of last week's plan; the documentation is clear that a Bot's memory is no substitute for the authoritative source. Each evening a routine re-proposes the order of the remaining stops, and before the proposal reaches the owner it reads every moved stop against the confirmed calendar. Nobody watches that run. Under the documentation, a request for approval coming from unattended work like this lapses after roughly ten minutes (Cursor's help pages say thirty) and the step is skipped, while a request in a conversation the owner is actively in stays open until answered; so the evening routine is written to need no approval and to finish with a proposal.

The calendar says that from the first of June the county bars nitrogen and phosphorus on turf. So every stop pushed past the thirty-first is marked: this round, as planned, carries nitrogen, and this address will now be served in the county's summer window. The Planner does not decide what happens. It lists the marked stops with their addresses and new dates for the owner and the second applicator, who choose between finishing them before the deadline, changing what that part of the round carries, or holding the fertilizer for autumn. The product and rate are theirs to choose.

The same county page, read on 16 October 2026, makes some weather a rule in any month. Nitrogen and phosphorus may not be applied while the National Weather Service has a severe thunderstorm, flood, tropical storm or hurricane watch or warning in effect, or when two inches or more of rain is forecast within twenty-four hours.

That gives the evening routine a second check. Where a watch or warning is in place for the next day's area, the Planner marks every stop on that day whose round carries nitrogen or phosphorus. Reading the advisory is supervised browser use, subject to the site allowing it and to testing; if the Planner cannot read it, it says so on the proposal rather than assuming clear skies. Whether the trucks go out at all on a showery morning remains the applicators' judgment. The Bot reports conditions; it does not call the day.

Customers whose visit moved get a short delay note, which the Planner leaves as an editable email draft for the owner to send or discard. The documentation describes no telephony, so a customer who rings about a missed visit is the owner's to answer.

The five share a group chat, which the documentation allows for two to six Bots. The Round Planner acts as coordinator, on the model of the documented group in which a coordinator can assign work. When a monthly re-check turns up a changed source page, the Rules Calendar Bot can also message the Round Planner directly, and the handoff is visible in both conversations. Cursor's help pages say no switch turns off messaging between Bots and that a Bot follows instructions about it, so the owner checks that no Bot has been told not to message the others before counting on the direct message.

Approval requests, sign-in requests and email drafts never appear in the group; they arrive only in each Bot's own conversation with the owner, which is where the owner decides. Handoffs posted to the group are text only for now, so when the Quote Check Bot needs another Bot to look at an aerial image, it sends the image to that Bot directly.

New inquiries reach the owner through the website form, passed to the Bots by a custom integration once tested, or through the owner's own notes from a conversation. Customers describe their lawns in rough terms, and the owner measures the turf area before quoting, using aerial imagery or a visit. In this company both figures go on the quote record.

The Quote Check Bot reads each draft quote before the owner sends it and flags any where the reported and measured areas differ by more than a margin the owner set. It also flags a quote with no measured figure at all. The flag says only that the two numbers disagree; the owner decides whether to re-measure, visit or quote as it stands.

The area matters beyond the price. The Pinellas page caps nitrogen at four pounds per thousand square feet per year, and the applicator works out how much product a lawn needs from its area. A lawn recorded at half its true size is a wrong load on the truck as well as a wrong quote. The Bot never does that calculation.

Each program lawn renews on its own anniversary. The Renewals Bot drafts each letter a few weeks ahead from the account's current terms and the prepay option the owner has written down for the year, and leaves it as an editable draft. If the owner has not written terms for a case, such as a lawn that changed size or a customer who missed rounds through rain, the Bot drafts nothing for that account and lists it instead.

Replies reach the owner, who forwards them for sorting; a cancellation, a weed complaint or a pause request goes back to the owner with the account history. Taking payment is not the Bots' job: billing runs in the company's software, reached only through a custom integration if the vendor permits it, and any website payment step is finished by the owner in person, taking over the computer. 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.

Every decision that needs a license stays with the people who hold one: what each round carries, the rate, whether today's conditions allow it, and the record of what went down. Records belong in the company's software, completed by the applicator; the pesticide use records guide in the pest control series shows how a records check can work without a Bot touching the record.

Two logins stay off the shared computer altogether: the state licensing portal and any account that signs records as an applicator. All of an account's Bots use the same cloud computer, including its signed-in browser sessions, and the documentation says separate Bots are not a security boundary.

The Weekly Review Bot builds its digest from the files the others save in the shared workspace, not from memory: rounds moved, marked stops and how the applicators resolved them, flagged quotes, waiting renewals, unconfirmed calendar rows and credential dates due this season. Its model is the Chief of Staff example in the documentation, which briefs a person rather than managing Bots, and it supervises no one.

Before any Bot, look at last year's late spring. How many stops did rain push past the last day of May, what did those stops carry, and who noticed? If the answer is that nobody checked, the rules calendar and the pushed-stop check are the first two pieces to build, and the companion article on the application rules calendar shows how the calendar is researched and confirmed.

The readiness assessment on this site costs nothing and is open to anyone. Put rain-day rescheduling through it: the workflow is rated on twelve fixed dimensions, and the page answers straight away with one of four verdicts, the blockers behind it and what to do next. Expect exception frequency to score poorly, since every wet week is one, and error sensitivity and controls to matter: one missed stop puts nitrogen down in a closed window. Aevrion Ops can then scope the round planner, the calendar and the integration with the company's lawn-care software, subject to that vendor's API or terms and to testing.

1. A rain day moves a program round rather than canceling it, and every moved stop has to be read again against the local rules for its new date.
2. Pinellas County keeps nitrogen and phosphorus off turf through its summer window and, in any month, while certain weather watches or warnings are in force.
3. The Round Planner marks stops pushed into a restricted window; the applicators decide what the round carries.
4. The Quote Check flags quotes where reported and measured lawn sizes disagree, because the applicator's product quantities depend on the area.
5. Customer emails are drafted for the owner, who reads each one and sends or discards it.