After the presentation, Zion joined her parents in a quieter room behind the stage. She had watched the questions and seemed more thoughtful than excited. Darius asked how she felt about the announcement. "I think everyone wanted you to say you beat them," she replied.
"And you kept trying to explain what you built instead." Joy smiled at that. Darius told his daughter that winning a headline was not the same as building something good enough to last.
They ate a late lunch together before the family returned to California. For the first time in several days, Darius sat through an entire meal without looking at his phone. Zion told him about a classmate's disastrous attempt to make a model wind turbine spin indoors, and Joy described the stubborn leak that had reappeared beneath the kitchen sink. Darius listened, asked questions, and found himself laughing at ordinary problems. He realized how much of his own life he had nearly allowed the airport incident to occupy.
On the flight home, he boarded without trouble. He found his seat, showed his pass, and accepted a glass of water from a flight attendant who did not know his name beyond what appeared on the reservation. The ease of it should not have felt like a gift, but after the previous week it did. He watched Zion settle by the window and Joy arrange a book on her lap. Then he leaned back and allowed himself to close his eyes while the plane taxied toward the runway.
The first month after the announcement was not the triumphal procession the news coverage implied. Freeman Systems had won the right to begin a vast project, which meant its people were now responsible for the consequences of every promise made in Dallas. Contracts had to be translated into staffing plans, data security agreements, testing schedules, and budgets that could survive contact with actual operations. Ameris had to provide access to systems that had grown over decades under different managers with different standards. Darius spent most of his time in rooms where people argued about details the headlines never mentioned.
One early problem came from a regional cargo hub whose shipment records used inconsistent codes for weather-related delays. A forecast model could learn from those records, but it would learn patterns that mixed genuine weather disruptions with unrelated staffing shortages. Anika's team identified the issue before deployment and asked for a pause. Several Ameris managers objected, concerned that the delay would move the public rollout beyond the quarter they had promised investors. It was the kind of pressure Darius had spent his career learning to recognize.
He joined the technical call and listened while the managers argued that a small amount of imperfect data was normal in any system. Anika agreed and explained why this particular error was not small: it would cause the model to suggest changes based on the wrong reason for a delay. An Ameris executive asked whether they could release the tool with a disclaimer. Darius asked whether the people making flight and cargo decisions would understand what the disclaimer meant when the system presented a confident recommendation. Nobody answered immediately, and he knew he had heard that silence before.