Chapter 51: The - That Broke

Chapter 51: Chapter 51: The Chapter That Broke

Haruki returned to the manga because everything else had become too large. Kanzaki Holdings. Ghost Project. Hidden quests. Financial pressure. Takeda’s damaged trust. Opportunity loss. All of it remained, sitting exactly where he’d left it, and none of it helped him draw Page One.

So he opened Chapter Fourteen of Threadless Gate, shut every browser tab, put his phone in a drawer, and stared at Ren, Miyu, and Shiori standing inside a half-collapsed drainage tunnel beneath Tokyo. The manga world smelled of rust, sewage water, concrete dust, and fear — a lot easier to understand than industry politics, at least on the page.

Ren had just escaped the Bureau facility with Miyu. Shiori had betrayed her superiors to help them. Three fugitives stood under the city with no shelter, no plan, and no proof anyone would believe them if they surfaced. Haruki sketched Ren gripping the wall to stay upright, Miyu sitting on the wet floor smiling with cracked lips because freedom felt unreal after three years underground, Shiori checking a stolen Bureau tablet while rainwater dripped from her hair onto the screen.

For the first time in days, the story breathed. Not the career. Not the platform. The story itself.

He worked through the morning without checking numbers once. By noon, six pages existed. Good pages, the kind that made his chest loosen a little just looking at them.

Then his phone vibrated inside the drawer. He ignored it. It vibrated again. Ignored. The third vibration came with the emergency tone he’d assigned only to Yui and platform alerts, and that was the one that made him open the drawer.

Platform alert. His stomach tightened before he’d even read it.

Scheduled Chapter Processing Failed

He blinked. Chapter Thirteen. The Chapter that should have gone live twenty minutes ago.

He opened the dashboard. Red warning. Upload error. File corruption. Processing incomplete. The scheduled release had failed entirely, sitting there unfinished on the platform’s end while his phone had been buried in a drawer for four hours.

For several seconds his hands didn’t move. Then they moved too fast. He tried reuploading — failed. Tried the backup file — failed. Checked the file format — wrong export layer. He’d exported the draft version, not the final one. The actual final file existed somewhere in his folders, buried under six similarly named versions because he’d been too tired the night before to organize them properly.

His pulse started pounding. Comments appeared almost immediately.

No update?

Did the Chapter get delayed?

Author?

Five minutes later, the forum noticed. Ten minutes later, someone posted: Threadless Gate missed another update.

Another update. The words stung in a way none of the earlier attacks had managed, because this time the failure wasn’t pressure from enemies. It wasn’t money. It wasn’t a conspiracy sitting behind a corporate name. It was him. Bad file management, bad schedule control, bad professionalism, exactly the kind of mistake Kanzaki Holdings didn’t even need to manufacture.

He searched folder after folder. Chapter13_final. Chapter13_final2. Chapter13_REALfinal. Chapter13_upload. Chapter13_fixed. Every creator lie he’d ever told himself about being organized sat right there in his own directory, laughing at him.

At 12:48, Mizuno called. He answered while still searching.

"Tell me you have the file."

"I’m looking."

Her chair scraped through the speaker. "Haruki."

"I know."

"No. You clearly don’t." The sentence cut sharper than he expected, and he stopped typing entirely. Her voice stayed calm, but the warmth had gone out of it. "You are under extra scrutiny. Your growth is being slowed. Your finances are unstable. People are waiting for you to look unreliable."

"I know."

"Then why did you give them proof?"

No defense appeared. Nothing useful came to mind at all. Only the sound of rain hitting his balcony and his own breathing, uneven and embarrassed in equal measure.

Mizuno continued, quieter now. "Find the file. Upload it. Do not post excuses. A short apology after the Chapter goes live. Nothing else." The call ended — no encouragement, no lesson wrapped around it this time. Just work, laid out plainly.

He found the final file at 1:17, inside a folder labeled old backup of all things. He stared at it for half a second, furious at his past self, then uploaded it. The Chapter went live eighty-one minutes late.

Comments flooded in — some relieved, some joking, some irritated. Then the one he’d feared showed up.

This is the second update issue already. If the author can’t keep a schedule this early, that’s worrying.

The reply chain grew fast. Supporters defended him. Critics agreed with the concern. Neutral readers just watched it unfold. The Chapter itself performed well, which almost made everything worse — the content was strong, but the release failure consumed the conversation anyway. People discussed the mistake more than they discussed the story he’d actually spent the whole morning finally enjoying again.

He sat there watching the damage spread. Not huge damage. Not career-ending. Public damage. Visible, searchable, screenshotted somewhere already for later use. A stain on professionalism sitting right next to a genuinely strong Chapter, and nobody arguing about the Chapter anymore.

His phone buzzed. Yui. He didn’t answer — not because he was angry at her, but because he couldn’t handle kindness yet, not with the thread still open in another tab. A message appeared instead.

I’m not going to tell you it’s okay. But I’m coming after work. Eat before then.

He read it twice, then set the phone down beside the tablet and opened Chapter Fourteen again. Ren, Miyu, and Shiori waited in the drainage tunnel, soaked, exhausted, hunted by something they couldn’t fully see yet. For the first time, he actually envied them. At least their disaster was fictional. His was sitting on the front page of the discussion board with his real name attached to it.

The system appeared without sound.

[Public Reliability Failure Recorded]

Schedule Trust: Damaged Recovery Estimate: Minimum 12 Chapters of Consistent Delivery Recommended Action: Build workflow redundancy. Available Upgrade: Production Pipeline Manager Cost: 650 Creator Points Current Creator Points: 80

He laughed once. It came out ugly. The tool he actually needed cost more than eight times what he had sitting in his account. Of course it did — he’d spent nearly everything a Chapter earlier, back when he’d assumed narrative quality was the biggest risk facing him. Today had proven professionalism could take a creator down just as easily as bad writing could, and it didn’t care how good the pages underneath the mistake actually were.

Outside, rain thickened over Tokyo. Inside, Haruki reopened his folder system and started renaming files properly, one at a time. No inspiration struck him while he did it. No grand resolve arrived to make the task feel meaningful. No neat emotional victory waited at the end of the folder tree. Just embarrassment, a slow-burning kind of anger at himself, and a new spreadsheet titled Release Checklist that he built line by line while the rain kept going outside.

The mistake wouldn’t disappear just because he’d fixed the folders. Readers would remember it. Mizuno would remember it. Whatever remained of Kanzaki Holdings’ quiet pressure campaign would absolutely remember it, and use it the first chance they got.

Haruki knew all of that already, sitting there with the checklist half-built in front of him. He also knew Chapter Fourteen still needed to be finished regardless of any of it.

So he cleaned the mess one file at a time, while the public thread about his failure kept growing in another tab he refused to open again that night.