Victor Hales taught structural assessment methodology on Monday mornings in a room on the second floor of the engineering annex — a room with the slightly impersonal quality of a space used for multiple purposes, whiteboards on three walls, the kind of chairs that were designed for functionality and had achieved it at the cost of everything else.

Noel described the room to Mira later with the precision of someone who cataloged spaces automatically, and she listened and filed the description alongside what she already knew about Victor Hales — not from this timeline, but from the one she'd lived, where his name had appeared in the official inquiry and been cleared with the same brisk efficiency that had cleared everything else, and she had been twenty-six and grieving and had not known what to do with the clearance.

She knew more now.

She knew, for instance, that Hales taught his methodology seminar with the particular confidence of someone who had spent a long time not being questioned. He was thorough, Noel said. He knew the material. He presented infrastructure safety as a solved problem — a field with clear methods and clear standards and clear accountability structures that worked when properly followed.

"He's convincing," Noel said. They were in the library, their usual table, Tuesday afternoon. "If I didn't know what I know, I'd find him entirely credible."

"That's the point," Mira said. "The most effective version of this kind of thing is always credible. It's not incompetence — it's the same competence being used in two directions at once."

He looked at her. "Two directions."

"Teaching the right way to do things. While having, in another context, done them the wrong way and signed off on it." She paused. "The skill set is the same. That's what makes it hard to prove from the outside. You can't point to ignorance."

Noel was quiet for a moment, processing this. "The folder was empty," he said. "I checked on Monday. The file was there — the label, the index entry — but all the documents inside had been removed. The modification date on the empty folder was three weeks ago."

Three weeks ago. The week after they'd filed the records request.

"So he knows," she said.

"Someone does. Whether it's Hales directly or someone acting on his behalf." He looked at his notebook. "The timing is too clean for coincidence. We file the request, three weeks later the faculty archive folder is cleaned. That's a response."

She thought about the impossible photograph from the darkroom — the corridor of the design hall, night, the light under the office door. Someone working late. Managing something.

"What was in the folder originally?" she said. "Is there an index anywhere?"

"The library archive keeps an accession log," he said. "It lists what was submitted for archival storage, not what's currently in storage. The log is maintained separately from the actual files — it's an audit trail." He paused. "I requested it this morning through the library system. Legitimate research request. It'll take a few days."

She looked at him. He had, she noted, already anticipated the next move before they'd had this conversation. He had been thinking about this on his own, at eleven-thirty on a Saturday night and eight on a Sunday morning, and had already taken the next step.

"The accession log will show what was originally submitted," she said.

"Yes. Not the content — but the titles, dates, and submitting parties. If TR-7 was ever archived in that folder, the log will show it was there even if the document itself has been removed."

The absence as evidence. The same principle as before, one layer deeper.

"Good," she said.

"I thought you'd say that," he said, and there was something slightly wry in it — not the crooked smile but the suggestion of it, the quality of someone who was beginning to know how someone else thought.

She chose to ignore the quality of it and focus on the information. "What's your read on Hales? As a person."

Noel considered this. "He's careful," he said. "Very careful. The kind of careful that comes from having something to protect rather than from natural precision." A pause. "There's a thing people do when they're managing a narrative — they over-explain the parts that are fine and don't discuss the parts that aren't. Hales does that. The methodology he teaches is very thorough about the process for identifying and documenting safety issues. He's less thorough about the process for what happens when a safety issue is identified and then not acted upon."

"The gap in the methodology," she said.

"The gap he leaves in the methodology. Deliberately or because he can't afford to teach the full version." He looked at the table. "I don't know which. Both are possible."

She thought about the woman in the photograph on Thorne's windowsill. About eleven years of stopped time. About the specific kind of careful that came from having something to protect.

"Does he seem like someone who would clean a folder himself?" she said. "Or someone who would have someone else do it?"

Noel was quiet for a moment. "Someone else," he said. "He's the kind of person who maintains distance from the direct action. Signs papers but doesn't break ground. Authorizes but doesn't implement." He paused. "Which means there's someone else involved. Someone closer to the implementation."

Someone closer to the implementation. Someone who had been in the design hall corridor at night, three weeks ago, with a light on under the door.

She wrote in her notebook: *Who cleans the folder? Find the implementer.*

Across the library, a group of students erupted in laughter at something on one of their laptops — the ordinary social life of the library continuing around them as it always did, indifferent to the specific gravity of their corner of the room.

"The accession log," she said. "When it comes through, bring it straight to Thorne."

"Thursday," he said.

"Thursday," she confirmed.

---

That evening she went to the darkroom.

She had three rolls to develop — project work, mostly, the last location visit's documentation, some architecture details she'd been gathering. She worked through them methodically, each step given its full time, the chemicals doing what they did, the images coming up in sequence as they always did.

The project work was fine. Clean images, technically correct, the kind of photographs that said what they were supposed to say about the spaces they documented. She pinned them to the line and moved on to the second roll.

The second roll was also fine. Third roll.

The third roll's eighth frame was not what she had shot.

She held it up to the light.

The design hall corridor — the same image as before, or nearly the same. Night. The light under the door. But this time the door was not closed — it was slightly ajar, and through the gap there was a figure, seen in silhouette, at a filing cabinet.

She stood in the red light for a long time.

The figure was not recognizable — backlit, partially obscured, the quality of a silhouette rather than a portrait. But the posture had the specific quality of someone working with focused attention on something that required care. Opening a drawer. Removing something. Replacing it or not.

The implementer, she thought. Memory Echo showing her the implementer.

She made two prints. She filed them in the bridge folder and noted the date and the roll number and the fact that this was the fourth impossible photograph, and the content was consistent with the previous one — same location, same time of day, escalating specificity.

She added to her investigation notes: *Frame 8, roll 7. Design hall corridor, night. Figure at filing cabinet. Same location as frame from roll 4. Echo showing the process, not just the person.*

She looked at the two prints side by side — the closed door, then the open door, the figure.

Two frames. Different nights, or the same night. The space documenting what it had held, showing her what she needed to see.

She thought about what Thorne had said: *the Echo offers up evidence.*

She thought about the cost he'd mentioned, the thing it asked in return. The fifth impossible photograph had shown her own image. If the escalation continued — if the Echo was showing her the implementer with increasing clarity — what would it show her next?

She filed the photographs. She turned off the darkroom light.

In the folder on three laptops, she added a note: *Two new impossible photographs. Design hall corridor, figure at filing cabinet. Will bring prints Thursday. The Echo is escalating — showing process, not just location. Discuss with Thorne.*

Then, below that, for Noel specifically: *Be careful in the Hales seminar. If he's managing the evidence, he's aware enough to notice people paying attention.*

His reply came before she'd left the building: *Understood. I've been careful. You'd be surprised how unremarkable it is to take notes in a methodology seminar.*

She was standing in the corridor outside the darkroom when she read it, and she laughed — quietly, to herself, in the empty hallway — and it was the first time she'd laughed since she'd arrived in this timeline that wasn't the careful social version. It was the real one, the one that came from being surprised by something someone said.

She put her phone in her pocket and walked home through the November campus, and the laughter was a small warm thing she carried for the length of the walk, and she let herself have it.

Small things. She was learning to let herself have the small things.

The investigation was real and the danger was real and the cost of what she was doing was real. But so were the small things. Both were true. They had to be, or the rest of it wasn't worth it.

She walked home through the cold, and the tram ran its route, and somewhere in the design hall the corridor held what it held, waiting for her camera to find it again.

Thursday came with rain — proper November rain, the kind that came off the lake and settled in for the day rather than passing through. The campus was darker than usual and everyone was moving slightly faster than usual, collars up, the particular kinetic quality of a cold wet day.

Thorne's office held the three of them with the familiar configuration: Mira and Noel on the chairs, Thorne behind the desk, the map on the wall with its notations.

Noel brought the accession log request — still pending, expected by end of week. He also brought what he'd found in the Hales seminar: a passing reference in a lecture slide to "the TR-7 protocol for post-installation assessment," which appeared as a bullet point in a list of methodology documents and which had a footnote indicating it was available in the faculty reference archive.

The same archive where the folder had been cleaned three weeks ago.

"He referenced it in class," Noel said. "Casually, as one item in a list. Not drawing attention to it."

"Because to draw attention to it would be to draw attention to the fact that it should be accessible but isn't," Thorne said. "He's maintaining the public appearance of transparency. The protocol exists, it's referenced, it's theoretically available. The fact that the copies have been removed is something you'd only discover if you went looking."

"Which we did," Mira said.

"Which you did." Thorne looked at the impossible photographs she'd brought — the four prints, laid out in sequence. The bridge, the corridor, the figure at the cabinet. "The Echo is showing you the mechanism," he said. "Not just the outcome."

"The implementer," she said. "I've been thinking about that. Noel said Hales is the kind of person who maintains distance from the direct action. There's someone else — someone who actually does the archive work, the access panel work."

"The maintenance contractor," Noel said. "Meridian. I cross-referenced the contract dates with the TR-7 creation date — the Meridian contract was signed fourteen days after the TR-7 creation date. That's consistent with the document driving the scope of work rather than the work driving the document." He opened his laptop and turned it toward Thorne. "TR-7 existed first. Then the contract was structured around what TR-7 found. Which means Meridian received a copy of TR-7 as the document of record for the work they were hired to do."

Thorne looked at the screen for a long time. "You verified this through the public procurement records."

"Everything I used is public record. The dates are in the procurement database." A pause. "The inference — that Meridian received TR-7 — is inference. But it's the standard practice for this type of contract. You don't hire a contractor to fix a problem without giving them the document that defines the problem."

Thorne leaned back in his chair. Outside the window the rain was steady against the glass, the campus moving through its wet day below.

"Meridian," he said.

"They're still active. Current city contracts, regular maintenance work." Noel looked at Mira. "The question is how to approach them. A records request won't work — they're a private company, no legal disclosure obligation. It has to be a direct approach."

"Risky," Thorne said. "If they're aligned with the city on this, a direct approach tells Hales we're looking at the contractor."

"If they're not aligned, a direct approach gets us TR-7," Mira said.

Silence for a moment. The rain on the window.

"There's a way to read which side they're on before approaching," Noel said. He had the quality of someone who had been thinking about this since before the meeting. "Their public facing work — recent bids, project documentation, public statements. If they've been doing ongoing maintenance on the bridge since the original work, they have an ongoing relationship with the city that makes alignment likely. If they haven't — if the bridge work was a one-time contract and they haven't been back — then they may have less invested in the cover."

"How long would that take to determine?" Mira asked.

"Adrian can pull the procurement data. A day, maybe two."

She looked at Thorne.

"One week," Thorne said. "We give this one week before considering a direct approach. I want the accession log back first, and I want to understand the full picture before we make a move that can't be undone."

Noel nodded.

"One week," Mira said.

---

Walking out of the theory building into the rain, she and Noel stopped on the sheltered porch to look at the weather. The campus path was wet and shining and largely empty, everyone having taken the indoor routes.

"You laughed last night," he said.

She looked at him.

"Your message," he said. "There was a laugh in it. The punctuation, something. I could tell."

She thought about standing in the corridor outside the darkroom, reading his message about the methodology seminar, the small real laugh that had surprised her.

"You were funny," she said.

"I'm occasionally funny," he said. Not boastful — matter-of-fact, the way he was matter-of-fact about everything.

"Yes," she said.

He looked at the rain. She looked at the rain. The porch was small enough that standing on it together required the kind of spatial awareness they'd been developing for weeks — the particular calibration of two people who had gotten used to proximity.

"The accession log comes Friday," he said.

"And Adrian starts the procurement pull today."

"Yes." A pause. "We're moving faster than I expected, this week."

"Faster than expected is sometimes good," she said. "And sometimes it means you've been noticed and things are moving to counter you."

He was quiet for a moment. "I know," he said.

She looked at his profile in the grey light — the particular quality of concentration he had when he was working through something he didn't want to say carelessly.

"Are you scared?" she said. It came out more directly than she'd planned.

He considered the question seriously, which was the thing she'd always valued about him — he didn't deflect honest questions with reflexive answers.

"Not of the investigation," he said. "The investigation I can think about clearly." He paused. "I'm more concerned about what happens if we find what we're looking for and can't make it stick. If the evidence is there and the system closes around it anyway."

She knew that feeling. She had lived that feeling, for three years, in a different timeline.

"It won't close around this," she said.

He looked at her. Something in her tone had been too certain — more certain than a first-year student who'd been investigating a bridge for six weeks had any right to be.

"How do you know?" he said.

She held his gaze. "Because we're doing it right," she said. "Because there are three of us and we're building a record that exists outside any single archive. Because the contractor has copies and the accession log exists and the coverage model analysis is already in three places." She paused. "Because we're not going to make any move that creates a single point of failure."

He held her gaze for a moment longer. She could feel him deciding whether to ask what she hadn't said — the part of the certainty that didn't come from the investigation logic.

He decided not to ask.

"Okay," he said. "I trust that."

She exhaled.

The rain kept going. Across the campus the tram hissed past on its elevated track, wet and reliable, doing what it always did.

"You should go," she said. "You'll get soaked."

"So will you."

"I don't have a seminar at two."

"True." He stepped off the porch into the rain, pulled up his collar, looked back. "Friday. Accession log."

"Friday," she said.

She watched him walk away through the rain — quickly, collar up, the rolled drawing under his jacket against the wet — and she stood on the porch of the theory building and felt the specific weight of a Tuesday afternoon in November when something had shifted, slightly, in a direction she couldn't quite name but could feel clearly.

The rain came down.

She went inside.