Experimental Analysis: First Human Trial of Muscle Automation

"Continue?" Orochimaru raised an eyebrow, looking at Hiroki.

Hiroki took a deep breath. Instead of looking at the corpse lying on the ground, he walked straight toward the second one.

"Continue," he said.

Though Hiroki said this, his mind had already delved deep into the desktop within his brain, where he created a new log file: [Analysis of Failure Reasons for Human Experimentation on Automated Muscle Growth].

Subject: Analysis of the root cause of failure in the human experiment of Muscle_AutomatedGrowth_v0.1.bat.

Final Goal: Analyze the cause of the error, construct a corrective hypothesis, and design a v0.2 experimental protocol to achieve controllable, non-lethal muscle growth in humans.

1. Data Review and Root Cause Analysis:

At this point, Hiroki pondered for a moment.

When he experimented on the first human subject, he had used the script intended for mice—a script that had already reached equilibrium in mice. Yet, in less than a minute, the first human had died rapidly. This was even more extreme than the effects of the first script he had used on mice; at the very least, the mice had survived for seven days.

Where did the problem lie?

Hiroki frowned as he thought.

The mouse experiment had clearly been a success... If one were to talk about the difference between mice and humans, the biggest difference should be the matter of scale.

A small mouse weighs about 500 grams, while an adult human is nearly 70 kilograms.

This meant a weight difference of nearly 140 times, which further implied that in terms of the number of various muscles and cellular tissues in the body, mice and humans were not even on the same order of magnitude.

It was highly probable that this was why the script's effect on the human body was not a simple scaling up of the animal model, ultimately leading to the death of the first test subject.

Analyzing it this way, Hiroki slightly modified the code—

In his mind, the source file for Muscle_AutomatedGrowth_v0.1.bat was pulled up.

Hiroki's thoughts began to modify it rapidly.

The difference in scale led to a catastrophic amplification of resource requests; this was the most likely reason.

The current v0.1 script instruction was a global command that initiated a maximum-intensity resource request to every single cell in the "full-body muscle group list."

For a mouse, this might have been a load it could barely withstand; but for an adult human, this was likely an unbearable burden.

It was just like a Brain Overload Attack.

The so-called Brain Overload Attack was similar to the method Hiroki had previously developed.

Taking the criminal as an example, every muscle fiber and every cell in his body had sent a massive, useless stream of access requests (in this case, requests for things like "calcium ions") to a server (in this case, the body's blood circulation system) at the exact same time.

However, the calcium ions in the human body are limited, and the quantity might not be sufficient. Under the massive influx of simultaneous requests from countless cells, the calcium ions were depleted rapidly.

As mentioned earlier, an adult human weighs nearly 140 times that of a mouse, which also meant that when his script issued the same command, the number of cells in the human body needing to respond to that command was over a hundred times greater than in a mouse.

This was highly likely to cause an anomaly.

For example, taking calcium ion imbalance as an example, Hiroki managed to recall from his memory that the normal calcium ion content in human blood is approximately 8.6-10.2 mg/dL, while in a mouse, it is 8.40±1.09 mg/dL.

These amounts are quite close.

However... regarding the instantaneous resource demand (the calcium ions required by the script) under a global command:

An adult human has a total muscle mass of about 28 kilograms (28,000 grams). When synthesizing muscle growth, assuming each gram of muscle requires 0.1 milligrams of calcium ions to initiate, then under a global command, the human body's instantaneous total demand would reach as high as 2,800 milligrams.

Calculating at the same rate of 0.1 mg/g, the mouse's instantaneous total demand would be 22.5 milligrams.

At this point, according to the ratio, it seems they are not that different?

But what if we consider the difference in the proportion of blood volume?

A mouse (about 500g) has a total blood volume of about 32 milliliters, with a reserve of about 3.2 milligrams of calcium ions, which is 7 times less than the demand of 22.5 milligrams.

But a human (70kg) has a total blood volume of only 5,000 milliliters, and the demand in the human body (2,800 milligrams) is about 5.6 times the reserve (500 milligrams).

Although the deficit ratio seems slightly smaller than that of the mouse, in reality, the difference between the two actual demands is far too vast.

The mouse has a total deficit of 19.3 milligrams of calcium ions.

But the human is missing nearly 2,300 milligrams.

The difference in demand between the two is nearly a hundredfold! And in terms of actual demand, the human requires nearly 2,280 milligrams more calcium ions than the mouse! The absolute scale of such a deficiency is devastating and immediate.

And this is just an assumption.

Specifically for the human body, the exact amount of calcium ions needed to synthesize muscle is impossible to calculate precisely.

Therefore, Hiroki had to change the global command to a targeted application.

Hiroki's intent modified the code at high speed. He deleted the loop command that targeted the full-body muscle group list and replaced it with a mandatory input parameter: specify target muscle group.

In this way, the patch could be applied to strengthen only a portion of the muscle groups.

But this was still not enough.

Although Hiroki had killed a person on his first experiment, test subjects were limited after all, and Hiroki did not want to use more errors to cause his test subjects to continue dying.

And even if it were only targeted at one muscle group, 100% intensity was still an unknown risk. He continued to add new parameters, introducing a throttling control mechanism—a variable named growth intensity percentage, and forced the default value to a conservative level of only 5%.

This variable is used to limit the total amount of muscle growth per unit of time, in order to determine exactly what kind of numerical value would cause the human body to exhibit abnormalities.

Finally, after some thought, he first placed his hand on the criminal, and very quickly found the data he wanted amidst a pile of files: blood calcium, pH levels, calcium ion reserves, and other such information!

Immediately following this, Hiroki added the most important safety feature to the program. A parallel resource monitor, somewhat similar to the one Hiroki had written for himself to view CPU and memory usage in real-time, was used to monitor key physiological parameters like blood calcium and pH levels in real-time.

Once any indicator touched the preset safety threshold, the monitor would immediately lower the growth intensity or trigger an emergency shutdown. At the same time, a work/rest timer was also added, transforming the continuous high-pressure work into a periodic pattern.

Muscle_Sustainable_Growth_v0.2.bat, compilation complete.

Hiroki took a deep breath and began his second experiment; the man shuddered violently, his eyes filled with pleading terror. Hiroki ignored him.

There was no need to save a criminal; it was better for him to honestly serve as nourishment for his own growth.

In the silence of his thoughts, he issued the command: "Execute."

"Blood calcium levels are beginning to drop!" a researcher's voice suddenly turned tense, "A 3% drop... but compared to last time, it is relatively stable!"

"Lactic acid levels are fluctuating within the safe range," another person reported immediately after, "The subject's heart rate is elevated, but the rhythm is stable, with no abnormal beats appearing."

"It seems we... succeeded?" a researcher looked toward Hiroki.

Hiroki took a deep breath and slowly spoke:

"..."