📘 CHAPTER 4 — REPETITIVE PATTERNS
629 Words
The second file didn't appear as a shock.
It came as a very small error—the kind one usually overlooks if you don't know what you're looking for.
Lam discovered it on the third day after his night shift.
He didn't search.
He didn't query.
He didn't do anything other than his usual routine: checking, verifying, closing files, forwarding.
The file was among hundreds of others, bearing an ID so ordinary it was almost anonymous.
512-03-7741
Nothing remarkable in the title.
No red flags.
No warnings.
Only when Lam opened the Error List did he stop.
It wasn't completely blank.
There was a line.
Error 0.0 — Unknown.
He frowned.
In the classification system, 0.0 is not a valid code.
Every error starts with 1.
Even the mildest error is 1.1 — slow response.
0.0 doesn't exist.
Lam scrolled down.
No description.
No timestamp.
No confirmer.
Just a single line, sitting there like an unreliable dot.
He looked around.
The Error Room was still noisy in its own way: the sound of typing, chairs being dragged, white light spreading across tired faces.
No one paid attention to him.
Lam closed the file.
Then opened it again.
Still the same.
He opened the edit history.
Empty.
But not the same empty as the first file.
Here, there was a trace of an attempt at notifying — as if someone had tried to name the error, but the system didn't accept it.
Lam felt his throat dry up.
The 447-19-8832 record is an absolute absence.
And this one… is an error that shouldn't exist.
During his lunch break, Lam didn't go out.
He opened his personal notebook, flipping to the page that held the first ID.
447-19-8832 — record with no errors, anomaly activated.
He added a new line below:
512-03-7741 — error 0.0, unknown.
The two lines of text stood side-by-side, unrelated, without explanation.
But Lam knew that in the Error Database, any coincidence was a signal.
He looked at the two IDs again.
Different regions.
Different ages.
Different occupations.
There was no common pattern that could explain it.
Except for one thing.
Neither of them was processed by the system in the normal way.
That afternoon, Lam received an internal memo.
Not a warning.
Not a reprimand.
Just a short, unsendered email:
Reminder: Archivists are advised not to store notes outside the system.
He read it over and over.
There was no evidence they knew about the manual.
No request for submission.
Just… a very polite reminder.
Lam deleted the email.
But his hands trembled slightly.
The Error Warehouse doesn't forbid thinking.
It only tracks behavior.
And repeated behavior… always leaves a trace.
That evening, on his way home, Lam noticed something very small.
At the train station, a man stood motionless in front of the ticket gate.
The scanner showed no error.
It didn't open.
It didn't close.
The man tried again.
Still no response.
Finally, the security guard arrived, swiped his own card to open the gate, and let the man through without saying a word.
No one questioned it.
No one took note.
Lam turned away.
He didn't know why he had noticed it.
Night fell.
He opened his notebook again, rereading the two lines of ID.
Then, for the first time, he added a sentence—not data, but an observation:
There are errors that aren't erased.
They just aren't allowed to have names.
Lam closed the notebook.
Outside, the city continued to function smoothly, as if nothing had changed.
But in the Error Warehouse, somewhere deep inside, a rule was repeating itself—not big enough to be detected, not small enough to be overlooked.
And Lam began to understand something that made him feel unsafe in his work:
Exceptions don't come alone.
- Writer
