Dylan Miller's relationship with sleep was, his sister Sophia had once observed, the relationship of a man who understood its theoretical importance and chose to engage with it on a consulting basis.
He had left the estate at eleven-fifteen the previous night, driven back to Brooklyn, and been in his office by midnight. Not because anything specific required him to be — the company didn't collapse when its CEO went home, a point his COO made with regularity — but because the trace he'd been running on Miller Global's data systems had reached a stage that required his personal attention, and he was constitutionally incapable of leaving something at a stage that required his personal attention.
He had slept from four to six-thirty on the couch in his office. This was not ideal. It was also not unusual.
By seven, he was at his standing desk with coffee and three active monitors, looking at the results of the night's work with the specific expression he wore when data told him something he had suspected but hadn't wanted to confirm.
Nexus Technologies occupied a converted warehouse on the edge of DUMBO — two city blocks of reimagined industrial space that Dylan had acquired six years ago when Nexus was still a promising startup and the building was still trying to remember what it was supposed to be. He had gutted it and rebuilt it as he'd wanted: open collaborative spaces on the ground floor, development labs on the second, executive functions on the third, and his own workspace in a glass-walled room at the building's northeast corner that gave him sightlines to the entire third floor and, through the large windows, to the Manhattan Bridge and a slice of the East River.
He had not chosen the space for the view. He had chosen it because it had two exits and excellent sight lines. His siblings, if asked, would have said this was paranoid. Marc would have said it was sensible. Dylan would have said it was architectural preference and changed the subject.
Maggie Chen arrived at seven-thirty, which was early for everyone except Dylan and therefore early enough for the purposes of the people who set Nexus's cultural norms. She was twenty-six, Chinese-American, possessed of a mind that could hold competing complex systems in active parallel without losing thread on any of them, and was the only person at Nexus who consistently told Dylan when he was wrong without first constructing an extensive buffer of diplomatic qualification.
She knocked on his glass wall — a courtesy, since he could clearly see her — and came in with her own coffee. She looked at his screens. Then at him. Then back at the screens.
"You've been here all night," she said.
"I went home."
"When?"
"I was at my family's place Sunday evening."
"That's not the same as going home."
"Technically — "
"Dylan." She sat in the second chair — the one she had claimed as hers through the accumulated weight of seven years of occupying it. "What are you looking at?"
He turned one of the monitors toward her.
The display showed a data flow visualization — Miller Global's network traffic rendered as a moving map of information currents. To most people it would have looked like an abstract animation. To Maggie, who had built three of the visualization tools Dylan was using, it told a specific story.
She leaned forward. Her expression shifted into the focused quality it took on when she was reading something that mattered.
"This is Miller Global's system," she said.
"Yes."
"Someone's siphoning."
"Yes."
"How long?"
"Based on the traffic pattern, at least eight months. Possibly longer — the earlier activity would have been smaller, more intermittent. Harder to distinguish from normal background noise. It's been scaling up over the past ninety days."
Maggie studied the visualization. "What are they pulling?"
"Financial architecture. Specifically the structural mapping of how funds move between Miller Global's divisions — the relationships between accounts, the transfer protocols, the timing patterns. Not the money itself. The map of how the money moves."
Maggie looked at him. "Why would you want the map instead of the money?"
"Because if you want to steal the money, you need the map first. But more importantly — " Dylan zoomed in on a specific cluster in the visualization "— if you want to manufacture evidence of financial crimes that didn't happen, you need to understand the system in enough detail to make the fabrication credible."
A silence. Maggie absorbed this.
"Someone's building a frame," she said.
"Someone's been building one for at least eight months," Dylan said. "Possibly longer."
He had started running the security analysis on Miller Global's systems as a favor to his father — a routine check, something he offered to do quarterly, the kind of thing a tech CEO son could do for a businessman father that made the son feel useful and the father feel modernly secured. He hadn't expected to find anything. Miller Global's IT department was competent, their security protocols solid. He'd built the framework himself three years ago.
He had found the anomaly in the third hour of analysis.
It was small — the kind of small that was designed to be small, the signature of someone who understood that conspicuousness was the enemy of sustained access. A deviation in the data traffic pattern so minor that Miller Global's own security systems had registered it as background noise and moved on. But Dylan's ORACLE, which operated at a different level of granularity than standard security monitoring, had flagged it.
He had spent the subsequent week watching it rather than closing it — the decision his father had arrived at independently last night, which Dylan had already implemented five days earlier. Let it run. Learn what it's doing. Find where it goes.
"Have you traced the destination?" Maggie asked.
"Partially. The routing is layered — five proxy hops before the data leaves Miller Global's network. I've cleared three of them. The fourth is a commercial anonymization service with a legitimate business front. I'm working around it."
"The fifth?"
"Unknown yet. But the signature of the routing architecture — " he pulled up a second screen "— matches a pattern I've seen before."
He opened a government cybersecurity brief he'd contributed to eight months ago — a classified document he had access to through Nexus's federal contractor status. He highlighted a section.
Maggie read it. Her coffee cup went down.
"This is a criminal network infrastructure pattern," she said.
"Yes."
"The brief says it's associated with Phantom Syndicate-affiliated operations."
"Yes."
"Dylan."
"I know."
"This isn't corporate espionage. This is organized crime."
"I know."
She looked at him for a moment with the particular expression she used when she was assessing whether he was handling something or performing handling it. She had this calibration finely tuned after seven years. "What are you going to do?"
"I'm going to keep watching. I'm going to clear the fourth proxy hop. And I'm going to identify the source inside Miller Global."
"Inside — there's an insider?"
"The access points are too specific for a remote breach. Someone with internal access has been facilitating. Narrowing the access list to people with both the permissions and the technical understanding to set this up gives me eleven candidates."
"Who's at the top of the list?"
Dylan was quiet for a moment. "Thomas Blake."
Maggie absorbed this. Thomas Blake — CFO of Miller Global, trusted by Edward Miller, present at every significant financial meeting the company held. "Your father trusts him."
"My father trusts a lot of people," Dylan said. "It's one of his best qualities and one of his most dangerous ones."
The rest of the morning operated around Dylan's investigation the way Nexus always operated around whatever Dylan was most focused on — the company's daily business continued, meetings were held, decisions were made, and Maggie provided the human interface between Dylan's operating world and the institutional requirements of running a company with four hundred employees.
Dylan appeared at the ten o'clock all-hands briefing for eleven minutes, made three points that redirected two projects and accelerated one, and then returned to his office, where he spent the next four hours in the company of ORACLE and the Miller Global data.
ORACLE — his private name for the system, used nowhere in official documentation — was the most sophisticated piece of software he had ever built. It had started as a cybersecurity project, a monitoring system designed to detect and analyze threats to Nexus's own infrastructure. It had evolved, over two years, into something considerably more powerful: an AI-driven surveillance and analysis architecture capable of monitoring communications across multiple platforms, identifying patterns in large data sets, and cross-referencing disparate information streams to produce intelligence assessments that no human analyst working with conventional tools could match.
He had built it because he could. He had refined it because the threat landscape required it. He deployed it carefully and with the specific consciousness of someone who understood what kind of power he was holding and what that implied.
"ORACLE," he said, to the interface — a voice command layer he'd added for operational efficiency during complex multi-screen work sessions — "expand the proxy trace on the Miller Global siphon. Secondary analysis: cross-reference the access timing with Thomas Blake's documented location records for the past eight months."
The system processed. Dylan watched the screens.
The results came back in forty seconds.
Forty seconds was, for ORACLE, a long time. The correlation was complex.
Dylan looked at the results for a full minute without moving. Then he picked up his phone and called Marc.
"It's midnight," Marc said, when he answered.
"It's ten-fifteen in the morning."
A pause. "I thought you were calling about the Dante Reyes thing."
"I'm calling about something else. Something I found in Miller Global's systems."
He heard Marc's breathing shift slightly — the adjustment of attention. "Talk."
Dylan walked him through it: the data siphon, the eight months of activity, the financial architecture targeting, the criminal network signature, the insider evidence, Blake's probable involvement.
Marc was quiet through all of it. This was one of the things Dylan valued about his youngest brother — Marc's silence during an intelligence briefing was not absence but active processing. He was filing, connecting, building.
When Dylan finished, Marc said: "Don't tell Dad yet."
"I know."
"Not until we know who else. Blake might be one layer. We need the whole picture before we show anyone anything."
"I know," Dylan said again. "That's why I'm telling you."
"What do you need from me?"
"Nothing yet. Keep your eyes open at the street level. If this is organized crime involvement, the physical operation exists somewhere. Buildings, people, routines. You're better at finding that than I am."
"I'll look."
"Marc." Dylan paused. "This is sophisticated. The people who built this have been planning for a long time and they're good at what they do. Be careful."
A beat. Then, in the tone Marc used when he was being genuine rather than performing: "Yeah. You too, Dyl."
The call ended. Dylan turned back to his screens.
ORACLE was already running its next analysis — following the fourth proxy hop, working around the anonymization layer with the patient persistence of a system that didn't get tired and didn't get bored and didn't stop.
Dylan, who also didn't stop, worked beside it.
At four in the afternoon, Maggie knocked on his glass wall again. She was holding a printed page — she printed things when they were important, a habit from an earlier era of work that she had never abandoned.
"You need to see this," she said.
She put the page on his desk. He read it.
It was an ORACLE flag — a cross-reference result from the secondary analysis he'd set running that morning. The IP signature of the Miller Global data siphon's routing architecture matched, at ninety-three percent confidence, the signature of a known state actor-affiliated criminal network that ORACLE had fingerprinted from the government cybersecurity briefs.
But that wasn't what Maggie had printed it for.
The cross-reference had also flagged something else: the same IP signature appeared in the communications of a company called Hargrove Consulting LLC — a small advisory firm registered in Delaware with no significant public profile.
Dylan looked at the company name. Something moved in the back of his mind — a connection not yet fully formed.
"Hargrove," he said.
"I ran the registration," Maggie said. "The company was incorporated eight years ago. The registered agent is a firm in Wilmington. But the beneficial owner — " she pointed to a line on the page "— is listed as Richard Hargrove."
Dylan was still.
"Dylan," Maggie said carefully. "Is that name familiar to you?"
He looked at the name. He thought about his mother — about Eleanor Miller, née Hargrove, who had a brother she spoke of with the particular warmth and sadness of someone who loves a person they have lost to time and distance.
"I need to make a call," he said.
Maggie took the printed page and left.
Dylan sat in his glass-walled office with the East River visible in the distance and ORACLE running on his screens, and he thought about what it meant to find your family's name at the center of a criminal network that had been systematically dismantling everything your family had built.
He thought about it for three minutes.
Then he picked up his phone. He called Marc again.
"I found something else," he said. "And it's worse."