THE ERROR BETWEEN US
Read Chapter 10: The Forecast
The morning after Theo kissed her, Eleanor found a forecast of their relationship on an internal server.
PROJECT ORPHEUS had been shut down.
The forecast had already been generated.
She opened it alone at 07:08.
PAIR TRAJECTORY SIMULATION E.VALE / T.MARCH
90-day probability of exclusive relationship: 0.81 180-day probability of major career change, Subject A: 0.67 180-day probability of major career change, Subject B: 0.41 365-day probability of cohabitation: 0.58 365-day probability of separation: 0.36 365-day probability of continued high-impact contact after separation: 0.79
She should have closed it.
Instead she scrolled.
Conflict drivers: privacy / institutional loyalty / planning asymmetry / grief substitution / autonomy interpretation.
Protective drivers: direct communication / low deception tendency / complementary uncertainty tolerance / mutual challenge without dependency capture.
Then:
MOST LIKELY HIGH-IMPACT EVENT: Subject A exits Lattice following ethical conflict. Subject B accepts major overseas commission. Relationship enters geographic instability.
Eleanor closed the window.
Then reopened it.
She hated herself slightly.
At nine, she was presenting to the executive committee.
“Become cannot launch on the current architecture,” she said. “Not as matching.”
Celia’s expression did not change.
Nathan asked, “Why?”
“Because transformation is not a user outcome we can safely optimise unless the user defines what transformation means.”
“Can we ask them?”
“Not with one onboarding screen.”
Eleanor advanced the deck.
“No score. No ‘you are ninety-four percent likely to change each other.’ No ranked matches. No destiny language. No intervention designed to preserve the relationship unless both users request it.”
Growth looked horrified.
Celia asked, “Then what is the product?”
“A discovery layer. Users can opt into meeting people outside their normal preference envelope. The system explains dimensions of difference, not predicted outcome.”
“Then why use Resonance at all?”
“To identify potentially generative difference while screening coercion and dependency risk.”
Nathan leaned back.
“You are turning our most powerful model into a suggestion engine.”
“I am turning it into something that respects uncertainty.”
Celia said, “That may not be commercially meaningful.”
“Then perhaps it should not be a product.”
Silence.
After the meeting, Nathan asked her to stay.
“You saw the forecast.”
Eleanor turned slowly.
“How do you know?”
“Access log.”
“You should not have generated it.”
“I didn’t.”
“Celia?”
“No.”
“Then who?”
“That’s what concerns me.”
They checked the audit chain.
The forecast had been generated automatically by a dormant workflow left inside Resonance’s original architecture.
Not human curiosity.
Machine continuation.
An instruction written eight years earlier:
FOR TOP 0.01% RESONANCE PAIRS, GENERATE LONG-HORIZON TRAJECTORY SIMULATION.
The system had simply obeyed.
Nathan stared at the code.
“This is why we killed it.”
“No,” Eleanor said. “You killed it because it hurt people.”
“That too.”
She printed the forecast.
Nathan looked at her.
“Why?”
“Because I’m showing Theo.”
“That may influence the outcome.”
“Yes.”
“Then the forecast becomes invalid.”
“Good.”
At lunch she met Theo beside the canal behind King’s Cross.
He read the pages.
“Apparently I’m going overseas.”
“Possibly.”
“You quit.”
“Possibly.”
“We break up.”
“Thirty-six percent.”
“And remain emotionally disruptive to each other.”
“Seventy-nine.”
Theo folded the paper.
“This thing is rude.”
Eleanor laughed.
Then he became serious.
“Does it bother you?”
“Yes.”
“Which part?”
“All of it.”
“No.”
He tapped the forecast.
“Which part?”
She looked at the line about separation.
“That.”
Theo’s face softened.
“Good.”
“Why good?”
“Because it bothers me too.”
They sat beside the canal. Autonomous delivery barges moved silently through green water.
Theo tore the forecast in half.
Eleanor stared.
“What are you doing?”
“Improving the data.”
He tore it again.
“You could have recycled it normally.”
“Less satisfying.”
She watched the pieces fall into a nearby paper bin.
“Now what?”
“Now I tell you something the system doesn’t know.”
“What?”
“I was offered a commission in Montreal three weeks ago.”
Eleanor felt a cold sensation under her ribs.
“You didn’t tell me.”
“We had kissed once.”
“The forecast knew.”
“It inferred.”
“That is not better.”
“No.”
“Are you going?”
“I haven’t decided.”
The future, which had felt theoretical on a screen, became immediate.
Eleanor heard herself ask, “When do you have to decide?”
Theo looked at her.
“Friday.”