The next morning, Lam arrived at the Warehouse on time.
Not early.
Not late.
No different from any of the previous days.
But as soon as he logged in, he knew something had changed.
Not the interface.
Not the access permissions.
But the response time.
The first file he opened processed about two seconds slower than usual.
The second fileâthree seconds.
The third fileâfive seconds.
Not enough to call it an error.
Not enough to trigger an Ops call.
Just enough to causeâĶ mild annoyance.
Lam tried opening another file, randomly.
Slow.
He switched to the local network.
Still the same.
The Error Warehouse wasn't malfunctioning.
It just wasn't prioritizing him as before.
"Is your computer lagging?"
A colleague at the next desk asked.
"A little," Lam replied.
â Strange, my machine is working fine.
The answer came casually.
But in Lam's mind, an invisible indicator had just moved down.
Not a bug.
Just individual priority.
During his lunch break, Lam opened his notebook.
The three dots, the upward curve from last nightâĶ had stopped.
He didn't draw anything more.
He only wrote one line:
System responds with delay.
In the afternoon, another small thing happened.
Lam submitted a request to switch shifts for the following week â a procedure he had done many times, always automatically approved.
This time, the system didn't reject it.
It changed its status to:
PENDING REVIEW
No reviewer.
No deadline.
Just pending.
When his shift ended, Lam stopped by his usual convenience store.
He bought a bottle of water and placed it on the counter.
The barcode scanner beeped.
The screen froze.
"Excuse me," the cashier said. "The machine is a bit slow."
She tried again.
The second time, the scanner worked.
"The system is like this a lot lately," she chuckled. "Probably due to an update."
Lam held the water bottle.
A coincidence is nothing.
The image started appearing on the screen.
That evening, Hai called.
"My appointment was just postponed," he said. "Not canceled. Just postponed. No reason."
"But the door is still open?" Lam asked.
"Open. ButâĶ as if someone is reconsidering."
Lam closed his eyes.
This was no longer silence.
This was observation.
As night fell, Lam turned on his personal computer.
He didn't log into the Warehouse.
He didn't query the logs.
He only opened the personal behavior dashboardâsomething every citizen has the right to view: general statistics, not details.
A graph appeared.
Interaction stability index: 98 â 94
No explanation.
No warning.
Just a number that had just been adjusted.
Lin stared at it for a long time.
In the Error Warehouse, somewhere very deep, a model was doing its job:
Optimizing.
Not punishing the individual.
Not eliminating immediately.
Only gradually reducing the favorability of behaviors that didn't conform to the optimal trajectory.
Lin understood something that sent a chill down his spine:
The system didn't ask him what he had done.
It only adjusted based on what he had made the world do differently.
Before going to bed, Lin opened his notebook again.
He didn't add any more dots.
He wrote:
Intervention creates feedback.
Feedback creates adjustment.
Then, very slowly, he added another line:
Adjustment not aimed at errors.
It's all about influence.
Lam closed the book.
He didn't know what line he had crossed.
But he knew one thing for sure:
From today, every step he took would be re-evaluated.
Not by law.
Not by people.
But by a system that had begunâĶ to take notice.