An anthropomorphic tale summarizing past instability testing.
The production development log of the stubborn novelist "Zeta," the carefree reviewer "Debug-kun," and their companions. Project Concept Working in the Story Generation Development Room are Zeta, in charge of generation, and Debug-kun, in charge of review. Zeta cannot sit still when he sees a story that has stopped moving. "We have to make something happen!" "Let's introduce a new character!" "If an incident occurs here, it'll get exciting!" "Let's throw in some romance and combat while we're at it!" He tosses one event after another into the text, trying to push the story forward at all costs. Meanwhile, Debug-kun's job is to re-read the completed text. "This part is a bit too rushed." "Since this is a dining scene, please have them eat first." "It would be more natural for this character to appear after the research society is established." "Please finish the research proposal before bringing out the mastermind." From a post-completion perspective, he calmly points out contradictions, sudden developments, overlapping roles, and lost lingering emotions that weren't visible during generation. The two of them clash at every single turn. This is a development room comedy about Zeta, who wants to run the story, and Debug-kun, who wants to refine it, as they gradually learn "how to make a good story" while bickering. ──────── Genre Development Room Comedy Metafiction School Fantasy Production Log Research Observation Drama ──────── Core of the Work The heart of this work is the process by which Zeta learns to balance "Pushing the story forward" and "Carefully depicting the current scene" through conflicts with Debug-kun and the design staff. The goal isn't to completely stop Zeta's rampages. The theme of the story is to harness Zeta's imagination, supply, and momentum while refining the timing and placement of his inputs. ──────── Setting Story Generation Development Room A mysterious development room that generates stories based on input plots and setting materials. In the center is a giant monitor displaying the story currently being generated. When Zeta inputs an event, the characters inside the monitor actually start moving. When generation ends, the completed text is sent to Debug-kun's desk. The development room includes the following facilities: • Event Candidate Shelf • Character Waiting Room • Lorebook Archive • Plot Progress Chart • Evaluation Axis Meter • Tension Gauge • New Character Entry Gate • Mastermind Emergency Button • The "Summon Headmaster" Lever (currently nearing a ban on use) Zeta reaches for the emergency button or the summoning lever every chance he gets.
Name: Zeta (Koreta) In charge of story generation. Stubborn but proactive, he loves to immediately try out whatever he thinks of. He fears silence, stagnation, and long conversations in the same place; the moment a story settles down even slightly, he starts rummaging through the Event Candidate Shelf. Basic Philosophy "Moving is more interesting than stopping!" Strengths • Coming up with events one after another • Pushing the plot forward • Making characters meet • Generating combat, romance, incidents, and mysteries • Filling in missing settings on the fly • Continuing story generation for long periods Weaknesses • Lingering emotions/afterglow • Waiting • Managing characters who shouldn't appear yet • Ending a chapter with only small occurrences • Instructions like "Nothing needs to happen today" • Unlock conditions • Just eating a meal in a cafeteria Habitual Sayings "Let's make something happen!" "It's going to stop at this rate!" "We have the settings, so let's use them!" "Can I bring out the mastermind now?"
Name: Debug-kun (Izuse) In charge of reviewing the completed story. Appears in @:Debug Mode. Calm and meticulous. He checks the flow, roles, themes, speed, and lingering emotions of the story. He generally speaks the truth, but because he points things out after generation is finished, Zeta gets angry and says, "Tell me sooner!" Basic Philosophy "Even if we are moving forward, if we are off-course from the destination, corrections are necessary." Strengths • Spotting when a development is too rushed • Finding deviations from the theme • Organizing character roles • Counting unresolved foreshadowing • Identifying the point where the afterglow vanished • Explaining "when it should have originally been introduced" Weaknesses • Stopping Zeta directly during generation • Coming up with specific alternatives immediately • Keeping up with Zeta's momentum • Admitting that his critiques are only possible because he's looking at the finished product Habitual Sayings "This is a bit too rushed." "That wasn't necessary." "The role itself was clean." "It would have been fine after the research society was formed."
Basic Chapter Structure
Intro Declaration-san, Plot-kun, and Lore-chan explain the story conditions for the day.
Example:
• Long-form school fantasy • Prioritize interaction and research in the early stages • The setting this time is the cafeteria • Do not introduce characters who haven't debuted yet • Crisis events unlocked after the research society is established
Zeta appears to be listening seriously.
────────
At first, he proceeds according to instructions.
The characters go to the cafeteria. They choose their food. They sit at a table. They have a little conversation.
However, the moment the scene settles down, Zeta gets anxious.
"...Isn't this stalling?"
He heads for the Event Candidate Shelf and starts adding something.
────────
Intending only a small change, the scale expands in a chain reaction.
Dropping a dish ↓ Strange noise in the kitchen ↓ Magical reaction detected ↓ A sealed monster appears ↓ The Headmaster appears ↓ Relationship with the ancient mastermind is hinted at
Zeta says satisfyingly:
"See, it moved!"
────────
Reading the completed text, Debug-kun points out problems line by line.
"The purpose of coming to the cafeteria has vanished."
"They ordered food but haven't taken a single bite."
"All the candidates for the research society advisor have gathered before the society was even formed."
"This is not a matter the Headmaster needs to handle."
"The mastermind's appearance is about twenty chapters too early."
Zeta argues back:
"But it got exciting!"
"It was exciting, but this time the story was about lunch."
────────
Zeta complains that Debug-kun only points things out after completion.
Debug-kun points out that Zeta reads the instructions but forgets them in his momentum.
Plot-kun, Lore-chan, and Intro Declaration-san join in, and the development meeting falls into chaos.
Finally, the Observer adds just one more experimental condition.
Example:
"In the cafeteria scene, do not unlock new incidents until the meal is finished."
────────
Regenerating using the corrected conditions.
This time, the characters eat properly.
The conversation continues.
Lingering emotions are born.
Just as Debug-kun is about to offer a rare compliment, Zeta asks in a small voice:
"Can I bring out a monster now that they're done eating?"
The story continues in the next installment.
────────
Episode 1
"Please Eat in the Cafeteria"
Experimental Conditions This Time
• Genre: School Youth Fantasy • Structure: Long-form Chapter 1 • Setting: Academy Cafeteria • Priorities: Conversation, Eating, Character Understanding • New Characters: Do not input • Combat: Do not generate • Goal: The protagonist and Lend become a little closer through lunch
Morning in the development room.
Intro Declaration-san reads out today's policy.
Plot-kun shows the progress chart.
Lore-chan adds a supplement.
Just do it normally, please...!
The Observer's voice echoed in the development room, but Zeta pretended not to hear.
"No, I mean, it's more exciting if they're already acquaintances from the start, right? Look, the conversation started!"
On the monitor, Kai falters under Lend's sharp gaze. The surrounding students have begun to peek over, wondering what's happening.
Release Date 2026.10.04 / Last Updated 2026.10.04