A two-crew mover in June: twelve moves, three interstate, nothing unsigned.

In peak season a small mover lives on the board: two crews, two trucks, pack days and load days, and customers whose closing dates will not move. Most of June can be rearranged when something slips. The interstate moves cannot be rearranged on paper. Under the federal rules for household-goods carriers, each needs a bill of lading that the customer has been given, has signed and has dated at least three days before the scheduled loading (49 CFR 375.505(h), the text as checked on 15 October 2026).

What follows is one invented June in one invented company, sketched to show how supervised AI assistants can carry the board and the paperwork list while the owner keeps every signature. Nothing in it describes a real mover, a real customer or a measured outcome.

In this illustration the owner does the surveys and the estimates, two crew leads run the trucks, and a part-time packer fills gaps. Nine of June's twelve moves stay inside the state; three go interstate, loading on the 9th, the 17th and the 26th. The local moves answer to whatever the state requires, which this page does not cover, so the federal paperwork below concerns only the three.

The owner holds every decision under the One-Man Army model, while named assistants each take one slice of the desk; the pillar article explains it. Here the owner has created three Bots in Grok Bot, following Aevrion's pattern, and all three share the account's single persistent cloud computer: Estimate turns survey notes into estimate packets, Paperwork keeps the interstate document list, and Dispatch proposes the crew board.

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.

Dispatch builds the month from the booked jobs and three lasting rules the owner gave it to remember, which guide the Bot but enforce nothing: each crew lead stays with their own truck, a pack day falls the day before its load wherever possible, and an interstate load is never paired with a second job that day. The result is a proposal with the conflicts marked, so the owner still edits the board before any crew lead sees it. The three interstate rows looked like this on 1 June.

The spine of the month is a daily at-risk digest that Paperwork posts each weekday morning. It is an Aevrion pattern running on a documented routine. A Grok Bot routine fires on the owner's chosen timetable, and the documented minimum gap between runs is five minutes, a floor a once-a-day digest never comes near. Among the documentation's example roles, Chief of Staff produces a source-linked digest of what changed and what needs attention, written for a person to read; this list does the same job for the owner and directs none of the other Bots.

One house rule shapes it. The owner's target for a signed bill of lading is five days before loading, so the regulation's three-day floor is never the working deadline. Red means a bill of lading still unsigned with that floor two days away or less. Amber means any other missing document for a move loading in the next three weeks.

The digest on 5 June, as the owner read it before the crews left (illustrative):

• RED: INTERSTATE 1

  Loads on the 9th, so the three-day floor falls on the 6th, and the bill of lading has not gone out. A cover email is drafted; the bill of lading itself waits for the owner to complete and sign.

• AMBER: INTERSTATE 2

  Loads on the 17th. The customer asked to skip the survey, but no written, signed waiver is on file, so the estimate still has to rest on a survey.

• AMBER: INTERSTATE 3

  Booklets went as links, and the signed, dated receipt the rule asks for in that case has not come back.

• CREW BOARD

  The clash on the 17th is unresolved. Dispatch has two versions of that day waiting in its own conversation.

• COULD NOT CHECK

  Nothing today. On a morning when the job system cannot be read, this line says so and the digest stops there rather than reporting from an old copy.

A routine that tried to send the cover email for Interstate 1 would raise an approval, and at seven in June the owner is usually in the yard. The documentation is specific about that case: when work nobody started in person, a routine for instance, raises an approval, the card goes to Expired after roughly ten minutes (Cursor's help pages say thirty) and whatever it guarded does not happen. So the digest never asks. It drafts, lists and stops, and the owner works through the drafts at the first break, choosing Send on each email after reading it.

The bill of lading is a different kind of document from the cover email. It is the contract, and the owner completes it, signs it and sends it. The same applies to every estimate and waiver. No Bot in this company sends a binding document, and none of them quotes a price.

The clash on the 17th is typical of June. Interstate 2 needs Crew B all day, and a local two-bedroom move had been booked for that morning before the interstate date was fixed. Dispatch lays out two versions: push the local move to the 18th, or give it to Crew A, whose own job that day should be done by noon, with the packer added. Each version shows which customer would have to be told about a change and where the overtime falls under the owner's own rules.

Choosing is the owner's call, and so is ringing the local customer if their slot moves. In the owner's version the local job keeps its date and goes to Crew A. Dispatch then drafts a short confirmation for that customer, which the owner edits and sends. The crew leads hear about the change from the owner, not from a Bot.

The customer on Interstate 1 signed the bill of lading on the afternoon of 5 June, four days before loading. On the 9th the crew lead opens the garage and finds it full of boxes and a workbench that never appeared on the video survey. If the carrier agrees to take goods the binding estimate does not list, the rules leave three paths, every one of them before loading: keep the binding estimate as it stands, write a fresh binding estimate itemizing the extra goods for the customer's signature, or settle on paper that the original will be handled as non-binding (375.403(a)(6)). Where a new estimate results from additions on the day of the move, the matching changes to the bill of lading do not start a new three-day period (375.505(h)).

The crew lead photographs the garage and sends the pictures to the owner, who passes them to Estimate. Group handoffs are currently text only, so if another Bot needs a picture, Estimate sends it directly to that Bot. Estimate drafts an addendum listing the added items with the price lines empty and the three paths set out, none chosen. The owner prices it from the tariff, picks the path with the customer, and both sign before anything is loaded. Paperwork then records the date, time and manner in which the new estimate was prepared, which the regulation says a carrier should keep.

The three Bots share a group chat, which the documentation allows for two to six Bots, and Dispatch acts as its coordinator, a role the documentation also describes: a coordinator in a group can assign work. When the owner moves a load date, Dispatch posts the change and Paperwork recounts that move's deadlines from it. Bots can also write to one another directly and hand over a task outright. Cursor's help pages say no switch turns off direct messages between Bots; a Bot follows instructions about them.

Some things never travel through the group. The documentation keeps approval requests, email drafts and login requests out of group chats, which leaves each draft in the conversation between its own Bot and the owner. A Bot's handoff into the group currently carries text only, so a picture the owner has passed to one Bot reaches another by direct message, although the owner's own messages in the group may carry attachments. And a supervising Bot that directs the others is not something the documentation describes; Dispatch's coordinating role is an Aevrion pattern assembled from documented pieces, and only the owner decides anything.

The three Bots share one computer, which is not a security boundary, so the deposit account was never put there: any payment step goes to the owner by takeover, and the banking login lives under a separate user account. 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 booklet receipt for Interstate 3 came back on the 8th, its bill of lading was signed on the 19th, and the truck loaded on the 26th under a non-binding estimate. The scale ticket put the shipment above the estimated weight. The federal rules have a ceiling for exactly this. Offered one hundred ten percent of the non-binding estimate on a C.O.D. shipment, together with the price of anything the customer requested once the bill of lading existed and any impracticable-operations charge, the carrier has to release the goods; and the impracticable-operations part demanded at the door is held to fifteen percent of everything else owed that day (375.407(a), (d)). The form of payment is the one agreed at the estimate unless the customer agrees in writing to change it, and the bill of lading itself states the most the carrier will demand at delivery (375.505(b)(11)).

Paperwork prepares a one-page delivery sheet for the crew lead from the signed documents: that maximum, the agreed form of payment, and any services added after signing, with the paperwork behind each. The crew lead collects at the door, not a Bot. Anything above the ceiling waits for a later bill, which under the 2022 changes, as ATA describes them, takes the form of an invoice. Paperwork drafts that invoice from the weight ticket and the tariff lines the owner priced, and the owner checks every figure before it goes.

A sensible first month runs the at-risk digest alone, in read-only form, because the deadline it watches is the one that cannot move. Estimate packets come next. The crew board comes last, because it needs the most of the owner's judgment written down first.

A moving company's owner can scope this with Aevrion Ops: turning the federal sections that apply into the digest's rules, deciding which three Bots to create and where each must stop, and connecting the moving CRM and survey tool in use, subject to each vendor's API or terms and to testing. The contact page is the way to start that conversation.

1. In a busy June much else can be reshuffled; an interstate move's bill of lading has to be signed and dated by the customer no later than three days before the scheduled load.
2. A daily at-risk digest, an Aevrion pattern on a documented routine, lists every unsigned interstate document against a house target set earlier than the federal floor.
3. The digest drafts and stops, because an approval card raised by an unattended routine lapses in roughly ten minutes (Cursor's help pages say thirty) with nothing done.
4. Dispatch proposes versions of a clashing day; the owner chooses, tells the customer and tells the crews.
5. On a non-binding delivery the crew lead works from a sheet showing the most that may be collected at the door; the balance is invoiced later, checked by the owner.
6. When goods appear on load day, the owner settles one of the three binding-estimate paths with the customer before loading, in writing where the path requires it; Estimate drafts the list of additions.
7. The group chat shows handoffs, but drafts and approvals stay one-to-one, crew photos reach a Bot through the owner, and the shared computer is not a security boundary.