end field

Chapter 11: The Incompatible Person

Huy started neglecting small things.

Not the big things—the big things the system always puts on checklists, with reminders and warnings. Small things: reporting a small fault in a serviced equipment; updating a status line to “checked” when he knew he’d only glanced at it; misnaming a data cassette so it wouldn’t show up correctly in the priority interface.

These things didn’t trigger immediate warnings. They were on the fringes: a misaligned line, a small delay, a skipped meta-line. They were enough to cause a shift to be delayed by a few minutes, to divert a team, to cause a generator to overheat for a short period. No one died. Not a single log entry was marked in red. Only minor indicators fluctuated, then returned to normal.

I first noticed Huy the day he forgot to close a maintenance ticket. Normally, he stayed up late updating reports. That time, he left early, leaving a line open. The person on the next shift had to open and close the task; it took a few minutes, but the system registered the delay and assigned his team a blinking point for behavioral reliability. The blinking point wasn't large. It was enough to add another gray dot to the record.

I called him to the dispatch office two days later. He came, neither bowing nor looking directly at me. I was used to seeing that weariness in many people—the tired look in their eyes after they've made a decision that can't be washed away.

"Is something wrong?" I asked.

"Just tired," he said. His voice was flat, without complaint.

"Did you sleep?"

He was silent. "I slept. But I can't stop thinking about… how we count people."

I thought he was talking about numbers, thresholds, or percentages. He wasn't.

“What I can’t stop,” he said, “is the way they look at each other after the meeting. When they say ‘processed correctly,’ their eyes are completely different. As if they’ve just exchanged a debt.”

I didn’t answer immediately. I thought about the looks I’d seen: empty, focused, comfortable because they were framed. I thought about the times I’d signed, without trembling, because the name had been entered into the data box.

“Do you want to do something?” I asked.

He shook his head. “I don’t know. I just… can’t continue to let everything be numbers without anyone reminding me that behind the numbers is a name.”

“In other words, you want the system to ask more questions?” I prompted.

“No,” he replied. “The system will ask, then it will learn. I want some people… to remember faces. Not to stop the system, just… not to let things slide so smoothly that faces disappear.”

That intention had no place in operation. We added medical parameters; we installed human-in-the-loop; we patched and fine-tuned. But remember a human face? That's vague, pointless, no test kit.

He started doing things that, on paper, looked like professional failures: he arranged shifts to give night shift workers an extra hour off; he turned off a non-emergency alert to give medical time to check hands; he wrote in longer journals—a few lines describing the human condition in the area, instead of just "rates stable."

Every action was recorded as a deviation. Each deviation triggered a review process. The system categorized him as "specific"—a category for people whose behavior didn't quite conform to optimization. That category wasn't a clear punishment; it was a label, subtle, but impactful.

They called him in for a "talk." They didn't scold him. They observed him like a scientist examining a specimen. “Such behavior affects performance,” the logistics team said. “We’ll need you to adhere to the new standards.”

“You can’t be a number in that category,” he said. “I… I just want a few people to keep their memories.”

They offered a solution: adjust assignments; monitor closely; if things continued, suggest moving him from the core team to a position with less exposure to allocation decisions. Those words were like a door: a shift away from the operational core.

He didn’t object. He didn’t agree either. He bowed his head, signed a few lines on the screen—emotionless digital signatures—and left.

The day he left the team, some people made small notes. A technician, holding a glass of water, watched him go by and whispered, “He’s no longer suitable.” The word “no longer suitable” carried an echo: it was descriptive, judgmental, and melancholic.

The following week, there were other small actions. A mother in Zone D volunteered to stand guard at the nursery to receive extra compensation; a logistics worker stayed up all night to revise a rotation plan; some people began to avoid talking about names that had disappeared from reports. These things were lifesavers; they were also signs of a segment of the population unable to withstand the pace the system imposed.

The system, as usual, was emotionless. It received the data, categorized it, and weighed it. It flagged “behavioral fluctuations” and suggested increased monitoring. These measures reduced the deviation in the index. The figures turned green again. Production stabilized.

But what the data failed to record lay elsewhere. One evening, as I walked past the engineering area, I saw Huy sitting on an old computer case, looking out at the empty space. He held a small photograph in his hand—a man with a thin smile—and he whispered something. The sentence was too quiet. I didn't ask. I knew the answer before he said it: he remembered faces.

“Do you think what you’re doing is pointless?” I asked afterward, not wanting to press him for an answer.

He looked up. His eyes were red. “Not pointless. I just fear that one day, when we’re too refined, there will be no room for those who aren’t. Then they’ll tell us, ‘You don’t fit.’ And you’ll understand—you’re standing before a small exit.”

“What do you want?” I asked.

“I want someone to hold their hand before they leave,” he said. “Not to let them become numbers. That’s all.”

There was no better answer for him. I could only stare at the screen, at the gray symbols, the flickering, balanced strings of numbers. I thought of the phrase: A person who exists wrong. Perhaps Huy was the wrong person—not because he was ugly, but because he still clung to an old habit: assigning names while everyone was trying to translate them into data.

The next day, Huy's profile was updated: “Transferred—Offline equipment monitoring.” A job with little direct contact with the operational flow. A safe, efficient position. Huy grabbed his small bag and left the control room before dawn.

That evening, when I opened the log, there was a new entry: Personnel redistributed—operational risk reduction. No judgment. No explanation.

I turned off the screen.

Outside, the base was still breathing steadily. The green numbers blinked. And in a small place, someone was trying to memorize faces, as if keeping a piece of paper in a notebook where everyone had agreed to tear out a few pages.