"Smart irrigation" usually means a timer with a weather app: it skips a scheduled run if rain is forecast, and otherwise does what it was always going to do. That is automation. It is not a decision.
Here is what an actual decision looks like: the one a Greensward estate makes in the small hours of every morning, while the household sleeps.
The night before
The thinking starts the previous evening. An AI agronomist sits down, so to speak, with everything known about the estate: the soil moisture readings that have been arriving from sensors at root depth all day, the local forecast, what the weather has actually done recently, the season, the grass, and anything the greenkeeper has logged: a feed, a treatment, a note that one lawn is being rested.
From all of that it writes a watering plan for the days ahead: which zones, how much, and why, with the reasoning recorded in plain English, not buried in a log file. If the soil is holding well and rain is due Thursday, the plan may be to do nothing at all. Doing nothing, on purpose, with a written reason, is one of the most valuable things an irrigation system can do.
5am: the interrogation
But the AI does not open valves. At Greensward, the AI proposes, and a separate, deliberately unintelligent system disposes. Every proposed watering run is interrogated by a deterministic referee: a fixed chain of safety gates, the same questions in the same order, with no creativity permitted. Among them:
Is it frosty, or about to be? Watering onto frost damages turf. If there's any frost risk, nothing runs, and nothing can override that. Not the AI, not an enthusiastic schedule, nothing.
Is the data fresh? If a sensor has gone quiet, the system does not guess what the soil is doing. Stale information is treated like frost: an absolute stop.
Has it rained, or watered, recently? Rainfall, and any watering already delivered, count against today's need. The sky's contribution is checked before the system adds its own.
Is this the right time? Watering belongs in the early-morning window, when evaporation is lowest and water pressure is kindest. Outside that window, requests wait.
Does a valid plan exist? No run happens "just because". Every drop of water traces back to a written plan with written reasoning. If there's no current plan, the answer is no. Not a shrug and a default schedule.
What does the soil say right now? The final word belongs to the sensors. If the root zone is already where it should be, the run stands down, whatever the plan expected yesterday evening.
Only a proposal that survives every gate becomes water on the lawn. If any single gate objects, nothing happens, and the objection itself is recorded, so there is never a mystery about why the system did or didn't act.
5:40am: the account
By the time anyone is awake, the morning's decisions are written up. Not telemetry. An account. The east lawn received twelve minutes because the root zone had dropped below its target and no rain is expected before the weekend. The front garden was skipped; Tuesday's rain is still holding. The owner can read it over coffee. The greenkeeper can read the longer, professional version. Either can ask why, and get an answer.
That, in the end, is the difference between a smarter timer and an autonomous system. A timer executes. An autonomous system decides, and a trustworthy one shows its working, accepts being overruled by its own safety gates, and treats not watering as a decision worth making well.