That week Sophie asked why everyone kept talking about Boston. Daniel told her the doctors there knew how to help a heart shaped a little differently from most. She asked whether her heart was bad. He said no; it had worked very hard, and the doctors wanted to help it work more easily. Sophie considered that answer for a while and then asked whether a heart could get tired of being brave. Daniel did not know what to say. Rachel, sitting nearby, said bravery was not something a heart had to do every minute and that resting was part of being strong. Sophie seemed satisfied. Daniel went into the kitchen and stood at the sink because the answer had almost broken him.
Two days before the demonstration, the load test failed again. Priya wrote a blunt report, attached the raw metrics, and requested a go-or-no-go review. Blake told Charlotte that a team member was exaggerating normal performance variation and that the product remained on schedule. Charlotte demanded a resolution rather than an explanation. Blake promised a patch by morning, then ordered the team to disable an expensive full-scale overnight test because the equipment would be needed for the presentation. Priya objected. He told her to leave the meeting. Charlotte later remembered seeing her exit with red eyes and assuming she had been unable to tolerate pressure. She would spend months reconsidering that assumption.
Daniel encountered Blake near the elevators while cleaning the conference area. Blake was arguing on the phone that the system would pass and that any remaining issue was a matter of temporary capacity. Daniel looked at the papers tucked under Blake's arm and saw a chart showing memory consumption rising more steeply with each new worker. He could not remain silent. "Your correlator isn't freeing work between batches," he said. "More capacity may make the collapse faster." Blake stopped talking and stared at him. For a heartbeat Daniel thought recognition had finally arrived. Then Blake smiled and asked whether the custodial department had started distributing architecture advice with the soap.
Two people nearby laughed. Daniel felt the familiar heat of humiliation, but this time it was accompanied by a deeper fear that someone could be harmed because the people in charge refused to look. He said he was not trying to embarrass anyone. Blake told him he had no authorization to discuss the system, then reported the exchange as a security concern. Daniel was called into Evelyn Ortiz's office and reminded not to interfere with proprietary work. Evelyn, who had never known his professional background, looked more puzzled than angry. She asked whether he had been trying to help. Daniel told her yes. She said she believed him, but that good intentions did not override the building's access rules. He agreed, even while resentment made his voice stiff.
That night Daniel wrote a note to himself in the old engineering journal he kept in his kitchen drawer. It contained no private Helix material, only a description of the failure mode he had inferred from visible information: uncontrolled event accumulation, recursive processing, worker multiplication, and lack of backpressure. Beside it