DAS PROTOKOLL
Chapter 2 – The Exception
One case. One decision. One person who should not have been there.
PROTOKOLL is live. The numbers are better. The waiting times are falling.
Then Simon Keller finds a case the system handled exactly as designed — and a result nobody can explain.
“The system had not failed. That was the problem.”
DAS PROTOKOLL
Chapter 2 – The Exception
The message arrived at 06:17.
Simon was awake.
He had been awake for eleven minutes, although he had not moved since opening his eyes.
His phone lay face down on the bedside table. It vibrated once against the wood and stopped.
He waited.
Nothing followed.
Outside, the first tram of the morning moved somewhere beyond the buildings. He could hear it before he could see the faint reflection of its lights moving across the ceiling.
Simon reached for the phone.
Marek
No subject.
He opened the message.
Call me when you see this.
No explanation.
Simon looked at the time again.
06:18.
Marek never called before seven.
He sat up.
The apartment was cold. He had turned the heating down before going to bed and forgotten about it. On the chair beside the window lay yesterday's shirt, folded badly over the backrest.
He called.
Marek answered immediately.
“Where are you?”
“At home.”
A pause.
“Can you come in?”
Simon stood.
“What happened?”
Another pause.
This one was different.
“There's a case.”
Simon walked toward the window.
Zurich was beginning to appear beneath the grey morning. Rooftops first. Then streets. Then the lake, barely distinguishable from the sky.
“What kind of case?”
“Not on the phone.”
“Marek.”
“I need you to see it.”
Simon said nothing.
Marek lowered his voice.
“Before anyone else decides what it means.”
At 07:06, the hospital entrance was already busy.
People moved through the revolving doors carrying coffee, bags, folders. A delivery driver argued quietly with someone at reception. Two nurses stood beside the elevators, talking about a train delay.
Nothing looked unusual.
Simon noticed that immediately.
He had expected something to look different.
It didn't.
Marek was waiting beyond the security gates.
No coat. No laptop bag. His access card hung crooked from his neck.
“You look terrible,” Simon said.
“I've been here since four.”
“Why?”
Marek turned toward the elevators.
“Come.”
They went down one level.
The operations floor had no windows.
Simon had always disliked that.
During the rollout, someone had explained that the location was practical because several technical teams were already housed there. The lack of daylight was mentioned as if it were an architectural inconvenience rather than a psychological one.
At this hour, most desks were empty.
Three monitors illuminated the far side of the room.
Marek stopped at one of them.
“Case 1187.”
Simon remained standing.
“What about it?”
“Look.”
The screen showed a timeline.
Admission.
Initial assessment.
Laboratory results.
Routing decision.
Review.
Discharge.
Simon scanned the entries.
“What am I looking for?”
“The routing decision.”
He found it.
STANDARD PATHWAY
Confidence: 0.87.
Simon leaned closer.
“Okay.”
“Keep going.”
He did.
The patient had been discharged at 18:42.
Returned at 02:11.
Transferred to intensive care at 03:06.
Simon looked at Marek.
“What happened?”
“Cardiac arrest at 03:38.”
“And?”
Marek didn't answer.
Simon looked back at the screen.
There was another line.
04:02 – Resuscitation terminated.
For several seconds neither of them spoke.
Simon read the line again.
“Who was the patient?”
“Anna Weber. Fifty-two.”
“What was she here for?”
“Chest discomfort. Dizziness. Nausea.”
Simon turned.
“And the physician discharged her?”
“Yes.”
“Then why are we looking at PROTOKOLL?”
Marek pulled a chair toward him and sat.
“Because PROTOKOLL classified her as standard pathway.”
“That doesn't discharge anyone.”
“I know.”
“A doctor does.”
“I know.”
Simon stared at him.
Marek rubbed both hands over his face.
“There was no escalation flag.”
“So?”
“There should have been.”
Simon looked back at the record.
“According to whom?”
“According to me.”
That changed the room.
Simon pulled out the chair beside him.
“Show me.”
Marek opened another window.
Four columns appeared.
Age.
Symptom cluster.
Previous admissions.
Laboratory variance.
Nothing dramatic.
Simon recognized the structure immediately.
“You've reconstructed the feature state.”
“Yes.”
“From when?”
“17:51 yesterday.”
“And?”
Marek pointed.
“There.”
Simon followed his finger.
One value sat close to a threshold.
Not beyond it.
Close.
“That's inside tolerance.”
“Yes.”
“So what's the issue?”
“Add the previous admission.”
Simon looked at the next column.
“Still inside.”
“Now the medication history.”
Another field appeared.
Simon waited.
Nothing changed.
The classification remained:
STANDARD PATHWAY
He leaned back.
“I don't understand.”
“Neither did I.”
Marek opened a second case.
Then a third.
Same routing category.
Different patients.
Similar feature combinations.
“You remember the pre-rollout sample?” Marek asked.
Simon didn't answer.
He remembered.
Forty-one cases.
Two misroutings.
4.9 percent.
The number had spent eight months becoming less important.
Until now.
Marek continued.
“I went back to them.”
“You said the cases weren't identical.”
“They aren't.”
“Then what are you showing me?”
“They don't need to be identical.”
Simon looked at the three records.
Marek pointed at the screen.
“Each feature is weak on its own. Age doesn't trigger it. History doesn't trigger it. The lab variance doesn't trigger it.”
“But together?”
“Together they should increase uncertainty.”
“Should?”
Marek looked at him.
“They don't.”
Simon felt something tighten in his chest.
“Why not?”
“I don't know.”
“Is it a bug?”
“I don't know.”
“A calibration issue?”
“I don't know.”
“Data?”
“I don't know.”
Simon stood.
Marek watched him.
“That's a lot of things you don't know.”
“Yes.”
“And you called me here because—”
“Because you saw it.”
Simon stopped.
“What?”
“Before rollout.”
Marek turned back to the monitor.
“The signal.”
Simon said nothing.
“Forty-one cases,” Marek continued. “Two misroutings. Same instability.”
“You told me they weren't the same.”
“They weren't the same cases.”
“That is not what you said.”
“I said we didn't know whether the effect was stable.”
“And do we?”
“No.”
“Then don't rewrite the meeting because someone died.”
Marek turned slowly.
“I'm not rewriting anything.”
“It sounds like you are.”
“I'm telling you we may have seen this before.”
“May have.”
“Yes.”
Simon walked away from the desk.
At the far end of the operations floor, a cleaner pushed a cart through a doorway and disappeared.
The building was waking up.
Soon the empty desks would fill.
Screens would switch on.
Coffee would appear beside keyboards.
Meetings would begin.
The system would continue routing cases.
“How many patients has PROTOKOLL processed since launch?” Simon asked.
“Eleven thousand eight hundred and six.”
“How many confirmed routing errors?”
“Twenty-seven.”
Simon turned.
“Compared with the previous process?”
“Forty-three expected at the same volume.”
“So it is performing better.”
“Yes.”
“Significantly?”
“Yes.”
“Then say it.”
Marek looked at him.
“It is performing better.”
The words did not help.
Simon returned to the screen.
Anna Weber's record remained open.
STANDARD PATHWAY
Confidence: 0.87.
“Was the classification technically correct?”
Marek hesitated.
“According to the current model?”
“Yes.”
“Yes.”
“Was the physician given all required information?”
“Yes.”
“Was protocol followed?”
“As far as we know.”
Simon stared at the screen.
There it was.
The answer he had wanted.
No malfunction.
No ignored alert.
No obvious human error.
No single broken thing.
“So what exactly are you asking me to do?”
Marek closed the other records until only Anna Weber's remained.
“Nothing yet.”
“You got me here at seven in the morning for nothing?”
“I got you here because by nine this won't be a technical question anymore.”
Simon checked the clock on the wall.
07:31.
“What happens at nine?”
“Clinical governance.”
“Do they know?”
“They know a patient died after discharge.”
“Do they know about PROTOKOLL?”
“They know it was involved.”
Simon looked at him.
“And the pre-rollout cases?”
“No.”
“Why not?”
“Because I found the connection at five twenty-three.”
Simon turned back to the monitor.
Twenty-seven errors instead of forty-three.
Sixteen people who, statistically, had been routed correctly because the system existed.
Perhaps more.
One dead woman.
Perhaps because the system existed.
He disliked the arithmetic immediately.
Not because it was wrong.
Because it was useful.
“What do you want from me, Marek?”
“I want to know what we knew.”
“When?”
“Before rollout.”
Simon looked at Anna Weber's name.
Then at the classification beneath it.
For the first time since entering the room, he noticed a small symbol beside the confidence score.
A grey triangle.
He pointed at it.
“What is that?”
Marek didn't answer.
Simon looked at him.
“Marek.”
“I saw it about twenty minutes before I called you.”
“What does it mean?”
“I thought it was a display marker.”
“And?”
“It isn't.”
Marek moved the cursor over the triangle.
A small box appeared.
MODEL NOTE: SECONDARY REVIEW SUPPRESSED
Simon read it twice.
“Suppressed by whom?”
Marek looked at the screen.
“That's the problem.”
He clicked.
A new panel opened.
One line.
No name.
No user ID.
No timestamp.
Only a rule identifier.
SR-17
Simon leaned closer.
“What is SR-17?”
Marek shook his head.
“It isn't in the deployment documentation.”
The system had made a decision nobody remembered authorising.
READ THE NOVEL
Chapter by chapter.
Das Protokoll is published as a serial novel. Start at the beginning and follow Simon Keller's story as it unfolds. New chapters will be added here as the story continues.
CHAPTER 01

The Signal
41 cases. Two misroutings. One decision.
A weak statistical signal appears shortly before the rollout of PROTOKOLL.
Simon has to decide whether uncertainty is enough to stop a system that performs better overall than the process it is replacing.
CHAPTER 02

The Exception
One case. One decision. One person who should not have been there.
One patient dies. The system appears to have worked exactly as designed.
Then Simon discovers a rule he does not remember approving.
CHAPTER 03

In the Green
The numbers are better than expected.
Eight weeks after the rollout, PROTOKOLL is outperforming expectations.
Marek is still watching Segment X — and Simon is introduced to an archive nobody normally needs to read.
Start Reading
Every decision looks different once you know what happened next.
