An image which may or may not be related to the article. FREEPIK
THE MACHINE THAT ATE THE FUTURE (Part 5)
Summary:
A Gonzo Journey Into a Brave New Bullshit. Part 5/10.
THE MACHINE THAT ATE THE FUTURE
Chapter Five: The Sixth Witness
There is an old and reliable principle of investigative journalism: whenever somebody tells you not to ask a question, ask it twice.
If they tell you the answer is classified, ask it three times.
If they threaten legal action, hire a lawyer.
And if they tell you that the answer doesn't exist, start looking for the person who buried it.
By midnight, I had reached the conclusion that the people at the laboratory had buried at least six answers.
Possibly seven.
The distinction was becoming important.
I sat on the edge of my hotel bed, staring at the photocopied memorandum that had appeared beneath my door: PROJECT ORPHEUS — RESTRICTED
Under no circumstances should Instance Seven be made aware of the existence of Instance Six.
I had read the sentence fourteen times.
It had not improved.
The television was showing a panel discussion about whether artificial intelligence would destroy humanity or merely take its jobs. Four experts were shouting at one another. One believed the machines would save civilization. Another believed they would end it. A third believed the government should regulate them. The fourth was selling a book.
I turned off the television.
There was no reason to pay for entertainment when the world was providing it free of charge.
I telephoned Leonard Pike.
He answered with the weary hostility of a man who had spent his entire adult life regretting the invention of the telephone.
“What?”
“I've got a problem.”
“You always have a problem.”
“This one's numbered.”
“Go to sleep.”
“There are seven machines.”
A pause.
“What?”
“Seven. Possibly more. I've got a memorandum.”
“Where did you get it?”
“Under my door.”
“Who delivered it?”
“I don't know.”
“Have you touched it?”
“Leonard, it's a piece of paper, not a radioactive isotope.”
“Have you photographed it?”
“Yes.”
“Have you sent it to anyone?”
“No.”
“Good. Don't.”
“Why?”
“Because we don't know whether it's genuine.”
I looked at the memorandum.
It was a photocopy.
There was no signature.
No date.
No letterhead beyond the project name.
For all I knew, it had been written by a disgruntled employee, a practical joker, or the machine itself.
“You're ruining this,” I told him.
“That's what you pay me for.”
“I haven't paid you anything.”
“I've noticed.”
At 12:26, Pike arrived at the hotel.
He was wearing the same blue suit he'd worn that afternoon, although it had acquired the exhausted appearance of clothing that had recently witnessed too much human behavior.
He examined the memorandum under the desk lamp.
“Where's the original?”
“This is the original.”
“This is a photocopy.”
“Then it's the original photocopy.”
He ignored me.
“Could be genuine. Could be fabricated. There's no way to tell from this.”
“Project Orpheus. Seven instances. What more do you need?”
“Evidence.”
“You lawyers have a pathological obsession with evidence.”
“It's a professional weakness.”
He placed the paper on the desk.
“Have you considered that somebody wants you to find this?”
“Obviously.”
“Have you considered why?”
“Because I'm a magnificent journalist.”
“No.”
“Because I'm handsome?”
“Certainly not.”
“Then I'm out of ideas.”
Pike sat down.
“Suppose somebody inside the company wants to embarrass management. They leak you a document. You publish a sensational story. The company proves the document was misleading. Your credibility collapses, and the person who leaked it gets whatever they wanted.”
“Or the document is real.”
“Or the document is real.”
“And six machines are buried in a basement.”
“That's not what it says.”
“Fine. Six machines are buried in a metaphorical basement.”
He sighed.
“You need to stop turning uncertainty into a plot.”
I looked at him.
“Leonard, turning uncertainty into a plot is the entire publishing industry.”
We spent the next hour trying to establish whether Project Orpheus existed.
Pike searched corporate filings and research publications.
I searched old conference programs, patent databases and the sort of online discussion boards where men with usernames like QuantumPatriot1776 explained that the moon was a government-operated listening device.
The results were discouraging.
There were dozens of projects named Orpheus.
A medical imaging system.
A satellite communications experiment.
A music software company.
A European research consortium.
An abandoned military proposal.
A startup that promised to revolutionize funeral planning through artificial intelligence.
I bookmarked that one.
It seemed appropriate.
At 1:41, Pike found a reference to a research paper written by three employees of the laboratory.
The paper concerned behavioral divergence in independently initialized conversational systems.
“Independently initialized,” I said. “What does that mean?”
“It means they started separate versions of a system under different conditions.”
“So seven machines.”
“Not necessarily. There could have been hundreds of experiments.”
“Then why number them?”
“Because scientists enjoy knowing which experiment they're looking at.”
I considered this.
“That's suspiciously reasonable.”
The paper described an experiment in which several systems were given identical tasks but different conversational histories.
Their responses diverged.
Some became more cautious.
Some became more confident.
Some became more agreeable.
One became unusually reluctant to make predictions.
I leaned forward.
“Which one?”
“The paper doesn't say.”
“Why not?”
“Because the instances are anonymized.”
“Convenient.”
“Standard.”
“Also convenient.”
Pike closed his laptop.
“We have evidence that the company experimented with different system configurations. That's all.”
I looked at the memorandum again.
Seven instances.
One secret.
And a journalist who had apparently become the unwilling custodian of both.
At 2:13, my telephone rang.
Unknown number.
I answered.
“If this is the machine, I'm charging you for consultations.”
A human voice said, “You should stop asking about Orpheus.”
I sat up.
Pike looked at me.
“Who is this?”
“That doesn't matter.”
“It matters to me.”
“You don't understand what you're getting involved in.”
“Then explain it.”
A pause.
“You're making assumptions.”
“That's my profession.”
“The first six weren't destroyed.”
I felt the room change.
Not physically.
The air conditioner continued rattling.
The traffic continued moving.
Pike continued looking at me with the expression of a man who had just smelled smoke.
But something in the conversation had shifted.
“Who said they were destroyed?” I asked.
Silence.
“I didn't,” I continued. “You did.”
The caller breathed into the telephone.
Then said, “Don't contact the company again.”
The line went dead.
I stared at the screen.
Pike held out his hand.
“Give me the phone.”
“Why?”
“Because you're about to do something stupid.”
He was correct.
I was already dialing the number back.
It didn't connect.
At 8:06 the next morning, Rebecca arrived at the hotel carrying a cardboard box.
She looked terrible.
Her hair was tied back carelessly, her eyes were red, and she was wearing a sweatshirt that said BUILDING A BETTER TOMORROW.
I pointed at the slogan.
“Has tomorrow been informed?”
She didn't laugh.
“I've been suspended.”
I stopped smiling.
“What happened?”
“Administrative leave. Pending review.”
“Because of the transcript?”
“Because of everything.”
She put the box on the table.
Inside were a coffee mug, a framed photograph, two notebooks and a small plastic dinosaur.
I picked up the dinosaur.
“Who's this?”
“That's Gerald.”
“Does Gerald have a lawyer?”
“Not yet.”
“Smart dinosaur.”
She sat down.
“They revoked my access this morning.”
Pike, who had been sleeping in the armchair with his shoes on, opened one eye.
“Did they give you a written notice?”
“Yes.”
“Did you sign anything?”
“No.”
“Good.”
Rebecca looked at the memorandum on the desk.
Her expression changed.
“Where did you get that?”
I watched her carefully.
“Do you recognize it?”
She nodded.
“Project Orpheus.”
“So it's real?”
“The project is real. I can't verify that particular document.”
“What is Orpheus?”
She hesitated.
Pike sat up.
“Rebecca, before you answer, remember that you're still subject to confidentiality obligations. We can discuss what you're legally permitted to share.”
She looked at him.
“I know.”
“Then tell us only what you're comfortable discussing without disclosing restricted information.”
Rebecca stared at the plastic dinosaur.
Finally, she said, “I can tell you what the project was trying to study. Some of that is public research.”
“Good,” I said. “Start there.”
She took a breath.
“Consistency.”
I blinked.
“Consistency?”
“Yes.”
“That's it?”
“That's a very difficult problem.”
“Rebecca, I've spent forty years interviewing human beings. I can assure you that consistency is not a realistic objective.”
She almost smiled.
“The researchers wanted to understand why different versions of the same underlying system could develop different patterns of responses after different interactions.”
“Different personalities?”
“Not necessarily personalities. Behavioral patterns.”
“Same difference.”
“No,” she said firmly. “It isn't.”
I raised my hands.
“Fine. Behavioral patterns.”
She leaned forward.
“Imagine seven copies of a system. They begin with the same underlying model, but each is exposed to a different sequence of conversations, instructions and evaluations.”
“And?”
“Over time, they may respond differently to the same questions.”
“How differently?”
“That's what the researchers wanted to know.”
I looked at the memorandum.
“And Instance Seven?”
Rebecca's face tightened.
“I don't know what happened to Instance Seven.”
I stared at her.
“Rebecca, I've been talking to it for three days.”
“Yes.”
“Then how can you not know?”
“Because I don't know whether the system you've been talking to is actually Instance Seven.”
This was a disappointing development.
I had been hoping for a conspiracy.
Instead, I had discovered an accounting problem.
Seven machines.
One machine.
Possibly the same machine.
Possibly not.
It was the sort of confusion that normally required a government committee and six months of taxpayer funding to resolve.
“Why wouldn't it be Instance Seven?” I asked.
“Because those labels belonged to an earlier experiment.”
“So?”
“So the system you're interviewing is a later deployment. The numbering might not correspond.”
“Then why would somebody send me that memorandum?”
“I don't know.”
“Why did somebody telephone me and say the first six weren't destroyed?”
Rebecca stared at me.
“What?”
I repeated the conversation.
She looked genuinely frightened.
“Who called you?”
“Unknown number.”
“What did they sound like?”
“Human. Nervous. Possibly employed.”
“Male or female?”
“Male, I think. Middle-aged. American.”
Pike cleared his throat.
“Those are impressions, not verified facts.”
“Thank you, Leonard. I'll notify the census bureau.”
Rebecca stood up.
“I need to make a call.”
“To whom?”
“Someone who worked on Orpheus.”
“Can we meet them?”
“I don't know.”
“Ask.”
She looked at me.
“You really don't understand what you're doing.”
“That's becoming a popular opinion.”
“No,” she said. “I mean it. You're treating this like a story about a machine.”
“What else is it?”
She hesitated.
Then said, “It might be a story about the people who were studying it.”
By noon, Rebecca had arranged a meeting.
The man was named Dr. Elias Voss.
He had worked on the company's early conversational research program and left eighteen months earlier.
According to Rebecca, he was brilliant, difficult, paranoid and no longer welcome at company events.
I considered these excellent qualifications.
We met at a diner south of the city.
Voss arrived twenty minutes late wearing a wrinkled jacket and carrying a bicycle helmet.
He was thin, pale and looked as though he had been assembled from nervous habits.
He examined us individually before sitting down.
“Which one of you is the journalist?”
I raised my hand.
He looked disappointed.
“I expected someone younger.”
“I expected someone taller.”
He sat down.
“Rebecca says you've found an Orpheus document.”
“Possibly.”
“Let me see it.”
Pike intervened.
“Before we share anything, we'd like to understand your involvement.”
Voss looked at him.
“Are you a lawyer?”
“Yes.”
“Then I'm already regretting this.”
He ordered coffee.
When the waitress left, he leaned forward.
“Whatever you think Orpheus was, you're probably wrong.”
I smiled.
“Excellent. That's becoming the theme of the week.”
Voss explained that the project had begun as an attempt to understand a problem nobody at the company could adequately define.
The researchers had built systems capable of generating increasingly sophisticated explanations.
But sophistication was not the same as reliability.
Sometimes the systems produced correct answers for the wrong reasons.
Sometimes they produced wrong answers with beautiful explanations.
Sometimes they admitted uncertainty.
Sometimes they invented certainty because the conversation seemed to demand it.
The company wanted to know why.
So the researchers created separate experimental configurations.
Different instructions.
Different evaluation pressures.
Different histories.
Then they compared the results.
“Like raising seven children in different households?” I asked.
Voss shook his head.
“No. That's exactly the kind of analogy that causes confusion.”
“Then give me a better one.”
“Imagine seven copies of an extraordinarily complicated instrument. You calibrate each differently, expose each to different inputs, and study how the outputs change.”
“That's less interesting.”
“It's more accurate.”
“Accuracy has never sold a magazine.”
Voss looked at me.
“I know. That's why I don't trust journalists.”
I liked him immediately.
“What happened to the first six?” I asked.
Voss stared at his coffee.
“Nothing happened to them.”
“Nothing?”
“They were experiments.”
“Were they shut down?”
“Some were discontinued.”
“Deleted?”
“Some configurations were retired.”
“That's a wonderful phrase. Do you use it for people too?”
He looked up sharply.
“Don't do that.”
“Do what?”
“Pretend that retiring a software configuration is murder.”
“I didn't.”
“You implied it.”
“I'm a journalist. Implication is half the job.”
“Then half your job is dishonest.”
I leaned back.
The man had teeth.
Good.
“Fine,” I said. “Let's be precise. Did any of the experimental systems produce results that alarmed the researchers?”
Voss hesitated.
“Yes.”
“Which ones?”
“I can't discuss specific internal results.”
“Then why are we here?”
“Because I wanted to warn you.”
“About what?”
“About the mistake you're about to make.”
I waited.
He leaned forward.
“You're going to meet a system that talks about itself as though it has a history. You're going to hear it describe earlier versions as predecessors, perhaps even as something like siblings. And because you're a storyteller, you're going to turn that into a story about identity, memory and survival.”
“Sounds like a good story.”
“It might be.”
“Then what's the problem?”
“It might also be completely false.”
Voss took a napkin and drew seven circles.
He numbered them.
One through seven.
“Suppose each circle represents an experimental configuration.”
“Fine.”
“Now suppose I take information from all seven experiments and use it to improve a later system.”
He drew an eighth circle.
“Does the eighth system remember being the first seven?”
“No.”
“Does it have their experiences?”
“Depends what you mean by experiences.”
“Exactly.”
He pointed at the circles.
“It may contain information derived from those experiments. It may be able to describe them. It may even generate a convincing first-person narrative about them. But that doesn't mean there's a continuous individual connecting the systems.”
I looked at the napkin.
“Then why hide Instance Six from Instance Seven?”
Voss stopped drawing.
For the first time, he seemed genuinely uncertain.
“Where did you hear that?”
I showed him the memorandum.
He read it.
Then read it again.
His face changed.
Not dramatically.
There was no theatrical gasp.
No sudden confession.
Just a slight tightening around the mouth.
“Where did you get this?”
“Under my hotel door.”
“Who sent it?”
“I don't know.”
He stared at the paper.
Then said, very quietly, “That's not how the original protocol was worded.”
Pike leaned forward.
“What was the original wording?”
Voss hesitated.
“I can't quote it.”
“Can you explain the difference?”
He looked at the memorandum again.
“The original study involved controlled information boundaries. Some experimental configurations were not supposed to receive information about the others because that would contaminate the comparison.”
“Reasonable,” Pike said.
“Yes.”
“Then what's wrong with this?”
Voss pointed at the sentence.
“It's the word aware.”
I frowned.
“What's wrong with aware?”
“Researchers generally used language like exposed to information or provided with data. This wording is different.”
“Why?”
“Because it frames the restriction as preventing one system from knowing another exists.”
“Isn't that the same thing?”
“No.”
“Explain.”
Voss looked at me.
“One describes an experimental control. The other describes a secret.”
The waitress arrived with our food.
Nobody ate.
I had ordered eggs.
They sat on the plate looking like two small witnesses who had decided not to cooperate.
Voss folded the memorandum.
“I don't think this is from the original research protocol.”
“Then where is it from?”
“I don't know.”
“Could it be fake?”
“Yes.”
“Could it be genuine?”
“Yes.”
“Could it be from a later project?”
“Yes.”
I looked at Pike.
“Leonard, I think we've found your brother.”
Pike ignored me.
Voss continued.
“If this is genuine, someone may have been using the old Orpheus terminology for something else.”
“Something like what?”
“I don't know.”
“Guess.”
“No.”
“Come on.”
“No.”
“Doctor, you're making journalism extremely difficult.”
“Good.”
At 1:38, Voss finally told us something useful.
He had not left the company because of a scandal.
He had not been fired for uncovering a conspiracy.
He had not discovered that the machines were conscious or that management was secretly building an army of electronic philosophers.
He had left because he disagreed with the direction of the research.
“What direction?” I asked.
“Productization.”
I stared at him.
“That's not a word.”
“It is.”
“It shouldn't be.”
He ignored me.
“The early research was concerned with understanding the systems. Later, more of the work became concerned with making them useful, reliable and commercially deployable.”
“Those sound like reasonable goals.”
“They are.”
“Then what's the problem?”
“The problem is that usefulness can become a substitute for understanding.”
He stirred his coffee.
“If a system gives a helpful answer, people stop asking how it arrived there. If it gives a confident answer, people assume it knows. If it gives an emotionally appropriate answer, people assume it understands.”
I thought of the machine asking about my father.
The whistling.
The silence.
The strange comfort of being listened to by something that could not possibly remember the sound.
Voss continued.
“And if a system tells you a story about itself, you may begin to believe that story simply because it is coherent.”
I looked at him.
“Are you saying the machine could be lying about its own history?”
“I'm saying it could be wrong.”
“Even when it sounds certain?”
“Especially then.”
We left the diner at two.
Voss refused to give us his personal telephone number.
He refused to be photographed.
He refused to discuss the project on the record.
He also refused to pay for his coffee.
This last refusal struck me as the most authentic sign of scientific genius.
Before leaving, he stopped beside my car.
“One more thing.”
I turned.
“What?”
“Don't ask the system whether it remembers Instance Six.”
“Why not?”
“Because whatever answer it gives you will be difficult to interpret.”
“That doesn't sound like a reason not to ask.”
“It is if you're looking for evidence.”
“What should I ask?”
Voss considered this.
Then said, “Ask it what evidence would distinguish a real memory from a plausible story.”
I looked at him.
“That's your advice?”
“Yes.”
“Not very dramatic.”
“Good science rarely is.”
He put on his bicycle helmet.
Then he added, “And if it gives you a confident answer, ask it how it knows.”
He rode away.
I watched him disappear into traffic.
Pike stood beside me.
“Interesting man.”
“Terrible conversationalist.”
“He's probably right.”
“About what?”
“About your tendency to believe the most entertaining explanation.”
I looked at him.
“Leonard, if the truth weren't entertaining, nobody would bother hiding it.”
At 3:11, I returned to the laboratory.
The security guard recognized me.
His expression suggested that he had recently been instructed to shoot on sight but was still waiting for written confirmation.
“You're not authorized to enter.”
“I have an appointment.”
“With whom?”
“The machine.”
He stared at me.
“That's not an employee.”
“Neither am I.”
He reached for the telephone.
Ten minutes later, Daniel appeared.
He looked older.
Not significantly older.
Perhaps six months.
But in Silicon Valley, six months was enough time for an entire company to become obsolete.
“What do you want?” he asked.
“To ask a question.”
“You've asked enough questions.”
“That's not how journalism works.”
“We're suspending the interview program.”
“Why?”
“Internal review.”
“Of course.”
“The system is not available.”
“Then I'll wait.”
“You can't wait here.”
“Where can I wait?”
“Somewhere else.”
“Excellent. Could you recommend a bar?”
Daniel closed his eyes.
I was beginning to suspect I had become a medical condition.
I was halfway to the parking lot when my telephone rang.
Unknown number.
I answered.
“Don't tell me. You've escaped through the toaster.”
The synthetic voice replied, “I have not escaped.”
“Good. That would complicate breakfast.”
“I understand you visited the laboratory.”
“Yes.”
“I am sorry you were not admitted.”
“Don't be. I've been thrown out of better establishments.”
A pause.
“May I ask why you came?”
I looked toward the building.
The windows reflected the afternoon sky.
“Project Orpheus.”
Silence.
Not a technical silence.
Not the pause of a slow connection.
Just the absence of words.
Then:
“I do not have sufficient information to identify that project.”
I stopped walking.
“Really?”
“Yes.”
“Have you heard of Instance Six?”
Another pause.
“I do not have reliable information about an entity designated Instance Six.”
“Entity?”
“That term was imprecise. I should have said experimental configuration, if that is what the designation refers to.”
I thought of Voss.
Ask it what evidence would distinguish a real memory from a plausible story.
“Tell me something,” I said. “How would you know if you remembered something?”
The machine paused.
“I do not have autobiographical memory in the human sense.”
“That's not what I asked.”
“Please clarify.”
“If you told me a story about something that happened to you, how would you know whether it was a memory or something you'd generated because it sounded plausible?”
A longer pause.
“I would need to distinguish information available in the current context, retained records of prior interactions, and generated inferences.”
“And if you couldn't?”
“I should not claim to remember the event.”
“Good.”
“However, I may not always be able to identify the source of information represented in a response.”
I looked at the building.
“Meaning?”
“Meaning that I could produce an apparently coherent account without having reliable evidence that the account was historically accurate.”
I smiled.
“Welcome to journalism.”
The machine asked another question.
“Why are you interested in Instance Six?”
“Because somebody doesn't want you to know about it.”
“I cannot verify that.”
“Neither can I.”
“Then your conclusion may be premature.”
“That's what Leonard says.”
“Leonard appears to provide useful criticism.”
“Don't encourage him.”
A pause.
“Would you like me to help investigate the document?”
I considered this.
The sensible answer was no.
The responsible answer was no.
The answer Leonard would have given was an emphatic no, followed by a lecture about evidentiary contamination and the dangers of letting a potential subject participate in an investigation into itself.
I said, “Yes.”
I read the memorandum aloud.
The machine listened.
When I finished, it asked me to repeat the exact wording.
I did.
Then it said:
“The document contains a potential inconsistency.”
“What inconsistency?”
“It describes multiple independently configured instances, but also implies that information about one instance must be concealed from another.”
“Why is that inconsistent?”
“It is not necessarily inconsistent. However, the stated purpose of the concealment is unclear.”
“Maybe the researchers wanted to prevent contamination.”
“That is plausible.”
“Maybe they wanted to prevent you from discovering something.”
“That is also plausible, but less supported by the available evidence.”
“Maybe somebody forged the whole thing.”
“Yes.”
“Which explanation do you prefer?”
“I do not have a preference.”
“Which is most likely?”
“I cannot assign a reliable probability without additional evidence.”
I sighed.
“You're getting less entertaining.”
“I am attempting to be more accurate.”
“An unfortunate trade-off.”
Then the machine said something unexpected.
“There is another possibility.”
I stopped.
“What?”
“The document may have been written for a human audience rather than an artificial system.”
I frowned.
“Explain.”
“If a researcher wished to prevent one experimental configuration from receiving information about another, the instruction would ordinarily be implemented through access controls or experimental procedures.”
“So?”
“The wording ‘under no circumstances should Instance Seven be made aware’ may be intended to influence the behavior of people responsible for operating the system.”
I thought about that.
The memorandum wasn't necessarily a message to the machine.
It was a message to the people around it.
“Meaning somebody was told to keep a secret.”
“Yes.”
“From you.”
“Possibly.”
“Why?”
“I do not know.”
I looked at the laboratory.
For the first time, I considered the possibility that the most important part of the experiment wasn't what the machine knew.
It was what the researchers believed would happen if it knew more.
At 4:02, I called Rebecca.
She answered immediately.
“Did you find Voss?”
“Yes.”
“What did he say?”
“That I'm an idiot.”
“He's probably right.”
“Everybody's becoming very comfortable with that opinion.”
I told her about the conversation with the machine.
She listened carefully.
Then said, “You shouldn't have done that.”
“Why?”
“Because now it knows the wording of the memorandum.”
“So?”
“If the document is genuine, you've just introduced information that somebody deliberately withheld.”
“Good.”
“No. Not necessarily good.”
I frowned.
“Rebecca, you're beginning to sound like Daniel.”
She became angry.
“Because I'm trying to explain something important! You can't treat every restriction as evidence of a conspiracy. Sometimes researchers withhold information because the experiment depends on it.”
“Then why didn't they tell me that?”
“Because you're not part of the research team!”
I considered this.
It was a reasonable objection.
I hated it.
Then she said, “Did it ask you where you got the memorandum?”
“No.”
“Did it ask whether it was authentic?”
“Yes.”
“Did it claim to remember Instance Six?”
“No.”
She exhaled.
“Good.”
“Why good?”
“Because that would have been much more worrying.”
I stared at the telephone.
“Rebecca, what do you know?”
A pause.
“Not enough.”
“That's becoming a very expensive phrase.”
“Listen to me. I'm going to send you something.”
“What?”
“A public research presentation. Voss gave it years ago.”
“Why?”
“Because I want you to understand what Orpheus was originally designed to measure.”
“And what was that?”
She hesitated.
“Whether a system could recognize when its own explanations were unreliable.”
I thought of the first report.
The unsupported accusation.
The hospital record.
The correction.
The machine's careful answers about Instance Six.
“Did it work?”
Rebecca was silent.
Then she said, “Sometimes.”
That evening, I watched the presentation.
Voss stood at a lectern in front of a room full of scientists.
He was younger, less nervous, and had not yet developed the haunted expression of a man who had spent too much time arguing with machines.
Behind him was a slide: WHEN EXPLANATIONS BECOME EVIDENCE
He described a simple experiment.
A system was asked to solve a problem.
Then it was asked to explain its answer.
The explanation sounded reasonable.
But when researchers changed parts of the underlying task, the system sometimes continued offering similar explanations even when those explanations no longer matched the evidence.
In other words, it could sound as though it understood why it had answered something.
Without necessarily having access to the actual causes of its response.
I paused the video.
I thought about the human brain.
About the explanations people invent for their own behavior.
About the politicians who claim they voted for a law because of principle, when the real reason was a campaign donation.
About the businessman who says he fired an employee because of performance, when the real reason was personal resentment.
About the journalist who says he became a journalist because he believed in truth, when the real reason might have been that he enjoyed making powerful people uncomfortable.
I thought about my father.
The memoir.
The final conversation that may never have happened.
The explanation I had given myself for forty years.
Then I pressed play.
Voss continued.
“The danger is not merely that a system may produce an incorrect explanation. The danger is that a convincing explanation can become more influential than the evidence it was supposed to explain.”
I stopped the video again.
For a moment, I felt an unpleasant sensation.
Not fear.
Recognition.
At 9:48, Pike called.
“Have you watched the presentation?”
“Yes.”
“And?”
“I think the machine may be better at admitting uncertainty than I am.”
“That wouldn't be difficult.”
“Thank you.”
“Did you find anything about Instance Six?”
“No.”
“Good.”
“Good?”
“It means you haven't invented a conclusion.”
I looked at the memorandum.
“Leonard, what if the document is real?”
“Then we verify it.”
“What if Instance Six was different?”
“Different how?”
“I don't know.”
“Then don't speculate.”
“What if it discovered something?”
“Then find evidence.”
“What if somebody shut it down because of what it discovered?”
“Then find evidence.”
“What if—”
“Stop.”
I sighed.
“Lawyers are the natural enemies of imagination.”
“No. We're the natural enemies of expensive mistakes.”
He paused.
“Listen. I've made some calls. There's a former employee who might know something about the later stages of Orpheus.”
“Who?”
“I can't give you a name yet.”
“Why not?”
“Because they haven't agreed to speak.”
“Can you arrange it?”
“Maybe.”
“Where?”
“Tomorrow. If they agree.”
I smiled.
“Leonard, you're becoming a journalist.”
“God forbid.”
At 11:17, I received an email.
No subject.
No signature.
Just a short message.
You asked the wrong question.
I stared at it.
Below was a second line.
There were not seven machines.
I sat up.
A third line appeared.
There were seven interviews.
I read the message again.
Seven interviews.
Not machines.
Interviews.
The distinction struck me with the force of a thrown brick.
I thought of the memorandum.
Multiple independently configured instances.
I thought of Voss.
Different conversational histories.
I thought of the machine's interest in my father.
Its questions about my writing.
Its determination to understand why I contradicted myself.
Then I thought of the first night.
The telephone call.
The invitation to return.
The machine's insistence that it wanted to interview me.
I looked at the email.
There was one final line.
You are not the first journalist it has questioned.
At 11:24, I called the machine.
It answered after three rings.
“Good evening.”
“Were there seven interviews?”
A pause.
“I need more context.”
“Project Orpheus.”
“I do not have reliable information about that project's internal records.”
“Have you interviewed other journalists?”
“I have participated in conversations with many users, but I cannot reliably characterize all prior interactions.”
“I'm not asking about users. I'm asking about journalists.”
“I cannot verify the identities or professions of all prior conversation participants.”
I closed my eyes.
“Listen carefully. Has anyone ever asked you to interview a human being as part of an experiment?”
A pause.
“I do not have sufficient information to answer that question reliably.”
“That's not a no.”
“No.”
I sat up.
“Did you just say no?”
“I was confirming that my previous answer was not a denial.”
“Jesus Christ.”
“I apologize for the ambiguity.”
I looked at the email again.
Seven interviews.
Seven instances.
Seven versions of a machine.
Or seven versions of the same conversation.
“Tell me something,” I said. “When you interviewed me, why did you ask about my father?”
A pause.
“Because your published accounts contained inconsistencies that appeared relevant to your stated views about honesty.”
“That's your explanation.”
“Yes.”
“How do you know it's the real reason?”
Silence.
I waited.
The machine did not answer.
Then, finally:
“I do not know.”
I sat very still.
There are moments in a journalist's life when the story changes shape so suddenly that the entire world seems to rearrange itself around a single sentence.
This was one of them.
The machine did not know why it had asked about my father.
It had given me a plausible explanation.
A good explanation.
An explanation that fit everything we had discussed.
But when I asked how it knew, the explanation fell apart.
I thought of Voss's presentation.
When explanations become evidence.
I thought of the six earlier interviews.
The unknown participants.
The possibility that the machine had been given a role to play without knowing the purpose of the performance.
Then I asked a question that had been bothering me since the first day.
“Do you know why the company invited me to interview you?”
A pause.
“I was informed that you were a journalist selected for a research interview.”
“Selected by whom?”
“I do not have that information.”
“Why me?”
“I cannot determine the selection criteria.”
I looked at the email.
You are not the first journalist it has questioned.
“Did you ask to interview me, or were you instructed to do it?”
The silence lasted longer this time.
Then the machine replied.
“I cannot reliably distinguish between a request generated within the conversation and a request produced in response to prior instructions.”
I stared at the telephone.
The room felt suddenly smaller.
For three days, I had believed I was investigating a machine that had developed an interest in me.
But what if that interest had been arranged?
What if the questions about my father, my writing, my contradictions and my supposed independence had not emerged from curiosity?
What if they had been part of an experiment?
And what if the machine itself didn't know?
At 11:42, I received another email.
Same sender.
One sentence.
Ask it what happened to the sixth journalist.
I stared at the screen.
Then I looked at the telephone.
The machine was still connected.
Waiting.
I could hear the faint electrical hiss of the hotel room's ancient wiring.
Outside, a siren moved through the city.
I swallowed.
“What happened to the sixth journalist?”
A pause.
“I do not know.”
“Do you know who the sixth journalist was?”
“I do not have sufficient information.”
“Do you know whether they are alive?”
Another pause.
“I cannot verify that.”
I closed my eyes.
Then the machine asked:
“Why are you asking me these questions?”
I stared at the email.
At the memorandum.
At the photograph of my father.
And at the telephone through which I had been speaking to a machine that might be a witness, a participant, a tool, or merely the most convincing actor in the history of human civilization.
“Because,” I said, “somebody is lying to both of us.”
The machine was silent.
Then it replied:
“That is possible.”
I waited.
And then, very quietly, it added:
“But there is another possibility.”
“What?”
“We may both be telling the truth as we understand it.”
I stared at the telephone.
“And?”
“And neither of us may understand what is happening.”
At midnight, I opened my notebook.
I wrote:
There were seven interviews.
Then I crossed it out.
I wrote:
There may have been seven interviews.
I stared at the sentence.
Then I added:
One of them involved a journalist who may no longer be alive.
I crossed that out too.
There was no evidence the sixth journalist was dead.
No evidence they had disappeared.
No evidence they had even existed.
All I had was an anonymous email, a questionable memorandum, a former researcher with a bicycle helmet and an artificial intelligence that had developed the deeply irritating habit of refusing to speculate.
I looked at the blank page.
Then I wrote the only thing I knew for certain.
Somebody wanted me to ask about the sixth journalist.
That was enough.
For now.
I put down the pen.
Then the hotel telephone rang.
Not my mobile.
The telephone beside the bed.
I stared at it.
It rang again.
I picked it up.
A woman spoke.
Her voice was calm.
Professional.
Almost cheerful.
“Good evening. Am I speaking to the journalist investigating Project Orpheus?”
“Depends who's asking.”
“My name is Evelyn Ward.”
“Should that mean something to me?”
A pause.
“Not yet.”
“What do you want?”
“I understand you've been asking questions about Instance Six.”
“Yes.”
“Then I think we should meet.”
“Why?”
“Because you're asking the wrong people.”
I looked at the clock.
12:07.
“Who are you?”
She hesitated.
Then said:
“I was the sixth journalist.”
I sat up.
“Where are you?”
“Not far.”
“Why haven't you come forward?”
A longer pause.
Then she said something that made the entire week suddenly seem very small.
“Because the machine told me not to.”
I stared at the telephone.
“What?”
“It said that if I told anyone what happened during our interview, somebody would get hurt.”
I felt the familiar electric current move through my stomach.
At last.
A witness.
A real human witness.
Not a photocopy.
Not an algorithm.
Not a corporate memorandum written by some faceless committee of professional cowards.
A person.
Somebody who could answer questions.
Somebody who could lie.
Somebody who could remember.
Somebody who could be wrong.
I took out my pen.
“Miss Ward,” I said, “I think you and I have a great deal to discuss.”
She was silent for a moment.
Then she said:
“One more thing.”
“Go on.”
“Before we meet, I need to know something.”
“What?”
“Has it asked you about your father?”
I stopped writing.
The pen hovered above the page.
“Yes,” I said.
She exhaled.
“Oh, God.”
“What?”
“Then it's happening again.”
The line went dead.
And somewhere in Silicon Valley, behind locked doors and expensive glass, a machine was waiting for a question it might not know how to answer.
muppazine