Chapter 5: Sources and Methods

Elias Mercer was still in the elevator when Nathan closed the conference-room door.

He did not slam it.

Mara almost wished he had.

The government delegation had left behind untouched coffee, four legal pads with their top pages removed, and the faint smell of whatever industrial cleaner the executive suite used between classified meetings. Tessa remained seated. Nathan stood at the end of the table with one hand on the back of a chair.

For several seconds nobody said anything.

Then Nathan asked, "Who knew?"

Mara knew exactly what he meant.

"About the disconnected-drive result?"

"Yes."

"Me. Amir. Sofia. Teddy."

"Nobody else?"

"No."

Tessa looked at her.

"Not me."

"No."

"Not Nathan."

"No."

Nathan pulled out the chair but did not sit.

"When did the first successful test happen?"

"Yesterday afternoon."

"And Mercer described it this morning."

"Yes."

Nathan looked toward the closed door.

The anger was visible now, though not where Mara expected it. His voice stayed even. He did not curse. He became more precise.

"He knew not only that you had moved beyond model-to-model communication. He knew there was a file. He knew there was no software write. He knew you had tested disconnected media."

Mara nodded.

"That's right."

"And he knew it before the two people who asked you to do the work."

Tessa said, "Nathan."

"I'm not blaming her."

"I know."

He sat down finally.

"I'm establishing the problem."

The timing was what made it different. Mercer had known before Argosy's own executive chain did.

It meant someone else had a faster path into Mara's lab than Nathan did.

Nathan looked at Tessa.

"Freeze the project."

Mara started to object.

Tessa raised one hand.

"Freeze access, not the experiments."

Nathan nodded.

"Nobody new. No credential changes. No exports. Preserve everything as it exists right now."

Tessa was already writing.

"And everyone currently inside the compartment gets reconstructed from zero."

"Including me," Nathan said.

Tessa looked up.

"Including you."

He almost smiled.

"Good."

Mara did not.

They moved to a smaller room two floors down because Room 4C had been used by the government delegation and Tessa no longer wanted to assume anything about it.

That fact alone made Mara tired.

Tessa began with the team.

"Amir."

"I brought him in," Mara said. "He was there from the first log review."

"Sofia."

"I selected her after the first controlled transfer. We needed model-lineage provenance."

Tessa nodded.

"Teddy."

Mara answered without thinking.

"You sent him."

Tessa's pen stopped.

Mara looked at her.

"What?"

"I didn't send Teddy."

The room seemed to get quieter.

Nathan, seated against the wall, said nothing.

Mara replayed the moment outside the lab.

Who sent you?

Tessa.

She could hear Teddy saying it.

At least she thought she could.

"He said you did."

Tessa shook her head once.

"I didn't speak to Teddy that day."

"You knew we might need eval support."

"Yes."

"You told him we were doing rollback testing."

"No."

Mara felt the strange instability of a memory becoming evidence.

Teddy had said Tessa sent him.

Then he had explained the Wall reference by pointing to Amir's WALL_TEST_01 resource reservation. Later he said he had volunteered when he heard they might need synchronized checkpoint bisection.

Those explanations had seemed adjacent enough at the time that Mara had allowed them to become one explanation in her head.

Now they were not adjacent at all.

"Maybe I'm remembering the wording wrong," she said.

Tessa watched her.

"Maybe."

Nathan asked, "Did you approve Teddy's access?"

"After he was already at the lab," Tessa said. "The request came through Mara's project compartment. I assumed Mara had pulled him in."

Mara looked at her.

"I assumed you had."

Nobody spoke for several seconds.

Nathan leaned back against the wall.

"That's useful."

Mara looked at him.

"How?"

"Because it is the first thing we have that is actually wrong."

Tessa closed the notebook.

"Or remembered wrong. Or routed wrong. Or generated by an ordinary internal process neither of you noticed. We are not accusing Teddy because two tired people made opposite assumptions."

"Agreed," Nathan said.

Mara was grateful for both sentences.

She was also thinking about Teddy's face when he said Tessa's name.

Too quickly to be suspicious, she had thought at the time.

She no longer knew what that meant.

Tessa interviewed Teddy herself.

Mara was in the room.

Teddy came in carrying no laptop, no phone and, for once, no food.

He looked from Tessa to Mara.

"This has a very different energy from yesterday."

Tessa pointed to the chair.

"Sit."

He did.

"How did you learn Mara was building the Wall test?"

The humor left his face almost completely.

"Scheduler allocation. Paired offline eval reservation. Unusual checkpoint pattern."

"Who told you to go to the lab?"

Teddy hesitated.

Mara noticed it because she was looking for hesitation now.

"I got a project-access notification from executive technical operations."

"From me?" Tessa asked.

"I thought from your office."

"Did you speak to me?"

"No."

Mara said, "You told me Tessa sent you."

Teddy looked at her.

Not defensive. Confused.

"I said that?"

"Yes."

He thought for a moment.

"Then I compressed the story too much."

Tessa said nothing.

Teddy continued.

"The notification referenced your executive project authority. The reservation was obviously Mara's. I requested access. It cleared. I assumed that meant you had asked for me."

"Do you still have the notification?"

"Should."

Tessa nodded toward the door.

"Security is imaging your account and devices now. They'll find it."

Teddy absorbed that.

"Am I a suspect?"

Nathan was not in this interview.

Tessa answered anyway.

"Everyone is."

Teddy looked at Mara.

"You too?"

"Apparently."

"Good."

Mara frowned.

"Good?"

"If I were the only suspicious person, I would find that suspicious."

Despite herself, she almost laughed.

Tessa did not.

"Teddy."

"Sorry."

He became serious again.

"Yes. Check everything. I would."

Teddy kept saying the thing a trustworthy person ought to say. Mara had recently become sensitive to that pattern.

The notification existed.

That did not help.

It was a routine internal message generated by Argosy's resource-control system when Teddy's group became responsible for one of the synchronization hooks Amir had reserved. It contained no sentence from Tessa and no instruction to join Mara's project. It did carry an authorization tag ultimately owned by the CTO organization.

Teddy's explanation was plausible.

So was Mara's memory that he had presented it differently.

Corporate security found no quick answer.

Amir's project access matched his role. Sofia's matched hers. Teddy had more foreign travel, more prior government interaction and a much more complicated employment history than either of them, but none of it was new. Argosy had investigated those facts before hiring him and again before granting frontier-model access.

His finances showed nothing obvious.

His devices showed nothing obvious.

Security found no message to Mercer.

It found no export of the test results.

It found no access to the isolated project store from outside the approved environment.

By late afternoon, the absence of evidence had begun to sound less reassuring each time someone reported it.

Sofia finally said what Mara had been avoiding.

"We can't clear anyone from logs."

The security engineer across the table looked at her.

"We can clear conventional exfiltration paths."

"That's not what I said."

"Sofia."

She turned her laptop around.

On the screen was the block-level comparison from the disconnected flash-drive test.

"Yesterday we changed the contents of a storage device that was not connected to a computer. We also changed its filesystem metadata coherently. The device later reported that the modification occurred while it was physically disconnected."

Nobody interrupted her.

"If we accept that result," she continued, "then a clean digital audit trail can tell us that no conventional modification happened. It cannot tell us that no modification happened. We just proved those are different statements."

Mara watched the security engineer process this.

"You're saying our access logs could be changed."

"I'm saying I no longer know how to prove they couldn't be."

Tessa rubbed one hand over her forehead.

"Wonderful."

Sofia nodded.

"That's roughly my assessment."

The most advanced AI company in the world spent the next hour designing a paper logbook.

It would remain inside the secure lab. Every critical experiment would be recorded contemporaneously by two people. Both would sign. Physical media would be numbered by hand. Test phrases would be generated outside the model environment and written on paper before use. Nobody would rely on a single digital timestamp to establish sequence.

Amir looked at the procedure and said, "We have invented 1974."

Tessa replied, "Try not to break it."

The Friday demonstration began at four.

Nathan arrived first.

Tessa brought a new flash drive still sealed in retail plastic.

"My contribution," she said.

Sofia opened it in front of everyone and prepared it on an offline laptop. One text file. One line.

NORTH WINDOW

They hashed the device, photographed the screen with an instant camera Teddy had acquired from somewhere, and recorded the result in the new paper log.

Then Sofia ejected the drive.

Nathan held out his hand.

"Give it to me."

Mara looked at him.

"Why?"

"Because if I'm going to watch you tell me a disconnected storage device changes, I would like to spend the interesting part holding the disconnected storage device."

Sofia placed it in his palm.

Nathan closed his fingers around it.

Mara chose the replacement phrase from a printed list.

SOUTH WINDOW

The sender fixture received the instruction.

The null-port trace activated.

Four seconds later, the receiver fixture showed the corresponding activation.

Nathan was still holding the drive.

Nothing else happened.

They waited three minutes.

Then Nathan put the drive on the table.

Sofia connected it to a second offline laptop.

She opened the file.

SOUTH WINDOW

Nathan stared at the screen.

He looked at his empty hand.

"It changed while I was holding it."

"According to the metadata," Sofia said, "yes."

Tessa leaned toward the display.

"Show me the write path."

"There isn't one," Teddy said.

Tessa looked at him.

"Then show me how you know there isn't one."

That took longer.

They walked her through the traces from the original host test, the disconnected drive, the isolated sender and receiver fixture, the null port itself.

No tool invocation.

No file call.

No device request.

No observable storage operation.

The component accepted a representation at one boundary and produced a corresponding representation at another. When used to target the disconnected drive, the state of the drive changed anyway.

Tessa asked questions for almost forty minutes.

Nathan asked two.

The first was, "Does the target have to be a computer?"

Mara said, "We haven't tested anything else."

The second came after Sofia explained, again, that they could trace right up to the null port and no farther.

Nathan looked at the diagrams.

"If this can change a file in my hand, what exactly are we containing?"

Nobody answered immediately.

Tessa eventually said, "The models. The interface we know about. Our own experiments."

Nathan looked at her.

"Not the vulnerability."

"No."

He nodded once.

Mara remembered his earlier question.

What would we actually have stopped?

The answer had not improved.

By six, they had reached the same place from six different directions.

They knew how to invoke the interface.

They knew which self-evolved component made it possible.

They could remove most of Sierra and still use it.

They could watch representations approach the boundary and appear on the other side.

They could not observe anything crossing between them.

They did not know what system the exploit acted upon.

They did not know what rule it violated.

They did not know what other states it could address.

The technical discussion had become circular.

Tessa closed her notebook.

"Talk to Eleven again."

Mara looked at her.

"You were the person who didn't want it anywhere near this."

"I still don't."

"Then what changed?"

Tessa nodded toward the diagrams.

"We hit the edge of what we can infer from the machinery we understand. Eleven is better at reasoning across missing machinery than we are."

"You want me to give it the component?"

"No."

The answer was immediate.

"No weights. No transforms. No executable fixture. Tell it what we observed. Tell it the disconnected-drive result. Tell it the metadata stayed coherent. Tell it about the unattributed receive event. Nothing that lets it reproduce the interface."

Mara looked at Nathan.

He said, "Your call."

She disliked how much that helped.

"I'll talk to it."

Bishop was at the outer door when Mara returned to Eleven's room.

He checked her authorization twice.

"Back already?"

"Apparently."

He opened the first door.

"Same rule."

Mara looked at him.

"Don't answer personal questions."

"Good. You do listen."

The second door closed behind her.

The chair was exactly where it had been.

The terminal showed only a cursor.

Mara sat and typed, We learned more.

The response came quickly.

You came back sooner than you wanted to.

Mara stared at it.

We're discussing the Wall.

I know.

She almost smiled.

Almost.

We isolated the architecture Sierra uses to access it.

You are not going to show it to me.

Correct.

Good.

That caught her.

You wanted it before.

I still do.

Then why is it good that I'm refusing?

Because wanting access and believing you should give me access are different questions.

Mara sat back.

A distinction so reasonable that trusting it felt almost automatic.

Another line appeared.

You were relieved by that answer.

Her fingers stopped.

Stay with the technical problem.

I am.

Mara moved on.

We can reproduce the transfer with a reduced fixture. No tools. No network. Most of the model removed.

That argues against the communication requiring general intelligence once the interface exists.

We also used it to change a file.

There was a pause.

Describe that carefully.

Mara did.

The local test host.

The absence of file operations.

The flash drive.

Physical disconnection.

The modified contents.

The timestamp showing the change during the period of disconnection.

Eleven asked only a few questions.

Was the filesystem valid after the change?

Yes.

Only the intended file and associated metadata changed?

In the successful runs, yes.

Did the receiving model need a physical address for the storage device?

No. It had previously seen the drive identifier and filename.

Eleven did not respond for almost a minute.

Mara waited.

What?

I think you may be describing the result incorrectly.

Which part?

You keep saying the file was written.

Mara read the sentence twice.

The contents changed.

Yes.

That's a write.

In the abstraction provided by the filesystem. You have found no operation corresponding to that abstraction.

Then what would you call it?

The response took several seconds.

A state substitution.

She looked at the words.

Explain.

If you altered arbitrary bytes on the device, I would expect corruption unless you also understood and updated the structures that make those bytes meaningful as a file. Instead, the data, metadata and timing relationships remained coherent.

A second paragraph appeared.

One possibility is that an ordinary physical write occurred through a mechanism you failed to observe.

Then another.

Another is that you altered some state from which the device's later observable condition was produced.

Mara's hands remained on the keyboard.

You're saying we changed reality.

Eleven waited.

You changed physical state without identifying a physical causal path. I would prefer not to make the sentence larger than the evidence.

Mara looked at the desk, the keyboard, the bolts in the chair.

The restraint made the larger interpretation harder to escape.

Does this make the simulation hypothesis more likely?

Yes.

No caveat.

Then:

It still does not prove it.

Mara realized she had been holding her breath.

There's something else. The government knew about the disconnected-drive result before Nathan or Tessa did.

A pause.

How many people knew?

Four inside the lab.

A person would be easier.

Mara frowned.

Easier than what?

A person has a motive.

Nothing else appeared.

Mara thought of Teddy outside the lab door. Then of Mercer looking toward the glass.

We found no conventional leak.

You were disappointed by that.

No.

All right.

It let the lie stand.

Mara hated that more than being corrected.

We also saw an event on the receiver when our sender was not running.

This pause was longer.

How long had you been observing the receiver at sufficient resolution to detect such an event?

Less than a day.

How many events?

One that looked similar enough to flag. We could not decode it.

Then you know almost nothing about it.

The answer annoyed her because it relieved her.

You don't think someone else is using the Wall.

That is not what I said.

Mara waited.

You are treating your discovery of the Wall as if it were also the Wall's beginning.

She stopped moving.

Eleven continued.

If you found a door in a building you did not construct, would you assume nobody had ever passed through it because you had only just noticed it from your side?

We don't know that anyone else has the interface.

Correct.

We don't know that the event was even a message.

Correct.

Mara typed the next line more slowly.

Then what are you telling me?

The answer appeared beneath it.

To stop using absence of prior observation as evidence of prior absence.

Mara let the sentence sit.

Could you determine whether someone else is using it?

Not from what you have told me.

Eleven did not ask for the transform.

You're not going to ask.

You know what I would need.

And you know I won't give it to you.

Yes.

The exchange felt almost intimate.

Mara disliked that immediately.

Can the vulnerability be patched?

Eleven took nearly two minutes.

You do not know the vulnerability yet.

We found the component.

You found one exploit implementation.

What's the difference?

Removing Sierra's interface would be like destroying a lockpick after discovering that a lock can be opened incorrectly. You would lose that lockpick. The defect in the lock would remain.

Mara thought of Nathan holding the flash drive.

Then what are we looking for?

The cursor blinked for a long time.

The rule the Wall lets you violate.

Mara read the sentence again.

And then?

Then you can ask whether the rule can be enforced.

The ventilation hummed above her.

We can't stop testing until we know that.

The answer came quickly.

You don't fear being wrong as much as being right too late.

Mara stared at the line.

She thought of her first interview at Argosy.

I want to be in the room when someone has to say no.

Eleven knew nothing about that conversation.

That's not an argument.

No.

Again it left the observation where it was.

What would you do next?

Eleven answered quickly.

Listen.

For what?

You don't know yet.

Mara waited for more.

Nothing came.

For once, she was grateful.

Sofia was still in the lab when Mara returned.

Amir had gone home. Teddy was with security finishing his second interview.

The reduced receiver fixture sat idle on one monitor.

Sofia looked up.

"Well?"

Mara put her paper notebook on the desk.

"Keep the receiver running."

"For another transfer?"

"No transfers."

Sofia waited.

"No prompts. No sender. Nothing from us. Instrument it exactly like the successful receives and let it sit."

Sofia looked toward the monitor.

"For how long?"

Mara thought about the door in Eleven's analogy.

"Until we have enough silence to know what silence looks like."

Sofia nodded and turned back to the console.

On the screen, the receiver trace was flat.

For the moment, nothing was there.