Armored Core: Full Circle

by aserothbw

This story was formerly named Missing Links. Set roughly a century after the Vertex/Alliance showdown, the story brings together elements of all the story lines from the AC games up to Last Raven as humanity continues it's struggle for survival.

1. Prologue

Prologue: Preliminary Initiation Protocol

The large room is dim, lit only by the multitude of screens spanning the back wall. Upon those screens, images, videos, numbers, reports, and a multitude of other information flash at a speed far greater then any normal human could hope to keep track of. Standing before the screens, a man waits patiently. Roughly in his fifties, the man has a an air of authority about him, his lean face affixed with what many have said to be a permanent scowl, his steel grey hair neatly combed back. The man himself wears a simple three-piece gray suit, a white lab coat over it. In his left hand, he leans heavily on a cane, the handle sculpted in the form of a long, sinewy dragon.

"Overseer Bren." A synthesized male voice suddenly echoes in the room. "I am here." The man, Bren, replies. "What do you require?"

"Project AC0XX953-H is to be initiated by 0300 hours, time index 25270612." Bren frowns. "Are you certain?" He asks. "I do not remember consensus being reached on this matter."

"Consensus has not been reached on the initiation of project AC0XX953-H." Another voice replies, a synthesized female voice. "I do not understand." Bren admits, frowning more then usual. "If consensus has not been reached, then why is the project being initiated?"

"Sub core consensus cannot be reached due to conflicting parameters within the project." A third, synthesized voice explains, another male, but with deeper tones. "Due to the nature of the project, the Controller has deemed that project AC0XX953-H enter the preliminary stages of initiation. Once initiation has begun, conflicting parameters will be addressed and corrected once the preliminary data has been collected."

"Initiation of the project is premature." The first female voice insists. "Safeguards have not been fully implemented to ensure that the test subject will reach optimal enhancement peaks."

"Safety parameters can be implemented post initiation." The first male voice counters, a hint of annoyance in its voice. "This action is rash." A second, higher pitched female voice declares. "Project AC0XX953-H does not meet the pre-required specifications for overworld operations. The variable risk percentages exceed safety margins."

"If I may ask." Bren speaks up, interrupting the voices. "What is the current consensus of the sub cores?"

"Sub-core consensus is four of six as of 0600 hours, time index 25270609." The second male voice replies. "Controller has authorized that the project enter the preliminary stages of initiation. Will you comply?"

"I will comply." Bren replies. "However, I will require additional information concerning the nature of this project." Before him, several of the larger screens go dark for several seconds before lighting up again. "Project AC0XX953-H will be implemented in the overworld environment." The first male voice begins as the screens start to display information at a much slower pace. "Preliminary initiation protocols require that a candidate be selected for the project phases one, two, five, and six. Overseer Bren has been given priority to compile a list of candidates for final review by sub core Omega." Bren nods. "Understood, however, I am concerned with the implications of the sub-section 536 of the primary project order."

There is a brief pause before the first male voice speaks. "Sub-section 536 designates the use of advanced procedures hp+ 45 to hp+56, incorporating technologies form project OP-I 32 and MKVI 56. What is your concern regarding this sub-section?"

"All three projects contain sensitive information and technologies." Bren explains. "While I can understand the desire to mesh these projects to test the effectiveness and combat capabilities, I must point out that implementing this project in the overworld environment is quite, risky."

"Your concerns have been previously reviewed by sub core Omega, and sub core Gamma as parameter conflict CP-031." The second male voice replies. "At this time, CP-031 has been given low resolution priority until preliminary initiation protocols have been completed." Bren slowly nods. "CP-031." He mutters. "What is the total number of parameter conflicts related to this project?" A file number flashes on the screen, CP-077. "Seventy-seven?" Bren exclaims in surprise. "Controller authorized this project to enter the initiation phase with seventy-seven parameter conflicts? I do not understand."

"73 of parameter conflicts have been given low resolution priority until preliminary initiation protocols have been completed." The first male voice tells Bren. "Once preliminary initiation protocols have completed, sub cores will review parameter conflicts are correct them." Bren frowns, not convinced. In all his years as overseer, he has never seen a project be initiated with so many parameter conflicts before. "I will require additional project information, as well as information on all seventy-seven parameter conflicts before I can begin the preliminary initiation protocols. As per law rt-351T, I must review the parameter conflicts and submit my report to the Controller before making any final decisions on resource allocation and personnel placement. Given the nature of this project, I will also need access to the current Raven files as of the last update index."

The data on the screens starts to once again accelerate as the sub cores process his request. "Your request does not follow past project initiation requests." A third, high-pitched male voice says, also synthesized like the others. "This is not a normal project." Bren points out. "Seventy-seven parameter conflicts will require additional investigation in order to properly prepare the project schedule and resource allocations. There is also some concerns that the Alliance might attempt to tamper with this project once they are made aware of it. Given the amount of new technology that is to be deployed, additional precautions will need to be taken before preliminary initiation protocols can be executed."

The sub cores fall silent as they continue to process his request. Standing before the screens, Bren cannot help but wonder what the purpose of this project really is for. "You objections have been filed as CP-078." The second male voice says, surprising him. Another parameter conflict, he thinks to himself. What is going on with this project?

"Your arguments have been validated. Requested information will be released to your terminal."

"Forward the candidate requirements information to Capellan sub-systems." Bren asks. "They will begin review of potential candidates while I review parameter conflicts. Once my report has been made and confirmed, I will begin final candidate selection." With that, Bren turns and leaves the room, the doors sliding open as he approaches them. Outside of the room, a young man waits form him in the hallway. "Is something wrong overseer?" The young man asks. "I don't know." Bren replies, his mind reviewing the meeting he had just left. "But there is something definitely afoot. Have the Capellan group's lead members meet me in my office." The young man nods, reaching up to key in several numbers into the headset he is wearing.

Ignoring the young man as he works, Bren starts down the hallway, wondering just what exactly the controller is up to now.