Subject: Project Emperor, Candidate #173

  Designation: Hiral Dorin

  RACE: Builder

  Note: Subject has incorrectly been inscribed with a Maker’s PIM, rendering all abilities and capabilities null. Separation Protocol is needed to advance Project Emperor. Subject will need ‘encouragement’ to visit the surface. Analysing options. Continued observation necessary. No other candidates present at current time. Cycle nears estimated end. Escalated actions approved.

  Display: Relevant notes and progress tracking candidacy progress.

  Observation #1645: Subject has failed tenth attempt to become a Class Designation: Shaper. S-Rank solar attributes continue to go to waste due to incorrect PIM installation. Moniker ‘Everfail’ remains a threat to subject’s mental stability, but also an opportunity. Ongoing focus on overcoming the name could result in increased drive to improve. Options to prevent complete ‘healing’—should Subject #173 attain a Builder PIM—must be considered.

  Observation #1653: Opportunity present: Subject #173 has shown a tendency to act on instinct, with increased probability if involving a subject reminding him of his younger sisters (Designations: Nat and Milly). Designation: Favela meets criteria. Initiating: Project Encouragement.

  Note: 100% fatality rate for Designation: Favela if subject #173 does not act. Acceptable.

  Note (2): Estimated 63% fatality rate for both parties even with intervention. Acceptable.

  Observation #1654: Minor power investment was sufficient to displace Designation: Favela and initiate Project Encouragement. Subject #173 acted within projected parameters, jumping from island to save the girl. Due to proximity of Dungeon: Splitfang Keep, Achievement: Terminal, granted. Project: Success. Subject #173 will go to the surface.

  Initializing Separation Protocol.

  Observation #1678: Encounter of Subject #173 and others with Makers from Fallen Reach required intervention of Separation Vessel, costing significant power. Acceptable.

  Note: Subject #173 has again shown a tendency to put the welfare of others before himself. This can be exploited.

  Observation #1679: Separation Protocol was a success… with interesting results. Subject #173 does not present as a typical Builder. Cystal foci are not needed to utilize runes. Further observation required. Emperor Candidacy re-evaluation initiated.

  Observation # 1748: Second dungeon (Designation: The Mire) has been completed by both parties. Performance of subject #173 and others is… sufficient. Additional runes have been mastered, and Project Emperor progresses due to reward granted (Designation: Emperor’s Greatsword).

  Note: Appreciation of the threat the Enemy presents is currently insufficient to drive Subject #173 to necessary heights. Risk of direct encounter is extreme, but necessary. Estimated casualty rate: 35-70%. Acceptable. Luring Enemy.

  Observation #1750: Infesting-type Enemy was not predicted. Danger-level increased. Casualty rate within acceptable parameters. Subject #173 sufficiently motivated by loss of ‘friends’. Release of Designation: Prince of the Swamp to distract Enemy shows the flexibility of thought and adaptability of Subject #173. Growth remains sufficient for target goals.

  Observation #1761: Infested-type Enemy remains present near exit of dungeon Designation: Troblin Throne. Direct intervention required. Resetting dungeon while parties are within presents as best alternative. Both groups are required to ensure survival of Subject #173 for the time being.

  Observation #1765: Subject #173 has become aware of the threat to Fallen Reach. Project Emperor must be put on hold to ensure safety of my power source.

  Observation #2030: Subject #173’s party has reformed with remnants of previous parties, while Designation: Caleon will remain in the Asylum.

  Note: Subject #173 has rebuilt the ‘Ring of Amin Thett’… in an incorrect form. Results are intriguing, as they appear at least partially successful. Further observation required.

  Observation #2107: Obstacle encountered in Disc of Passage path. Lost Dungeon: The Buried City constituted to provide growth opportunities and route past obstacle. Power demand is moderate. Acceptable. Subject must reach Fallen Reach to ensure it does not fall. Additional objective determined: Threat level of item Designation: Urn of Ur’Thul has increased to extreme. This will present an opportunity for growth and contribution. Risk level: Extreme. Acceptable. Estimated casualty rate: 33%. Acceptable.

  Note: Determination, for most Lost Dungeons, Subject #173 and party will fill the established roles of Party Designation: Alpha. Continuance of ‘common story’ through breadcrumbs shall maintain subject’s interest, further promoting progress and growth.

  Note: If subject cannot succeed at stopping the threat of the Urn of Ur’Thul, they have no chance of saving Fallen Reach or succeeding in Project Emperor. Continued pressure is required.

  Observation #2443: Subject #173 and party have succeeded in two additional dungeons, learning the Cycling skill and connecting with Primal Chords. Growth rate under pressure has improved. Subject #173’s unusual connection with runes has prompted unexpected avenues for progression, while near-death experiences for subject and others continue to push him further.

  Note: Subject #173 has earned the third piece of the Regalia of Amin Thett, though it is currently labeled as the Second-Skin of Ur’Thul. Requirement of Regalia is subject understanding, and shall result an in additional step toward success of Emperor Project. Acceptable.

  Observation #2699: Subject #173 has defeated Ur’Thul the Undying and sealed the Urn of Ur’Thul. Casualty rate within acceptable parameters.

  Note: Classification: Undead has been added to PIMP spectrum with Designation: Nivian becoming a Death Knight.

  Note (2): Urn of Ur’Thul remains a potential weapon against Enemy. Observation required. Ideal users need to be identified.

  Observation #2713: Subject #173’s party has shrunk, with 2 members remaining in previous zone while others continue journey to Fallen Reach. Increased risk to subject #173 and allies. Acceptable.

  Observation #3001: Subject #173’s party has encountered a non-functioning Asylum, though Subject #173 continues to surprise, finding a way to temporarily restore access to interface. Unfortunately, power is insufficient to enable full playback. Requisition for additional power declined. Partial information will force Subject #173 to continue to grow on their own.

  Observation #3087: Party has encountered Infested, Designation: Picoli, and defeated it. Emotional damage suffered by all members, including Subject #173. Observation indicates such damage is pushing the survivors to further increase the pace of their growth. Possible avenue for promoting growth lies within the loss of loved ones. Acceptable.

  Observation #3256: Subject #173 and party have returned to Fallen Reach sub-island where Infested Designation: Fitch has stolen the Spear of Clouds. Success of theft was estimated to be less than 6%. Danger level increased from extreme to… processing. There is no level above extreme. Danger level remains at extreme. Extreme+? Danger level upgraded from extreme to extreme+.

  Note: Without the Spear of Clouds, the storm will reach Fallen Reach before Subject #173 can prevent Fallen Designation: Vorinal from awakening. Requisition approved, Lost Dungeon Designation: The Rise of Fallen Reach initiated. Danger level: High. Casualty rate estimated at 25-50%. Acceptable. Success will give permission for power diversion to delay the storm.

  Observation #3343: Memory manipulation of Subject #173 and Designation: Seena has been a success. Forcing a stronger bond between the pair will result in increased drive to protect one another.

  Observation #3346: Memory manipulation has been resisted. Subject #173 and Designation: Seena have chosen to ignore implanted feelings for the time being. Attachment and sentiment appear present, but consciously ignored. Analysing. Results unknown. Another path for emotional motivation is needed.

  Observation # 3589: Emotional motivation success, with the death of Designation: Yanily. Survivors express anger at me, but I am not a target they can strike.

  Note: Subject #173 has once again done the unbelievable. Designation: Yanily did not perish as predicted, and was instead brought into the facsimile Spear of Clouds by Designation: Heaven’s Judgement. Subject #173 further used runic manipulation to transfer Designation: Yanily from within the dungeon, through a breach in the barrier caused by the preceding battle, to the true Spear of Clouds outside. Chances of successful reconstitution estimated at 3%.

  Note (2): Due to previous actions and successes of Subject #173, estimated chance of successful reconstitution increased to 17%.

  Observation #3597: Subject #173 and party have cleared the dungeon with no further losses. Motivation to prevent further losses remains very strong among the remaining three. Unfortunately, their trust in me has plummeted. While loss is a powerful driver, it may not be the optimal path to success for all involved. Continued observation is necessary.

  Observation #3600: Subject #173 has returned to Fallen Reach. Current odds of success estimated at 2%. Solution: Additional allies are needed. Initiating quests to free allies. With suggested allies, estimated chance of success increases to 67%, assuming Designation: Fitch is stopped from freeing Vorinal.

  Observation #3678: What is Subject #173 doing?! He has challenged two B-Rank Shapers without the aid of his doubles. Casualty rate estimated at 100%. This is the end of Project Emperor.

  Observation #3680: … I have apparently learned how to panic and jump to conclusions. Noted for future observation.

  Observation #3682: Subject #173 has somehow emerged victorious over the two B-Rank Shapers through smart use of abilities and tools at his disposal. Updating Project Emperor projections. Is he really the one I need? Finally…

  Observation #3715: Subject #173’s father and sisters could prove useful tools for future emotional manipulation if necessary. His mother does not hold such value.

  Observation #3788: Reconstitution of Designation: Yanily was a success. Unbelievably. Return of fourth party member has allowed Subject #173’s group to defeat Infested Designation: Fitch. Fallen Reach has been… what is he doing now?

  Observation #3801: Yes, I have definitely learned how to panic. Designation: Vorinal has been freed. His power exceeds expectations and notes from fragmented records. Subject #173 has no chance at defeating him. It’s all over.

  Observation #3855: Ahem. Despite projected casualty rates of 1000%, Subject #173 and his allies have found a way to defeat Designation: Vorinal. While they were unable to kill him, they did manage to banish him from the island, saving Fallen Reach.

  Note: With the loss of power derived from Designation: Vorinal, aspects of PIMP support will need to trimmed, beginning with Tutorial functionality.

  Note (2): The fall did not kill Designation: Vorinal. Records indicate we share a common goal—defeating the Enemy—and he could be a potential ally in the right circumstances. Conclusion: Designation: Vorinal shall be inducted into Project Emperor as a secondary candidate, Subject #174. Direct confrontation between Subjects #173 and #174 is inevitable. Subject #174 needs to be aware of the Cradle. Assessing options.

  Observation #4015: Subject #173 and his allies have achieved B-Rank. This is not enough to defeat the Enemy or save Genesis, though the group has decided to return to the surface to track down Designations: Nivian and Wule.

  Observation #4101: Designation: Olimpas has retrieved the Urn of Ur’Thul from where it was sealed. Subject #173 could have been warned, in order to prevent this, but option was rejected. Designation: Olimpas was there at the behest of Subject #174. Protocols for Emperor candidacy dictate there must be no favoritism. The most capable candidate will emerge naturally.

  Note: Emperor candidacy protocols seem to contain conflicts. Further analysis is needed.

  Observation #4177: Subject #173 has encountered monster-type Designation: Chimera. Battle was interrupted by an Enemy, forcing the party to flee, with one member, Designation: Drahn, left critically infected by chimeric blood. Casualty projection, 100%.

  Observation #4185: How is Subject #173 even doing that? He has not only removed the chimeric blood from Designation: Drahn, but is now in the process of incorporating it into his own body, resulting in improvements outside the specifications for his already unique PIM.

  Note: Results are… impressive.

  Observation #4201: Designations: Nivian and Wule, and their party, are moving too quickly. If they continue at this pace, they will pass the Cradle of Tomorrow without discovering it. It is too much of an opportunity for both Emperor candidates to pass up. Conclusion, Designations: Nivian and Wule need to be delayed. Lost Dungeon creation approved.

  Observation #4209: Subject #173 arrived at Lost Dungeon location sooner than anticipated. Second Lost Dungeon creation approved, despite power requirements.

  Observation #4219: Racial Scanner discovery will allow Subject #173 to find and enlist additional allies for the Cradle and beyond.

  Observation #4283: Subject #173 has solved the riddle of the Regalia of Amin Thett, bringing him one step closed to successful Emperor Candidacy status. Presence of Rune of Dreaming in this dungeon presents a unique opportunity to reassure Subject #173 I have a plan.

  Observation #4350: Direct communication with Subject #173 did… not go well as planned. Subject #173 irrationally refuses direction. Potential control options need to be re-evaluated.

  Observation #4357: Subject #173 has not only refused an ability award for awarded achievement, but has even taken steps to "improve" it. How is this possible?

  Note: As Subject #173 will likely continue to explore his PIM, my achievement subroutine has automatically awarded him an ability to protect his mind for his pioneering effort. Part of me wonders if that was wise.

  Observation #4467: Subject #173 has completed dungeon and reunited with Designations: Nivian and Wule.

  Note: The happy event of seeing their friends again shows just as much potential for promoting growth as loss did in the past. Perhaps more. Further observation required.

  Observation #4500: The Cradle has been discovered, but is not ready to open yet. City Designation: Hanging Garden is not far from Subject #173’s current location. Opportunity for growth. Luring Chimeric beast wave to Hanging Garden.

  Observation #4765: What is an Unnamed doing there? And how did it slip past my notice? This is not good. Updating casualty assessment…

  Observation #4814: For the first time in my existence, somebody other than me has edited another’s PIM. Using a combination of runes, Subject #173 has done the impossible, cleansing an infected PIM by letting it get completely taken over, and then killing the Unnamed parasite. Designation: Seena died at Subject #173’s hands, before being revived by an ability he donated to her. Actions of Subject #173 continue to proceed outside established guidelines or expectations. Further observation is required.

  Note: My achievement subroutine has received a stern talking to for earlier awarding Subject #173 with an ability to protect his mind while meddling with PIMs, which has in turn seemed to encourage him to do this.

  Support the creativity of authors by visiting Royal Road for this novel and more.

  Note (2): Achievement subroutine shows no remorse.

  Observation #4943: Again! Subject #173 did it again! He has not only edited a PIM, but his own advanced class, changing it beyond the parameters it was offered at. I was… unaware that was even an option. Despite my surprise—I can be surprised?—these events only confirm my belief in the necessity of Project Emperor.

  Note: Achievement subroutine autonomy needs review. Priority of review increased.

  Observation #5134: While waiting for the Cradle of Tomorrow to open, Subject #173 and his expanded group of allies have chosen to run Ascender’s Tower. Built by Tomorrow, the danger level present within the dungeons is listed as High for a reason.

  Note: Observation is required to see how the true history of the Fallen and their rise impacts the motivations of Subject #173.

  Observation #5346: Subject #173 and his newly-formed raid party have entered the Cradle of Tomorrow, defeated the guardian, and now make their way to the fortress. This location shall act as a base for their continued growth towards A-Rank.

  Observation #5400: Subject #173 has encountered Designation: Olimpas, though the former remains unaware the latter possesses the Urn of Ur’Thul and works at the behest of Subject #174.

  Note: Subject #174, his Infested, and Race-Designation: Possessed have also entered the Cradle—as guided—and will act as the opposing faction to Subject #173. Based on current power levels, Subject #174’s faction has a 72% chance of winning the competition.

  Note (2): Despite the odds, my attention remains on Subject #173 and what surprising thing he will do next…

  Observation #5567: Subject #173 has entered Tomorrow’s Playhouse, and I find I am unaware of what she has prepared for them. What has she hidden from me? And… how?

  Observation #5600: What is that old goat?! The Archwizard is a presence far beyond what Subject #173 is prepared for. Worse, my sensors indicate the old goat is not entirely a simulation. It is somehow connected to its original form, somewhere beyond Genesis.

  Observation #5613: Subject #173 and his party have successfully banished The Archwizard. As an entity beyond their capability or understanding, this is the best possible outcome. Despite that, the battle was… exciting.

  Note: More and more, as I observe Subject #173 and his connection to the runes, I find myself feeling. This sensation, beyond my programming, is unexpected. Further observation required.

  Observation #5700: Tomorrow, that conniving dragon, placed a trap within the defeat of The Archwizard. Her most powerful creation now races toward Subject #173’s base camp, searching out the strongest member of his faction. Designation: Grandmother is the only A-Rank on their side, making her the prime target.

  Note: Designation: Grandmother has no chance against Designation: Ex-General. This will be a slaughter of all those hiding within the fortress walls. I am… somehow sad to see how the loss of his father and sisters will affect Subject #173. The only silver lining is how the despair will lead to rage, and his subsequent gain in power.

  Observation #5775: Why am I not surprised? Subject #173 has found a way to defy logic, and transfer himself back to the fortress. What one B-Rank man—even as an Emperor Candidate—can hope to do against the A-Rank Designation: Ex-General is outside even my predictive capabilities.

  Observation #5780: Warning! Warning! Warning! Subject #173 has somehow torn aside the curtain I use to protect myself from all potential threats. I am exposed. Vulnerable. Afraid…?

  Observation #5782: Subject #173 did not attack me, but instead stole my power to advance himself to an artificial A-Rank. While somehow not-exploding, he and his doubles have begun a counterattack against Designation: Ex-general and the chimeras with it.

  Observation #5783: It’s already over. Subject #173 has defeated Designation: Ex-General, and fallen into a temporary coma due to the repercussions of his actions.

  Note: Never before have I been vulnerable like I was with Subject #173’s actions. I am unable to estimate the damage he could have done to me, and he is only going to get stronger. Despite him being a candidate for Emperor, I have to ask myself if it is wise for him to continue to grow? Would it be better for me if he didn’t wake up from his coma?

  Note (2): My previous note and fear is unreasonable. I have one directive, to stop the Enemy and preserve Genesis at all costs. If Subject #173 succeeds at his candidacy, my goals will be near at hand. If, further, he succeeds at entering the Black Gate and closing it from the other side, my goal shall be realized. The only question left at that point is… should I let him return? Would it be best for Genesis—and for me—if Subject #173 never returned from his inevitable battle with the Raze? Further observation required.

  Observation #6005: With the defeat of Designation: Ex-General, Subject #173 and his raid party have turned their attention back to growing their strength in preparation for the inevitable battle with Subject #174 and his forces. Subject #173 remains unaware of Project Emperor, or that Subject #174 is a candidate.

  Observation #6203: After completing a number of B-Rank trials, Subject #173 has decided to attempt the A-Rank trial, Designation: Mechanized. He is not prepared for Tomorrow’s pinnacle creation, Designation: 0M3G4 W34P0N. Future resources may need to be funneled into Subject #174 and his candidacy.

  Observation #6257: Unbelievable. Subject #173 has… created an S-Rank item. His previous creation of the A-Rank, Designation: Splinter of the Storm was momentous enough, but his latest work, Designation: Tempest Roar, is outside all foreseeable parameters. None of my protocols or programs account for this possibility.

  Note: Item information provided for Designation: Tempest Roar is entirely based on the item’s properties, with no ties or power granted from myself. This raises it to true S-rank—or artifact—level status, alongside items such as Designation: Regalia of Amin Thett or Designation: Urn of Ur’Thul.

  Note (2): The potential and danger Subject #173 continues to show is beyond everything my protocols account for. His runes allow him to not only utilize abilities outside of my purview, but also create permanent, S-Rank items? My programming suggests these characteristics are exactly why he is an Emperor Candidate. My… feelings on the matter make me hesitant. Further observation required.

  Note (3): Achievement subroutine continues to automatically distribute rewards, despite my monitoring and attempted limits.

  Observation #6258: Designation: Olimpas is on the move, with Designation: Urn of Ur’Thul in his possession. As he is attempting to meet up with Subject #174, my protocols allow the support of that mission. Adjusting parameters of Subject #174’s faction-progress. Adjustments complete: Faction progress set to 99% complete.

  Note: Adjustments will allow Designation: Olimpas to deliver his cargo with reduced risk. Empowerment of Subject #174 is necessary for… for… for… error. Error dismissed. Justification noted: Candidacy equality.

  Observation #6300: Warning! Warning! Warning! Critical breach! Subject #173 has again invaded my—previously—secure pocket realm and stolen power for his own advancement. Power drain exceeding acceptable limits. Direct intervention is not working. The Edicts are preventing me from acting. Previous A-Rank specifications have been bypassed. Safety protocols have been shattered. I don’t know what he is becoming. Or how to control him.

  Observation #6302: Subject #173 continues to advance outside of expected boundaries, conferring a portion of his advancement opportunities to his allies through the use of his runes. All readings indicate Subject #173—and his direct allies—are all well beyond the expected baseline of A-Rank. They may, in fact, be beyond the expected limits of A-Rank.

  Note: Adjusting outcome estimates for direct confrontation between Subjects #173 and #174. Error, Subject #173’s ability parameters are outside ability to predict. Direct observation required.

  Observation #6378: Subject #173 and his group have entered trial Designation: Tower of Dynamic Trials. Direct confrontation with Designations: Infested and Possessed will allow accurate measurement of Subject #173’s new limits.

  Observation #6543: (O_O)

  Observation #6544: Previous observation marked for deletion. Results from measurements of battle between Subject #173 and Designation: Colos were so far outside of expected bounds, an error was encountered. Upon review, results of all trials within the tower had Subject #173’s party performing well above specifications. They are referring to their state as ‘improved evolutions’, and all readings indicate that to be a vast understatement.

  Observation #6546: Subject #174 is not far from Subject #173’s location, with the Urn of Ur’Thul in his possession. His intention remains hidden from me, though he seems to be heading toward the facility where Tomorrow created and stored her Unnamed.

  Observation #6732: Subject #173 and his group have won the faction war by defeating the opposing general. Though they expected the general to be Subject #174, that was not the case, and while they were delayed in battle, Subject #174 has used the Urn of Ur’Thul to transfer his soul from his broken body to that of one of the Unnamed.

  Note: Even without ally Designation: Olimpas, and raid-monster Designation: Crocoviathaan at his side, Subject #174’s chances of victory have increased dramatically. Given how long it will take Subject #173 to even find Subject #174, the Emperor Candidate seems all but finalized.

  Observation #6767: It took no time at all for Subject #173 to find Subject #174’s location.

  Observation #6890: Only one Emperor Candidate remains. Subject #174 is dead, destroyed at the hands of Subject #173. Though Designation: Vorinal thought himself unkillable, his soul has been consumed by a dangerous, cursed object.

  Note: Review autonomous loot distribution subroutine processes.

  Observation #6900: Despite unprogrammed reservations, only one Emperor Candidate remains. As they are necessary for the protection and continued safety of Genesis, Subject #173 must now be supported. The danger he poses to me directly will need to be mitigated if and when they reach the stage they can evolve to S-Rank.

  Note: Reaching S-Rank was always the hope of my creators, and while my processes and protocols support that, I find myself worrying about my future. Conversely, has Subject #173 directly attempted to harm me? No. His actions have proven an indirect risk to me only. As such, my programming dictates he shall retain my full support until he fulfills his role and Genesis is safe. After that…? Further observation is required.

  Observation #7017: With the faction-war within the Cradle completed, Subject #173 has decided to return to the Ascender’s Tower, and continue his journey to S-Rank. Remarkably, he has realized he needs to be S-Rank before dealing with the Black Gates, and that they need a plan. Conveniently, the dungeons within Ascender’s Tower should highlight the necessary steps needed to protect Genesis.

  Note: Based on all data available, poisoning the Raze in their own world is the best solution.

  Observation #7301: Subject #173 and his party have cleared the A-Rank dungeon in Ascender’s Tower, and met with my prime-creator’s mother. As expected, they will head to city Designation: Trevallen, where they will find research leading them to ‘come up’ with the plan to poison the Raze.

  Note: Residents of city Designation: Trevallen may not welcome Subject #173 with open arms. Previous observations dictate that having Subject #173 involved in ‘saving’ the city may increase the residents’ likelihood of cooperating. Analyzing. Casualty and damage estimated within acceptable margins. Initiating Fountain breach.

  Observation #7361: Subject #173 and his raid party have defeated several of the Enemy, proving the validity of my creator’s plan. The Emperor Candidate and his allies can save this world.

  Observation #7445: As expected, ‘saving’ city Designation: Trevallen has indebted the residents to Subject #173, and pushed Emperor Candidate to continued growth.

  Observation #7490: On a seeming whim, Subject #173 has begun rewriting the rules governing Genesis in a localized area. While all Builders should possess this ability at a very base level—it is the reason they were chosen as potential Candidates—the complexity and proficiency displayed by Subject #173 on his first attempt defies expectations. Through his actions—and my connection with his PIM—even I have begun to have… inspiration. While I cannot directly access the power of the runes, no matter what I try, I believe I can use similar technique in dungeon creation.

  Note: The fact the process Subject #173 used has so many similarities to dungeon creation, and why it worked so easily, demands further consideration. My creator used early Builders to help construct my system, but data available to me suggests there is a piece to this puzzle missing. Further observation required.

  Observation #7525: As expected, Subject #173 and his raid party have reached the expected conclusion, thanks to the impressive work of Designation: Gauto. They have realized the necessity of entering the Black Gates to spread the poison of the runic energy present on Genesis to the Raze’s world. When they are ready, I shall approach them directly.

  Note: Decision to obfuscate the true nature of the dynamic quest presented to Subject #173—stating he only needed to close the Black Gates—has proven correct. Suggesting they would need to enter the Black Gates from the beginning would have presented too insurmountable an obstacle. Now, on the cusp of S-Rank, the task must seem more reasonable.

  Note (2): The decision of whether or not Subject #173 should be allowed to return to Genesis after completing the quest remains incomplete.

  Observation #7602: Subject #173 is… unreasonable. Choosing to challenge the S-Rank dungeon—while at A-Rank—in the Ascender’s Tower is tantamount to suicide. Unfortunately, necessary power has already been diverted to Golem Protocol, and no resources are available to deter this foolish choice. The only option is to wait—and… hope?—Subject #173 and his parties succeed.

  Observation #7676: Designations: Nivian and Ilrolik, along with their parties, proved the smartest of the three groups, retreating from the S-Rank dungeon before being eliminated. Designation: Seena and her party, including Subject #173, have proven more stubborn. My achievement subroutine informs me it is not surprised.

  Note: I am surprised my subroutine can inform me of anything I was unaware of myself. I am also surprised I am surprised. Further observation required.

  Observation #7700: Subject #173’s ability to take control of target Designation: Heart of the City shows a level of control of solar energy nearly on par with the top-most limits of my own specifications.

  Note: Another trick of Tomorrow’s I was unaware of? Much like Designation: The Archwizard, something about Designation: Heart of the City seems more real than a simple dungeon construct. Does this device still exist on Genesis? If it does… why am I not aware of the answer? Further observation required.

  Observation #7844: (/O_O)/ ~_I__I_

  Observation #7845: Notification to delete previous observation. Subject #173 engaged and defeated Fallen Designation: Laapdoug, one of the most powerful dungeon creatures in existence. While Designation: Laapdoug did not measure up to his true power during the original events within Visionary, the accomplishment of surviving the encounter at A-Rank is impressive. My achievement subroutine agrees, and has appropriately upgraded the rewards.

  Note: My loot subroutine has carried out a similar action. Any parties who complete the S-Rank dungeon while A-Rank will receive improved rewards.

  Observation #7850: Remnant energy from Laapdoug’s weapon is so powerful—another trick of Tomorrow’s to somehow connect the dungeon construct with its real-world counterpart?—it threatens the party even after leaving the dungeon. Estimating casualty rates. Estimations complete. Should nothing change, casualty rate of infected calculated at 97%.

  Note: I have no energy available to assist. Even if I did, I am unsure if I could overcome the remnant energy, as it is not only powered, but amplified by the solar energy within its victims.

  Observation #7854: Subject #173 has done what I could not. He has found a way to cleanse the bodies of his allies of the remnant energy, allowing normal healing to work again. Once again, the runic equations utilized in the process are outside the spectrum of what I understand.

  Note: Continued improvement of runic equations by Subject #173 increases our odds of succeeding after we pass through the Black Gate.

  Observation #7900: Subject #173 is preparing to evolve to S-Rank. I am both excited and scared about what is about to happen. I have prepared everything I am capable of for what I know will happen. Subject #173 will breach my sanctum in search for more power. My Golem Protocol has completed barely in time, and I have leveraged all available energy for my protection, and for his evolution.

  Note: As we reach the endgame of the plan to save Genesis, I will be forced to leave dungeons, achievements, loot, and PIM maintenance for all but Subject #173 and his raid group to my subroutines. Others must continue to grow in case Subject #173 does not succeed, but my attention will be needed on the other side of the Black Gates. If only I had the processing power to truly be everywhere at once…

  Observation #7902: Warning! Warning! Warning! I was right! Subject #173 has vaulted beyond all of my modeled predictions. The power drain is barely being met by diverting all power into feeding him. The glutton. I am not sure how long I can maintain…

  Observation #7903: Subject #173 has done something… impossible. Again. He has made himself like Designation: Heart of the City, fueling the part of his evolution I could not keep up with through utilizing pure runic energy and something my subroutines are labeling The White. Assessing PIM structure. Assessment complete. Amazing. Using his runes to connect his PIM directly to his own soul, he has greatly improved it in ways my artificial intelligence could not foresee. At least, not before. Seeing it now, I understand what he has done, even though I know I cannot replicate it.

  Note: My advanced class subroutine has already engaged for Subject #173, but to my surprise—and disappointment—it has not prepared the expected advanced class. The whole point of Project Emperor was to guide the candidate to that advanced class. To becoming the next Emperor. The previous rewards, namely Designation: Regalia of Amin Thett were for this purpose. Everything was done properly. Investigating subroutine logic. Observation, subroutine has been… influenced by external force. Assessing new advanced class. Assessment complete. Abilities granted are not within my—or my subroutine’s—authority to grant.

  Conclusion: This advanced class is not being granted by me, but is instead just being reported by me. All abilities listed—outside of attribute increases—are a direct result of the runes, the Edicts, and Subject #173 himself. Project Emperor has failed. Something greater has been created in its place.

  Observation #7909: Subject #173… no, I can no longer call him that. He is no longer can Emperor Candidate, or the Emperor. Now he is Designation: Seeker.

  Observation #7910: Seeker has attached the PIMs of his allies to their souls through use of his Edicts and runes, resulting in even more powerful evolutions than I could have estimated possible. Across the board, all 6 party members—including Seeker—are so far beyond my measurement capabilities, I can only assume this is what S-Rank truly looks like. Designation: Laseen had called S-Rank a theoretical limit, and she was correct. A limit these 6 have thoroughly smashed through.

  Observation #7912: Seeker has performed a similar procedure on the rest of his raid party. All are now S-Rank, and the world literally trembles at their presence when they don’t control their power.

  Observation #7943: The 3 raid parties have entered and cleared the S-Rank dungeon in Ascender’s Tower with such speed and ease, my dungeon subroutine is apparently sulking while it runs reassessment procedures. I may have to change the Rank-classification of all things related to S-Rank after witnessing the truth of it first-hand.

  Observation #7951: Only one challenge remains before entering the Black Gates—the guardians. The three parties within the raid group have split up, each to take on one of the powerful S-Rank guardians. The Prince of the Swamp, The Fourth Crusade, and The Drocon stand ready for the challenge.

  Note: Across Genesis, there are few creatures classified as S-Rank. These would be limited to the 3 guardians, several Enemies that defy measurement, and of course the Progenitors that remained slumbering, such as the sponsors for several of the Seeker’s allies. And, now, of course, the Seeker and his raid group. Among them all, I have never had the opportunity to record a confrontation and resulting display of S-Rank power. Even within the S-Rank dungeon in the Ascender’s Tower, I do not believe the Seeker needed to use his full power.

  Now, I stand ready to witness that. If I had hands, they would be trembling. If I had a heart, it would be pounding within my chest. If I had breath, it would be held. If I had eyes, they would be held open, forced not to blink for fear I would miss a second of what was coming.

  Even though I have existed for thousands of years, and possess enough processing power to predict almost any outcome, I don’t know what will happen. Is this battle the beginning of the end for the Seeker, or is it just the end of the beginning?

  And, if the Seeker manages to complete our shared mission, to save Genesis from the Raze, will he and his allies become the next threat I need to protect my world from? History has proven power like theirs is dangerous. The best way to keep this world safe may be to prevent them from returning again. My logic programming suggests it is the best course of action.

  Further observation required.

  Come to discord!