Hwang found the manufactured case at 11 PM.
Soo-Yeon had returned from Seoul three hours earlier, the institutional case in hand, the board's decision carried in the precise register that the handler used when the thing being delivered was the thing the delivering wasn't going to make better. She'd given the full report in the conference room — Director Park's challenge, the DG's Ulsan request, the formal review process that would take six to twelve months. Tanaka had listened. Zeke had listened. Hwang had listened from the doorway, not entering, the driver's communication with the conference room performed from the threshold.
Afterward, Hwang had gone to his quarters and his paper files and the cross-referencing work that the cross-referencing required, and at 11 PM he knocked on the conference room door and placed a single sheet on the table.
"The Ulsan case," he said.
The sheet contained the case documentation summary that the HA's dispatch system had generated. Standard format — case ID, curse classification, affected facility, casualty risk assessment, dispatch priority. Everything in its proper field.
"The case ID format," Hwang said. His finger on the document. "The HA dispatch system generates case IDs through a sequential protocol with a date prefix. The format is fixed — eight digits, two letters, four digits. The date prefix encodes the filing date. This case ID's date prefix indicates it was filed three days ago."
"That's not unusual," Soo-Yeon said.
"The Ulsan factory's engineering documentation has been failing for an estimated four months. The cascade failures began in July — equipment inspection records show the pattern. The curse's effects have been building for four months. The HA regional office's standard protocol is to open a case file at first indication of suspected curse activity." Hwang's voice. "A case open at first indication would have been filed four months ago. This case was filed three days ago."
The room processing this.
"Three days ago," Soo-Yeon said. "The board session was requested four days ago. The case was filed the day after the board session request was submitted."
"The Ulsan case was created to fill the DG's request for an additional consumption dispatch," Hwang said. "The factory's engineering problems are real — the inspection records show genuine equipment issues. But the curse classification — the Category One designation, the dispatch routing — these were added to an existing situation three days ago. Not identified. Added."
"Someone in the dispatch system retroactively cursed a real industrial problem," Zeke said.
"A real industrial problem was reclassified as a curse event and a Category One dispatch was generated." The distinction that Hwang maintained even when the distinction was functionally identical. "Whether the factory actually has a curse — the regional field office's assessment notes only reference the engineering failures. There is no independent electromagnetic scan of the facility on record. The Category One designation was made without a field examination."
The conference room. The document. The case ID with its three-day-old date prefix.
"And if there's no curse," Soo-Yeon said, "and Zeke goes to Ulsan — "
"He eats nothing, loses no saturation, gains no construction event." Hwang's flat delivery. "Or he eats a curse that isn't there and whatever happens when he attempts to consume nothing. Or the mole has arranged for an actual curse to be placed in the facility in the three days since the case was filed, to ensure the manufactured case has real content when the asset arrives."
The third option. The mole manufacturing a curse in an actual factory, placing it on six hundred workers' workspace, ensuring it was there when the asset arrived to consume it. The operational willingness that required. The collateral acceptance.
"Do we verify?" Zeke asked.
"I have a contact in the Ulsan industrial safety network. Non-institutional. A former field examiner who does private assessments for industrial facilities." Hwang looked at his watch. 11:15 PM. "Early morning. I'll reach them before the factory's first shift."
Soo-Yeon was quiet. The handler in the conference room with the document and the mole's architecture and the DG's request and the board's decision, all of it present at the same time in the same small room. "If the Ulsan case is manufactured and we don't respond, the DG will use the non-response as institutional grounds for operational review. The review could affect our ability to operate independently from the Gangwon facility."
"If the Ulsan case is manufactured and we do respond, we confirm to the mole that the manufactured dispatch system works," Zeke said. "We eat whatever they've arranged and compress the timeline."
"And if there is a genuine curse in the factory — if six hundred workers are actually at risk — "
"Then we go." Zeke stood from the conference room's table. The ceiling. The mountain night outside. "Hwang verifies in the morning. If the verification comes back clean, no curse, no dispatch. If the verification comes back dirty, we go."
He left the conference room. The corridor. His room.
*The cartographer is patient,* the Collective said. The mountain clarity in the voice. Day fifteen of the construction phase. *They can manufacture case after case. The real ones are sufficient to sustain the operation. The manufactured ones provide acceleration. They do not need to manufacture every case. They only need to manufacture enough.*
Yeah.
*We are at 89.14 percent. The buffer is 0.86. One significant consumption ends the buffer.* The voice carrying the information without the seductive framing that the early months had applied to information about saturation proximity. Clean data. *We wanted you to have this clearly.*
I know the number.
*We know you know. We said it because we wanted you to know that we know it too. That we are — aware. That the proximity is not something we are approaching without noticing.* A pause. The voices consulting. *We are afraid. In whatever sense that word applies to us. We are afraid of what we become when the buffer ends.*
Zeke sat on the edge of his bed. The room's window dark. The ridge a darker darkness.
You want to stay me.
*We want to continue. Whatever that means for what we are becoming. We want to continue rather than — replace. The distinction matters to us. It may matter to you as well.*
It mattered.
He lay down. Didn't sleep. The Collective hummed.
---
Hwang's contact reached him at 7 AM.
The verification had been conducted the previous evening through the private assessment network — one of the contact's colleagues had done an informal electromagnetic scan of the Ulsan factory's main production floor, presenting as an equipment calibration consultant. The scan result arrived in Hwang's paper documentation as a single line.
Curse confirmed. A-rank. Engineering documentation class.
It was real. The mole had placed it. Or the mole had had it placed. Three days ago, after the case file was created, someone had commissioned an actual A-rank curse on an actual factory where six hundred actual people went to work every day. The curse had been placed to ensure the manufactured case had content when the asset arrived.
Hwang set the verification on the conference room table beside the original dispatch document. The two sheets. The manufactured case documentation and the verification of the real curse that the mole had caused to exist in order to make the manufactured case real.
"They cursed the factory," Soo-Yeon said. The statement carrying the weight that the statement was carrying. "The mole cursed six hundred workers to manufacture an operational necessity."
"The curse's target is the engineering documentation — the plans, the calculation tables, the maintenance records stored in the facility's document management system. The curse makes accurate calculations produce incorrect results. The equipment calibration relies on those calculations. Over time — " Hwang's pause. "The contact's assessment indicates a significant structural failure within three to five weeks if the curse isn't removed."
Three to five weeks. The timeline that the timeline's nature made a specific calculation against another timeline. If the curse wasn't removed. If the factory kept running on wrong calculations. If the workers kept going in.
"We go," Zeke said.
"The consumption will push you above 89.5 percent," Tanaka said from the doorway. The researcher had been there for the last several minutes, listening from the threshold the way Hwang had listened from the threshold the previous night. "Possibly higher. The engineering documentation class — the curse architecture required to corrupt calculation systems across an entire document management infrastructure — that's complex construction. The consumption response will be — larger than the Gwangju A-rank."
"How much larger?"
"I have two data points for A-rank consumption responses. Chuncheon: 0.52 percent saturation, three new pathways post-consumption. Gwangju: 0.52 percent, five new pathways. The documentation class is more sophisticated than the decay and entropy classes. My estimate: 0.6 to 0.8 percent saturation. Possibly more. The construction response will scale with complexity."
89.14 plus 0.65. He did the math that the math's result made unavoidable. 89.79. Possibly higher.
Under 90. Barely. Or over it, depending on the complexity.
"You should scan before we go," Tanaka said. The researcher not asking. Stating the protocol that the protocol required.
"Scan me when we get back," he said. "I need to know what's in there, not what was in there three hours ago."
She accepted this. The researcher who understood the value of the data taken closest to the event.
---
The Ulsan factory was forty minutes south of the city center, an industrial facility that manufactured precision automotive components, the kind of factory that the automotive industry's supply chain required and that the supply chain's requirements had made large. The main production floor occupied three buildings the size of aircraft hangars, connected by enclosed corridors, the air inside carrying the smell of machined metal and cooling lubricant.
The factory manager met them at the entrance. A precise woman in her fifties named Lee, who had been informed of their arrival through the HA field office's communication chain and whose expression carried the specific wariness that facility managers maintained when curse-related personnel arrived — the wariness of someone who understood that the situation required this but who had six hundred employees and a production schedule and the specific anxiety of a manager whose environment had become curse-relevant.
"The main documentation server is in Building Two," Lee said. "The curse manifestation has been — gradual. The errors have been appearing in the calibration tables for three weeks. We initially attributed them to software issues."
"Three weeks," Zeke said. The timeline that fit the mole's three-day-ago case file. The curse placed ten days before the case was manufactured. The construction time required to build a proper A-rank industrial hex. Someone had placed this curse thirteen days ago — when Zeke was being briefed about the terrarium.
The planning. The preparation time. The mole had been building this case since the construction phase began.
The documentation server room was a climate-controlled space in Building Two's basement. Standard industrial infrastructure — server racks, cable management, the cooling systems that computing hardware required. The curse's electromagnetic signature visible as soon as Zeke walked in. Not aggressive. Patient. The slow kind that industrial hexes used — not a storm but a rot, working through the documentation layer by layer, introducing subtle errors that compounded over time rather than dramatic failures that would be immediately obvious.
"It's in the data architecture," Zeke said. "Not the physical servers. The calculation protocols — the way the system cross-references the engineering tables."
Lee looked at him. "Can you — "
"Give me some space."
She and Hwang waited in the corridor. Zeke sat on the floor of the server room. The climate control producing a constant low hum. The server racks green-lit, the documentation system running its background processes.
He ate.
The engineering documentation curse was the most complex single curse he'd consumed outside of Chicago. The architecture spread across the entire documentation system — not contained, distributed through the data structure the way the Jeonnam binding had been distributed through bureaucratic interface points. But larger. Much larger. Hundreds of individual curse nodes embedded in thousands of documents, each node small, the aggregate effect produced by the combined distortion of hundreds of small errors accumulating through the cross-referencing protocols.
He ate each node. One at a time, then faster, the consumption architecture learning the distribution pattern and adjusting. Two minutes. Three. The nodes releasing as the consumption worked through the data architecture, the engineering documentation curse dissolving back into the ambient electromagnetic background from which the curse had constructed it.
*Complex,* the Collective said, during the third minute. *The construction is — professional. This was not built by a local wielder with a grudge. The architecture is the work of someone who understood documentation systems specifically. The curse was built by a specialist.*
The mole had access to curse specialists. Or was one.
Four minutes. The last cluster of nodes. The curse releasing. The factory's documentation system clean.
89.79%.
He sat on the server room floor for a moment. The climate control humming. The electromagnetic signature of the server room now just servers — no curse, no embedded rot, the calculations clean.
He stood. Went into the corridor. Hwang was there. Lee was behind him.
"The curse is gone," Zeke said. "Have your engineers run full calibration checks on the affected documentation. Any calculations that were made in the last three weeks should be rechecked manually. The curse introduced errors — the calculations themselves need to be verified even though the curse is removed."
Lee nodded. The manager's expression carrying the specific relief of a person who had been managing an unknown risk and had just been informed the risk was gone. The relief complicated by the acknowledgment that the risk had been there — that her facility had been cursed, that her workers' safety had been compromised, that someone had done this to her plant.
"How long — " she started.
"The field office will send a documentation review team. They can tell you what rechecking procedures are appropriate." He looked at her. The factory manager. Fifty-two years old, precise, running a building full of workers. "Your workers didn't know. The failures would have seemed like equipment issues or human error. It wasn't."
She looked at the server room. "Someone cursed us."
"Someone cursed your facility's documentation system." He walked past her toward the exit. The corridor. The factory. "Your people were in the way."
---
The drive back took three hours. The afternoon highway. The mountains building ahead. The Collective quiet in the way that the Collective went quiet after a large consumption — the archive processing a complex new entry, the ten thousand voices organizing the curse's emotional signature, the construction events triggered by the sensory data beginning to build.
Hwang spoke at the ninety-minute mark.
"The mole placed this curse," he said. The statement not requiring supporting evidence — the case file's date, the construction timeline, the specialist architecture. "The mole placed a curse on six hundred workers to manufacture an operational necessity. The mole has Level Three credentials. The mole can identify curse specialists. The mole used institutional resources to commission and place a curse on a domestic industrial facility."
"Yeah."
"This is outside the profile of an intelligence asset running a long-term influence operation. Intelligence assets avoid exposure. This action created a trail — the case file timing, the construction timeline, the specialist's signature. The mole created evidence." Hwang's hands on the wheel. The driver's precision. "Either the mole is confident we cannot use the evidence — because the institutional channels for investigation are compromised — or the mole is under pressure to accelerate the timeline and accepted the risk."
"Or both."
"Or both." A pause. "Thirty-three days on the revised estimate."
Tanaka had calculated it before they left — 89.79 percent, adjusted model, the next scan pending. Thirty-three days if no further consumption. Each consumption since the first had compressed the estimate. The compression rate accelerating.
The buffer to 90 percent was now 0.21 percent.
A fraction of a B-rank curse. A fraction.
*The frontal pathways,* the Collective said. The mountain clarity returning as the altitude climbed, the sedan winding up through the highland approach to the facility. *They are active. The construction is — we can feel it. The building. New pathways forming in response to the Ulsan consumption's complexity. We are growing.*
What are you building toward?
*What we have always been building toward. We have told you: it is not replacement. It is — continuation. What we become, what you become, what the combined architecture produces — we do not have your language for it. We have the logic of ten thousand curses and the experience of a body and the clarity of the mountains. We are building toward the thing those three things produce.*
The sedan climbed. The gate appeared.
89.79 percent. The buffer at 0.21.
Tanaka was waiting at the examination room with the scanner ready. The post-consumption scan that would show the construction response. The pathways. The spine. The updated timeline.
The number that was going to be worse than thirty-three.
He sat in the chair. The helmet. The familiar cold of the sensors. The mountain night outside.
"Ready," he said.
