"Spatiotemporal debugging" was an action that could very easily produce bugs.
It was even more prone to bugs than programmers writing code.
For example, this time, "spatiotemporal debugging" had theoretically moved things ten seconds into the past. Your memories and actions from ten seconds later should no longer exist.
That was the only way it conformed to the usual meaning of the "laws of time."
But doing that had a certain probability of causing a "spatiotemporal paradox," commonly known as the "grandfather paradox."
If you viewed time as a line and pulled the "Highgode" at the front ten seconds backward, where should the "Highgode consciousness" from ten seconds ago go?
It couldn't keep moving backward, could it?
According to quantum theory, although it was only ten seconds, theoretically, there could be an infinite number of "Highgodes" within those ten seconds.
Among that endless procession, if you suddenly made the "someone" at the very front cut in line, there was a high probability of triggering the "observer effect."
What if the "Highgode" at some point in time suddenly stood up and declared, "Are kings and nobles born to rule?"
Then things would get really interesting.
The spatiotemporal agents across the entire timeline would have to come over and clean up the mess.
Therefore, as far as the Time Administration's controlled weapons were concerned, their "spatiotemporal adjustment" was incomplete.
The timeline retreated, but consciousness did not.
In this way, the adjusted timeline was like a slipped knot.
The "retreated past node" was actually also the future of that same timeline.
This allowed them to avoid most of the bugs produced by spatiotemporal travel.
Thus, the supreme councilor of the Mierta clearly retained his memories of using the "Book of Coevolution."
The Mierta higher-ups present likewise remembered the scene of voting to use