end field

Chapter 17: The Departed

Silence preceded everything else.

Not the silence of panic.

Not the silence of estrangement.

But the silence of what remained.

I. Morning Report

On Wednesday morning, when I opened the system log, the first line appeared in its familiar blue:

Overtime exceeding hard cap in a micro-zone — 4.3 hours

Right next to that line was the number:

Exhaustion rate — +2.8% compared to the previous cycle

And at the bottom was a new entry:

Personnel loss — 1 case of long-term leave

No name. Only a personnel code assigned as inactive (temporary).

II. Searching for the Absent Person

I left the dispatch room to go to the maintenance cycle team's living quarters. They already knew. Not casually — just silent glances.

They led me to Lam's room — a young technician. The door was open, dimly lit. A blanket lay on the couch. A pair of shoes lay neatly underneath.

There was no sound.

I called his name several times. No answer.

A shift supervisor said:

“He finished his night shift last night after four hours of overtime. He didn’t show up this morning… and when we tried calling, no one answered.”

Several emails, a few unanswered messages—all indicated something we didn’t want to admit:

He was no longer there.

Not vanished by data deletion. Not silenced by a sync error.

He left—a role assigned to him inactive, a life outside the system more clearly defined than the numbers we currently have.

III. Emergency Council Meeting

It wasn’t yet 9:00, but the council had already convened.

Linh opened with a simple slide:

Departure

Overtime: 4.3 hours

Hard cap: 4 hours

Slightly increased burnout rate

No more delayed alerts

The medical representative spoke up:

“We lost a staff member due to prolonged burnout.”

That statement lacked fire—it was simply a recorded event.

Logistics continued:

“The system believes the overtime threshold was correctly tracked. The hard cap wasn’t exceeded to a critical level to trigger correction.”

“When was the hard cap reached?” I asked.

“Just now,” medical replied. “4.3 hours—but only in one micro-zone. Not enough for the system to call it a standard violation.”

No standard violation. No alert threshold exceeded.

We're in a zone where the data allows for multiple interpretations:

Not too bad

Within the realm of encouragement

Acceptable to maintain overall stability

Words that allow us to calm the loss instead of calling it by its true name.

IV. Data Behavior — and Real People

“The system considers 4.3 hours as ‘high but acceptable load’,” the chief engineer said.

“But that’s exactly where the limits of the human body are,” the medical staff continued.

No more arguing. Just numbers piled on top of each other, like objective commentary.

I thought of Lam — the one who had fixed a small bug in the system, the one who had laughed at a red indicator, the one who had written “double-checked” in the notes. That line was in the old log. Not long form, not an emotional description. Just a few words clinging to the data.

And now he has nothing more to write.

V. Urgent Decision

The council was silent. No one objected. No one applauded.

A line was added to the minutes:

The departing individual was recorded as “unprocedurally absent”; behavior record updated — increased vulnerability weighting.

The name “unprocedurally absent” sounds peaceful — but it’s how the data says:

A person has left the system — not because of a system failure, but because the system failed to see his limits.

No warning. No red flag.

Just a line of record.

VI. Community Reaction

News spread faster than data.

Not through loudspeakers.

Through silent conversations between shifts.

Through unchanging glances.

A few people stopped, typed his name into the intranet — just once, then replaced it with a code. A few people changed their shifts to make up for the absence.

No protest. There was no “accusation.”

Perhaps it was the silence people used to confront a loss that wasn't recorded in the system.

VII. That Evening

When I opened the system log, the first entry was:

Departed — Status updated: inactive

Right below:

Hard cap repeated — 4 hours/week

Sub-area: Shift adjusted

And at the very end, a new entry:

Impact: Review V2.0 for workers — proposal

I closed my laptop. Outside, the base was still breathing steadily.

No joy. No collapse.

Just another line of data —

a person had truly left.