Wren met him at 0700.
Not at the facility — that would have been the wrong kind of visible. She'd named a location in her reply: a coffee shop three blocks from the Grid 2-A district border, the kind of place that opened early for the morning commuter traffic and had enough ambient noise to make conversation private without requiring anyone to whisper. He'd gotten there first, taken a corner table with sight lines on both entrances, and ordered something he wasn't going to drink.
She came in at 0701, in civilian clothes, and sat across from him with the economy of motion he'd catalogued from the second-floor ledge of Tanaka's restaurant. She looked at his untouched coffee and then at him.
"You said 72 hours," she said.
"70 now," he said. "I'll be direct."
"Please."
He told her what he knew. Not everything — he gave her the operational picture without the system's architecture behind it, the way you gave a capable person the information they needed to act without the information they didn't need to carry. The organization. The consolidation meeting. Three simultaneous sites as misdirection. The unified intelligence package being assembled on kaiju-adjacent phenomena.
She listened without interrupting, which he'd expected. When he finished she was quiet for a moment in the way of someone running parallel tracks simultaneously — processing what he'd said and assessing what he hadn't.
"Three sites," she said. "You need coverage on all three simultaneously."
"Yes."
"You can cover one."
"Yes."
"And you need people for the other two who can operate without full context." She looked at him steadily. "Because giving them full context creates exposure."
"Yes."
She looked at her own coffee — she'd ordered one when she sat down, was actually drinking it, the small behavioral difference between someone at ease and someone performing ease. She was at ease. He filed that.
"I can cover one site," she said. "Independently, no Defense Force channel involvement, clean deniability." A pause. "The third site is your problem."
"I know."
"Amano," she said.
He looked at her.
"You've talked to her," Wren said. It wasn't a question. "The dossier. You went for it and came back with something other than destruction." She read his expression — or the absence of it. "She's analytical, she's independent, she has organizational resources and she's already invested in documenting what you are." A pause. "She's also the reason the organization got close enough to run the Grid 5-C operation in the first place, which means she has motivation to make that right."
He'd arrived at the same conclusion at 0200 the previous night. Hearing it from Wren made it cleaner — the external confirmation of internal logic.
"She's not field capable," he said.
"She doesn't need to be field capable," Wren said. "Site coverage for a misdirection location is observation, not intervention. She watches, she reports, she stays invisible. That's her natural operating mode."
He thought about a silver-haired analyst in a storage unit surrounded by evidence, moving through the world with the practiced invisibility of someone who had been doing careful work in unacknowledged spaces for years.
"I'll contact her," he said.
Wren nodded. "Timeline for site identification?"
"The system will narrow it as the meeting approaches. I'll have locations within 36 hours."
She accepted that without asking what the system was — the same way she'd accepted his codename on the district border outside Grid 2-A, filed and not pushed. He appreciated that about her.
"One condition," she said.
"Name it."
"After this is resolved I want a full debrief on the organization. Not operational details — the architecture. Who they are, what they want, how they're structured." She held his gaze. "I'm Defense Force adjacent. If there's an organized non-state entity with significant resources targeting kaiju-adjacent phenomena I need to understand the scope of that."
"Agreed," he said.
She stood up. "I'll be ready when you have the locations." She picked up her coffee. "No. 0."
"Wren."
She left.
He sat for a moment in the coffee shop's morning noise and thought about the shape of what he was building — not a network exactly, nothing so formal. More like a constellation of capable people who had each decided, for their own reasons, that the work mattered. Miyako from day one. Sera from a quiet conversation in an equipment room. Amano from a question mark and two words written on the back of it. Wren from a second-floor ledge and a one-eared rabbit and the specific quality of the decisions that had led him there.
He pulled out his phone and sent a message to Amano.
*I need your help. Same arrangement, different application. Can we talk today?*
Her reply came in four minutes.
*Storage facility, Grid 8-B, 1200. I'll have lunch.*
He almost smiled.
---
The morning rotation kept him at the facility until 1130.
Perimeter support again — the second day of the support role assignment, Kuro running it with the systematic efficiency of someone building a baseline before he changed anything. Miyako worked the route beside him with the same low continuous observation she'd brought to yesterday's circuit, and he gave her the shape of the Tier 4 mission in the same register — barely above normal conversation, the words absorbed by the ambient sound of a patrol route.
She was quiet for a full circuit before she responded.
"Three sites," she said. "Wren on one, Amano on one, you on one."
"Yes."
"That leaves the facility coverage for whenever this runs."
"I know."
"Which means Sera and I are managing the internal layer while you're managing the external one." She checked a boundary marker. "This is more complex than anything we've run before."
"Yes."
"Are you telling me because you want my assessment or because you've already decided and you're informing me?"
He thought about that honestly. "Both."
She looked at him sideways. The not-quite smile. "At least you're consistent." She logged the marker. "The facility timing is the hardest variable. If the meeting runs long —"
"I'll be back before it matters."
"You said that about Grid 8-B and made it with four minutes to spare."
"This time I'll have more margin."
"You don't know that."
"No," he said. "I don't."
She accepted that with the equanimity of someone who had decided uncertainty was a working condition rather than a problem. "I'll coordinate with Sera. She needs to know enough to cover effectively." A pause. "How much do I tell her?"
"Enough," he said. "Not everything."
"That's what I've been doing." She finished the route's final marker. "Shiro."
He looked at her.
"This is the one where it gets complicated," she said. "Not the missions — those have always been complicated. The people." She met his gaze. "Wren is Defense Force adjacent. Amano has organizational connections. Every person you bring into this carries their own affiliations and their own version of what they think you are." She paused. "Make sure you know what each of them is actually working toward."
He thought about that. About Wren wanting a structural debrief on the organization — not operational details, architecture. About Amano building a record rather than a targeting package. About the specific clarity of each person's stated motivation and the question of whether stated motivations were complete ones.
"I know," he said.
"Good." She turned toward the facility entrance. "You have forty minutes before your 1200 meeting. Don't be late."
"You knew about the 1200 meeting."
"You sent Amano a message at 0830. She's punctual and she has a fixed workspace." Miyako looked straight ahead. "1200 was the obvious reply."
He walked beside her and thought about what it meant to have someone who could infer his schedule from first principles, and whether that was a security concern or the most useful thing in his operational picture.
He decided it was both and kept walking.
---
Amano had brought actual lunch.
Two bento boxes, the kind from a proper shop rather than a convenience store, set out on the folding table beside her laptop in the Grid 8-B storage unit. She gestured at the second one when he came in and he sat and opened it because declining food from someone who'd brought it intentionally was a specific kind of rudeness he didn't have time for.
She waited until he'd eaten three bites before she spoke.
"The organization," she said. "The Grid 5-C group's parent structure."
"Yes."
"I've been pulling threads since our conversation." She turned her laptop to face him. "They have a name internally — ARGUS. Analytical Research Group for Unexplained Singularities." She paused. "The name is more formal than their structure. They're a distributed network — no central headquarters, cells operating in different cities with loose coordination at the top. The Grid 5-C group was a field cell, moderately resourced, operating on intelligence they obtained from my analytical work without authorization."
"How distributed?" he said.
"Seven confirmed cells across three major cities. Unknown number of associates. The coordination layer at the top is three to five individuals — I haven't identified them yet." She pulled up a diagram. "They're not anti-Defense Force exactly. They're adjacent to it — they think the Defense Force is managing kaiju phenomena with insufficient scientific rigor. They want to study it directly."
"Study it," he said.
"That's the stated mission. The methodology varies by cell." She looked at him steadily. "The Grid 5-C cell's methodology was acquisition. Others are purely observational. The coordination layer's approach is the unknown variable."
He looked at the diagram. Seven cells, three cities, a coordination layer he didn't have the shape of. Bigger than Grid 5-C had suggested. Not as big as the word network might imply — distributed but not massive, resourced but not institutional.
"The consolidation meeting," he said. "What's the purpose from their perspective?"
"Efficiency," she said. "They have data on three kaiju-adjacent phenomena from three separate cells. Consolidating it lets the coordination layer build a complete operational picture rather than fragmented cell-level views." She paused. "It also lets them decide on a unified approach. Right now each cell is operating independently. After consolidation they'll be coordinated."
"Which makes them significantly more dangerous," he said.
"Yes."
He thought about that. About the difference between seven cells doing their own thing and seven cells with a unified direction from a coordination layer that had decided what to do with a complete operational picture.
"The meeting location," he said. "Three simultaneous sites as misdirection. How do they choose which is real?"
"The coordination layer communicates the real location through a separate channel twenty minutes before the meeting time. Only confirmed attendees receive it." She pulled up another window. "Which means we can't know which site is real until twenty minutes before — unless we have access to the confirmation channel."
"Can you get access?"
She looked at him with the expression of someone who had been thinking about this since 0830. "I have a former colleague who does contract work for ARGUS's observational cells. He's not in the field operation — he's analytical support. He won't know the confirmation channel directly but he'll know the communication architecture."
"Will he talk to you?"
"He'll talk to me if I give him a reason that doesn't involve him understanding the full picture." She paused. "I'm good at giving people partial pictures that motivate correct behavior."
"I know," he said. "I've seen your wall."
She almost smiled. "I'll contact him today. If I can get the communication architecture I can potentially intercept the confirmation transmission." She looked at him. "That changes the three-site problem. Instead of covering all three simultaneously you wait for the confirmation and go directly to the real location."
He turned that over. It was cleaner — one site, full resources, no split coverage. But it depended on Amano's former colleague and the communication architecture and the interception working within a twenty-minute window.
"Keep the three-site coverage as backup," he said. "If the interception fails we revert."
"Agreed." She turned her laptop back and began typing. "I'll need 24 hours."
"You have 68."
She nodded and typed and he finished his lunch in the particular comfortable silence of a storage unit that had become, somewhat improbably, a functional operations center.
The system, which had been running background assessments throughout, offered:
*"Amano's approach is sound. The communication architecture intercept is higher probability than three-site coverage."*
*"But not guaranteed,"* he said.
*"Nothing is guaranteed,"* the system said. *"That's why you maintain the backup."*
He looked at Amano's wall. The question mark was gone — she'd taken it down after their last meeting and hadn't replaced it. The rest of the evidence remained, the timeline and the sensor logs and the photographs, but the center of the wall where the question mark had been was empty now.
She'd put something else there. Small, printed, slightly off-center.
*No. 0.*
Not as a label. More like an anchor — the point around which the rest of the evidence organized itself now that it had a name.
He looked at it for a moment.
"The two other cases they're investigating," he said. "What do you know about them?"
She pulled up another file. "One is a Defense Force soldier in the western grid cluster. The ARGUS cell there has observed anomalous combat performance over several field engagements — speed and strength beyond standard parameters, inconsistent sensor readings during transformation events." She paused. "The cell believes it's a kaiju-host situation similar to documented cases but with unusual characteristics."
"And the third case?"
She looked at him. "You already know about the third case."
He held her gaze.
"The ARGUS data on the third case is more extensive than on either of the others," she said carefully. "They've been building a profile for longer. The cell involved is better resourced." She turned the laptop to face him again. "The name in their file is Kafka Hibino."
He looked at the file. The accumulated intelligence on a man he'd never met, assembled by an organization that didn't have his best interests in mind, connecting him to phenomena that the Defense Force was simultaneously trying to understand and contain.
Kafka Hibino. Third Division cleanup worker, failed applicant, the same trajectory as Riku's own except louder and more visible and further along the timeline of someone who had become something the world hadn't prepared for.
"How close are they to a complete profile?" he said.
"Close." Amano's voice was measured. "The consolidation meeting is primarily about him. The coordination layer wants to decide what to do with the Kafka Hibino case. The other two cases — yours and the western soldier — are secondary consolidation items."
He looked at the file for a long moment.
"He doesn't know," he said.
"No," she said. "He doesn't."
He thought about the system's answer when he'd asked whether he should tell Kafka. *That is your decision, No. 0. Not mine.*
He thought about what it meant to carry something alone. About eight months of cleaning up rubble and building an architecture of acceptance around something that wasn't actually acceptable. About the third attempt and what it felt like to walk into an examination room knowing you'd already failed twice.
Kafka Hibino had carried more of this for longer. And somewhere in the city, an organization with seven cells and a coordination layer was twenty-four hours from deciding what to do about him.
"I need his location," Riku said.
Amano looked at him. "That's not in any file I have access to."
"His work assignment," he said. "Cleanup Corp, Grid sector. The public assignment records."
She pulled up a different window. Typed quickly. The results populated and she turned the laptop toward him.
Grid 3-C cleanup rotation. Morning shift, 0700-1500. Currently assigned to post-incursion debris clearance in the eastern residential sector.
He looked at the schedule. Then he looked at his own rotation — Fourth Squad, perimeter support, 0900-1700.
A two-hour window in the morning before his shift started.
*"You're going to talk to him,"* the system said.
*"Yes,"* he said.
*"Before the consolidation meeting."*
*"Yes."*
*"He won't know who you are,"* the system said. *"You'll be a stranger telling him something that will change the way he understands his situation."*
*"I know."*
*"He may not believe you."*
*"I know that too."*
The system was quiet for a moment.
*"Do you know what you're going to say?"*
He looked at Kafka Hibino's work assignment on Amano's screen. At the grid sector and the shift time and the mundane administrative record of a man who had no idea that tomorrow morning a stranger was going to find him in a post-incursion debris field and tell him something that would make the last several months of his life look different.
*"Not yet,"* he said.
*"You have 24 hours to figure it out,"* the system said.
He stood up. Closed the bento box. Looked at Amano.
"24 hours," he said. "Communication architecture."
"24 hours," she confirmed, already typing.
He walked to the door. Stopped.
"Amano-san."
She looked up.
"The wall," he said. "Keep documenting."
She looked at him for a moment. Then she turned back to her laptop.
"I intend to," she said.
---
He was back at the facility by 1340.
Kuro ran the afternoon debrief at 1400. Renmei updated the week's rotation at 1500. Yashiro watched him through both with the same field-sharpened curiosity she'd been bringing since Monday, and he watched her back with Predator's Eye and filed what he saw — not hostility, not suspicion, the specific quality of someone waiting for a data point that would resolve an open question.
At 1800 he found Miyako.
"Tomorrow morning," he said. "0700 to 0900. I need to be off-facility."
She looked at him. "You have squad PT at 0900."
"I know. I'll be back."
"That's a tight window."
"Yes."
She read his expression with the accuracy of someone who had been paying attention for six weeks. "This isn't a system mission," she said.
"Not officially."
"But it's important."
"Yes."
She was quiet for a moment. "Who are you going to see?"
He thought about how to answer that. About the specific weight of the name and what it would mean to Miyako — who had read everything, who had mapped Fourth Squad's dynamics in forty minutes, who would understand immediately what it meant that Riku was going to find this particular person before the consolidation meeting.
"Someone who's carrying more of this than either of us knew," he said.
She looked at him for a long moment. Then she nodded.
"0700 to 0900," she said. "I'll cover the morning check."
"Thank you."
She started to turn away. Stopped. "Shiro."
He waited.
"Be careful how you do it," she said quietly. "Finding out someone's been watching you without your knowledge — even someone trying to help — lands badly if it's not done right."
He thought about the night he'd found her at the coffee shop on day thirty-seven, the way she'd laid out everything she knew with the precision of someone who had decided the truth was more useful than the performance of not-knowing. The care she'd taken with the delivery even as the content was blunt.
"I know," he said.
"Good." She walked away.
He went to his bunk and lay there in the evening light and thought about what he was going to say to a man he'd never met who was carrying something alone that he didn't have to carry alone.
He thought about it for a long time.
By the time the facility went to its nighttime cycle he still didn't have the exact words.