Who can diagnose foundation failure, and where AI intake has to stop.

Who can diagnose foundation failure? In North Carolina, the Board of Examiners for Engineers and Surveyors puts that call with a professional engineer (PE): its guidance is that only a PE who has evaluated the conditions should say a foundation has failed or needs structural repair, and that contractors and home inspectors who suspect trouble should pass the matter to one. The source is the board's Foundation Repair Guidelines, in the version revised on 22 October 2024, as checked on 15 October 2026. Rules vary by state, and this article describes no other state's position.

For an AI intake assistant the consequence is simple to state and easy to break: when a homeowner sends a crack photo, the reply books an inspection and, where the inspector suspects a structural issue, leads to a referral. It never offers a diagnosis, not even a reassuring one. This article is not legal advice; a company confirms its own state's rules with that state's board or a lawyer.

The guideline is an interpretative guide to North Carolina's engineering and surveying licensing act, written to help engineers and engineering firms comply. Read for intake purposes, it sets out five points, paraphrased here.

It says nothing about software or AI. The cautious reading, and the one this article takes, is that a sentence sent in a company's name is the company's statement, whoever or whatever drafted it.

• THE STATEMENT

  Failure, or the need for structural repair, is for a PE to declare after evaluating the house; a non-engineer who suspects either makes a referral.

• RESPONSIBLE CHARGE FROM THE START

  From the very first analysis, including the evaluation of pier numbers and pier locations, the work is done by a PE or by someone working under that engineer's responsible charge.

• THE CONTRACTOR'S PART

  Contractors may look at the house, reach an initial view and send the matter to a PE if a structural problem is suspected; working out the cause and designing the fix belong to the engineer.

• PRODUCT SPECIFICATIONS

  Installing a manufacturer's pier or grout to its specification is not enough on its own, because the PE must account for the actual field conditions.

• HOME INSPECTORS

  An inspector holding the state's license may flag a possible foundation problem; the client should then go to an engineer for an evaluation.

The board links the statement to an engineer's own evaluation. A photo taken by an anxious homeowner is not an evaluation, and an assistant reading it has evaluated nothing. Between the photo and any statement about the structure sit two human steps: the contractor's inspection and preliminary assessment, and, where a structural issue is suspected, the engineer's evaluation. The table shows how a draft reply handles six messages a homeowner might send, in an Aevrion pattern for intake.

Grok Bot, an agent product, is built from durable, named Bots that run on a persistent cloud computer. Its documentation says to tell a Bot its standing rules and boundaries in chat and ask it to remember them, with one-off instructions kept to ordinary messages. Under Aevrion's pattern the owner creates an Intake Bot and gives it lasting rules that might read, in the owner's words: never state or suggest a cause, a severity, a repair method, a quantity, a price or a result; never describe a crack from a photo; record what the homeowner says in their own words; offer an inspection; send any message about safety straight to the owner with nothing drafted.

A remembered rule shapes what the Bot tends to write; it is not a lock, and a wrong sentence can still appear. The owner therefore reviews every homeowner draft before it goes out. A Bot's email appears in its conversation as an editable draft with recipients and body, and the owner chooses Send or Discard. Because approval in Grok Bot is set per tool and per level of risk rather than applied to everything, the owner also puts a stop in front of any message leaving the company.

The documentation describes no telephony: the assistant takes no calls, leaves no voicemail and sends no texts, so phone inquiries reach it only as a note somebody wrote.

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.

The sequence below is an Aevrion pattern. Each step names the decision it settles and what exists afterwards; the Bot's steps are all preparation.

1. 01

   Capture

   Decides

   Has the inquiry reached the Intake Bot?

   Output

   The message and photos attached to its conversation by the owner, or copied to the shared workspace by a custom integration

2. 02

   Screen

   Decides

   Does anything match the owner's escalation list, such as a safety worry?

   Output

   Either an escalation to the owner with nothing drafted, or the next step

3. 03

   Record

   Decides

   What exactly did the homeowner say?

   Output

   An intake record in their words, with photos filed and no description of them added

4. 04

   Draft

   Decides

   What can honestly be offered?

   Output

   A reply offering inspection windows read from the company's calendar through a tested custom integration, or supplied by the owner, and asking what is missing

5. 05

   Review

   Decides

   Does the draft contain anything on the never list?

   Output

   A reply the owner has edited and sent, or discarded

6. 06

   Inspect and refer

   Decides

   Is a structural issue suspected, or already flagged?

   Output

   The inspector's decision, and where it is yes, a referral pack for the PE that the owner sends

A short morning routine keeps the sequence honest. It lists inquiries with no reply sent, drafts waiting for review, and inspected jobs with no referral decision recorded. The documented floor between scheduled runs is five minutes, which a once-a-day check never approaches. If the inquiry folder or the calendar cannot be read, the routine reports the failure instead of working from yesterday's copy, since what a Bot remembers is not, in the documentation's terms, an authoritative source.

Nothing alerts anyone if a run fails: the documentation describes no automatic failure alerts. So when the morning list does not arrive, the owner opens the routine's run history and looks for the failed run. An approval the routine raises before anyone is at a desk times out after around ten minutes (Cursor's help pages say thirty), leaving the action undone, so the routine only drafts.

North Carolina's guideline is one board's reading of one state's statute. A company working elsewhere confirms its own position with its state's engineering board or a lawyer before writing its intake rules; this article does not say what any other state requires. Using North Carolina's line as a company-wide floor is a business choice the owner can make, not a statement of law anywhere else.

Neither choice belongs to an assistant. The Bot does not work out which state's rule governs a job, and it does not soften the never list for a job in another state. The broader question of how much authority to give an AI agent has its own article in Aevrion's insights.

Collect a week of real inquiries and the replies that went out. Mark every sentence that stated or hinted at a cause, a severity, a repair or a result. That marked-up week is the first draft of the Intake Bot's lasting rules, and the replies that did it well are its examples.

With a foundation company, Aevrion Ops can work through that rule, set up the Intake Bot and the points where it must stop for approval, and link it to the existing inbox and calendar through custom integrations that each vendor must permit and that are tested before use. Begin with the readiness assessment for workflow automation.

1. In North Carolina, the engineering board's guideline says only a PE who has evaluated the conditions should state that a foundation has failed or needs structural repair (revised 22 October 2024, checked 15 October 2026).
2. Contractors look, form an initial view and refer; home inspectors note and refer; pier number and location sit under a PE's responsible charge.
3. A crack photo is not an evaluation, so the honest intake reply is an inspection booking and, where needed, a referral.
4. The no-diagnosis rule is one of the Intake Bot's lasting rules, but a remembered rule is not a lock, so the owner checks every draft.
5. Rules vary by state; the owner confirms their own state's position, and the Bot never decides which rule applies.