📘 CHAPTER 3 — EXCEPTIONS THAT MAY NOT BE NAMED
693 Words
The "ANOMALY MATCH FOUND" message didn't reappear.
Lam sat motionless for almost a minute, his eyes glued to the screen.
He tried moving the cursor.
Nothing.
Refresh.
The 447-19-8832 file remained open, empty as before, as if the previous moment had been just a visual glitch due to fatigue.
But Lam knew he hadn't misread it.
In the Error Repository, there are three levels of alerts:
System fault
Ethical deviation
And anomaly
The final level almost doesn't exist in reality.
It's taught in training, as a historical note—something that was designed but never triggered.
No one on the Archivist team had ever seen it with their own eyes.
Lam lowered his hands from the keyboard.
He didn't log the event.
It was the first time in ten years of working that he hadn't followed the procedure.
His shift ended at six o'clock in the morning.
The Error Department's shift change was very smooth—the next person sat down, entered the code, and continued the previous person's work without asking a single question.
Lam stood up, put on his coat, but before leaving, he glanced at the screen one last time.
The blank file was still there, like a room so thoroughly cleaned that no one dared to enter.
He went outside as dawn broke.
The city in the early morning was operating at its usual rhythm: trams, billboards, commuters.
Everything seemed too normal compared to the feeling in his head.
Maybe I'm overreacting, Lam thought.
Maybe it's just a new module. An experiment.
He used to believe in those assumptions.
Believe that systems are always one step ahead of humans.
That afternoon, Lam returned to the Error Department earlier than usual.
He didn't give notice.
He didn't ask permission.
He didn't register for an additional shift.
The Error Warehouse doesn't forbid that.
It just… discourages it.
He sat down in an empty chair in the secondary access area—a place Archivist only uses when needing to cross-reference old data history.
An area few people frequent, because there's nothing new there.
Lam entered his personal code.
ACCESS GRANTED.
He opened a simple query:
List all records with an error index of 0.
The system processed it in a few seconds.
RESULT: 0 RECORDS FOUND.
He typed it again, adding an additional condition:
Include records that have been automatically processed.
The screen froze longer.
Then it showed:
RESULT: 1 RECORD FOUND.
Lam held his breath.
The ID slowly appeared.
447-19-8832
No other records.
Not a group.
Not a trend.
Just a single point.
A perfect exception.
He opened the edit history of that record.
Empty.
No creator.
No editor.
No input trace.
Even the time the record was “entered into the system” was blurred, like a number erased by hand.
Lam leaned back in his chair.
In the Bug Bank, everything has a source.
A bug always comes with a time.
A time always comes with a person.
This record is different.
It doesn't look like it was deleted.
It looks like…it was never written.
Lam closed all tabs.
He didn't dare dig any deeper during his shift.
He knew the system tracked query frequency, and that repeated questions formed a behavioral pattern.
A behavioral pattern is also a form of error.
Before leaving the Warehouse for the second time that day, he did something small, very small:
He opened his personal notebook—which wasn't connected to the internet—and jotted down a line:
447-19-8832—error-free record, but anomaly triggered.
The handwriting was illegible, not conforming to standard archiving.
But it existed.
Night fell.
Lam lay in bed, the ceiling dark.
He closed his eyes but couldn't sleep.
In his mind, the Error Warehouse was still lit.
The data streams were still running.
Errors were still being recorded—regularly, precisely, emotionlessly.
And somewhere, among millions of people, there was one person who left no trace.
Not because they were perfect.
But because… the system hadn't named their mistake.
For the first time, Lam considered a possibility that sent chills down his spine:
If the mistake wasn't recorded…
would that person still be considered to exist?
- Writer
