We delivered an AI Roast Season Manager for a five-person Awendaw oyster roast caterer whose AI had been telling customers they were booked for five weeks while nothing reached the calendar -- one that now reads every booking back before it says the word, tests its own connectors at six each morning, and orders the bushels and the crew the moment a deposit lands.

His grandfather picked oysters by hand off the banks of Bulls Bay and sold them by the bushel from the back of a truck on Highway 17. He started roasting them for church fundraisers in Awendaw in his twenties, on a sheet of steel over a fire pit, and in 2017 he turned it into a business: a trailer with a roasting table built to his own drawing, a steam cooker, forty shucking knives and a stack of wet burlap. Five people work for him year round. On a Saturday in season it is fourteen.

Last season he did 162 roasts, from backyard birthdays in Hollywood to 300-guest weddings on Wadmalaw. Almost none of them begin with a phone call. Four out of five arrive as a message on Instagram or Facebook, usually at night: a photo of a backyard, a date, a guest count with a question mark. Last March he set up Muse, Meta's personal agent, on his own account to answer them, and through the summer it did.

It quoted, sent a deposit link and put the roast on the calendar. Then, in early September, he changed his email password after a phishing scare. The calendar connector lost its permission and said nothing. Muse kept answering messages, kept collecting deposits and kept telling people they were booked, and for five weeks nothing it booked reached the calendar.

It was also still quoting last season's $34 a guest; he had raised it to $38 in August when bushels went up. He found out on October 9, when a bride's mother called his cell to ask what time the trailer would arrive for a roast nobody on his crew had heard of. By then 23 deposits sat in his payment account against a calendar that knew about 14 of them, the first Saturday in November held three roasts for a rig that can run two, and nineteen bookings were priced $4 a guest low. He brought his laptop to Jessen Lane on October 13 and started the fix himself, with one of us beside him.

Re-permissioning the calendar took ten minutes. Reconciling 23 deposits against messages, dates and guest counts was where it got strange, and he slid the laptop across the table for the rest of the hour. The repair was not the password. It was that nothing had been watching the connection.

Now every booking is read back: Muse writes the roast to the calendar, reads it back, and only then tells the customer the word booked. If a write fails it stops taking deposits and texts him. Every morning at six it tests each connector, and the price lives in one sheet he edits, not in its instructions. A message arriving is the trigger.

It asks for the date, the count and the address, quotes from the sheet -- a bushel for every five guests, crew and tables included, a mileage fee past thirty miles -- and sends a 25 percent deposit link. When the deposit lands it books the date, orders the week's bushels from his harvester, texts the crew their call time, and sends the host one page: twenty feet of flat ground, a hose, nowhere under the live oaks. His line is written down. It never confirms a date without the deposit and the read-back.

It never books more than two roasts a day or more bushels than the harvester has allocated for that week. It never refunds, discounts or answers a complaint. He honored the nineteen low quotes, and he called the third November family himself and moved them to the Friday with $150 off. On Saturday, October 24, he ran a 240-guest wedding roast on Wadmalaw from three in the afternoon until past eleven, phone in the truck.

Thirty-one messages came in. It booked four roasts, offered a Friday to two people who wanted a full Saturday, and one took it. At 8:40 the harvester texted that rain had closed his beds through Wednesday. It moved Tuesday's corporate roast to the backup harvester in McClellanville he had approved in the spring, and left him one line about it.

That is the whole report now: one text at 6:30 each morning, usually empty. On October 28 the morning test caught the payment connector expiring; it stopped, texted him, and he reauthorized it at a red light on Highway 41. Since the fix, 38 roasts have been booked and every one was on the calendar before the customer heard the word. "I spent five weeks thinking it was handling things," he said.

"Now it tells me when it isn't, and that's the part I trust."