Data Log
Authorization - *******
Confirmed Access Approved
Loading Data
Name: Krusa Corraine
Ship: XB-2 "Havoc Mk II" Ageira Bomber
Home System: New York
Unique Roles: Guardian Safety Controller
Krusa first started out as an LPI Pilot, however, displeased with a few of his encounters he worked harder and became accepted as an LSF Pilot. After several days of waiting, he was finally issued his LSF ID. Once the LPI ID was torn up and tossed to the back of his Liberator, Krusa undocked and left and headed back to New York. Over the next few weeks he encountered several enemies. Most he could only hold off in hopes that help would arrive shortly as his ship was too weak. Because of this flaw Krusa searched for a more powerful ship and found himself purchasing a Raven Claw. After a few fights he realized a flaw in his new ship, which crippled its effectiveness similar to the Liberator. This ship, while having great firepower, lacked agility and was defenseless against faster ships.
After finding his Raven Claw lacked the agility essential to , and knowing his very limited capabilities in the BDR Series Fighters ( //Defender, Guardian, Executioner, Avenger// ), he set out to find a way for a Guardian under his command to be piloted without human control. One day, he came across the Liberty Autonomous Sentinel Project. The project currently had a Liberator controlled completely by an AI, needless to say they came to the same conclusion that Krusa did concerning the Liberator's strength. The LASP supposedly had an unsuccessful attempt at placing the Sentinel in control of a gunboat, due to its response time. Krusa began to think how the Sentinel could be placed in a stronger ship, without sacrificing too much of its agility. His answer was the BDR-804 Guardian.
With the combined efforts of LSF technicians and LASP programmers a new project was started. This project would be named after the ship being used, Guardian. After countless amounts of reprogramming and program testing, the Guardian System was put through simulation flights. Nearly four months had passed as the system was being calibrated to fly the BDR-804 more efficiently. Now, it was time for a test flight. Krusa, confident that the system would be a success, became it's test pilot, in case something went wrong and the Guardian System needed to be shut down.
Guardian Test Sections
Docking with trade lanes, stations, and landing on planets to test basic controls.
Cruising through debris fields and asteroid fields to test response times and agility.
And finally, encounters with practice ships such as traders, pirates, and smugglers to test its decision making and fighting ability.
Each part of the test was passed without a single problem. Once Krusa returned to Norfolk Shipyard, the Guardian System was placed in full control. With the Guardian System now running on its own, Krusa obtained a bomber ship so that once fully equipped, should it be necessary, the Guardian could be recalled to Norfolk and Krusa sent out in his bomber to engage Capital Class ships.
Project Guardian
Authorization - *******
Confirmed Access Approved
Loading Data
Callsign: Guardian.059
Ship: LAAS-059 "Guardian" Liberty Very Heavy Fighter
Base: Project Guardian Docking Station at Norfolk Shipyard
Project Guardian began as an advancement to the Sentinel Project. It has very similar programming to the Sentinel in that it will enforce Liberty Law and will accept orders from LSF and LN designated ships. It is connected directly to all ship controls including the communications unit. Because of this it can understand other pilots speaking on comm-links ( //in english of course, given server rules// ). However, since it can't speak, it uses the console on ships to send messages.
For Common Encounters:
Due to some pilots being confused as hostile pirates, the Guardian System has been programmed to clarify
an unknown pirate's intentions, engaging only in defense. Should a hostile intention be found, that pirate's
name will be saved and engaged offensively during future encounters.
As for smugglers, once contraband is found on a ship, the cargo scan is saved. That smuggler is then given
a chance to drop his cargo for immediate disposal. Should this chance be refused, the Guardian will engage
the ship carrying the contraband.
Since the Guardian is still incapable of fighting large groups of fighters, once a group of hostile targets has
been encountered, an alert will be sent out to all ships and the Guardian will only engage defensively unless
assistance arrives.
When hostile capital ships are encountered, an alert will be sent out to all ships and the Guardian will keep a
distance from the ship and wait for assistance.
If the Guardian System or it's ship is in danger, it will immediately send a backup to Norfolk Shipyard and
erase all data aboard the ship.
The system will continue to learn and adapt to new encounters such as smuggler routes, enemy tactics, and area authorization.
Project Guardian
Authorization - *******
Confirmed Access Approved
Loading Data
With the cooperation given by the Bounty Hunters Guild in supplying the weapons used in the Guardian Unit 059 Fighter, work began on a second AI, Guardian Unit 062. This was to be a Cruiser Support AI installed on a Talarca Cruiser "Fenrir" that was assigned to a Bounty Hunter named Krin. Because only people directly involved in the programming, construction, and maintenance of the AI are allowed to operate on the Guardian Units, one of the technicians was assigned to the Fenrir.
Data Log
Authorization - *******
Confirmed Access Approved
Loading Data
Like everyone else, Krusa's past caught up to him. He had received previous reports of ships being piloted by someone claiming to be Riku. However, because none of these reports were confirmed, he paid no attention to them as the Riku he knew as his brother was still taking freelance jobs out in Rheinland. A few days ago, Krusa heard a familliar voice over the system channels. To his surprise, it was Riku. Krusa asked if he was still working as a freelancer, but only to receive a reply stating he had become a Lane Hacker. After a while of talking, Krusa asked Riku if he'd join him for a bit of target practice as they used to do back in the Navy. Riku agreed but only after setting a wager. If Krusa lost, he would have to leave the LSF; If Riku lost, he would have to surrender himself to be arrested. Being a better pilot than his brother, Krusa won the bet and took Riku to be placed in a holding cell aboard the Missouri. The following day, Riku was to be transferred to the Fairbanks Prison. Even though Krusa was a better pilot, offensively; Riku was a better defensive pilot, able to escape numerous situations. During the transfer, Riku broke free and fled towards the outer systems.
Construction of a new Liberty Assault Battlecruiser began a little over a month ago. The Liberty Assault Ship "Freedom" is now operational. The Guardian unit-086 System, "Aesir", is still in its testing phases aboard the ship.
This ship uses a uniquely adapted version of the Guardian System. Unlike the BHS-Fenrir, that was scrapped a few months ago, the Guardian unit-086 is fully integrated into the design of the Freedom. To protect the Civilians of Liberty, instead of mooring with the Norfolk Shipyard like other Guardian equipped ships, the Freedom will be moored at a more remote, classified area. The ship holds a total of one hundred crew members. Among the crew are: Weapon's Specialist Jac taking command of the Gunners; Officers Jun, Cofield, Drake, and Razak in command of the various prison sections; and Dr. Trall in charge of the medical and research labs. Krusa Corraine of the Liberty Security Force is in charge of the ship. However, as a naval commissioned vessel, the ship and its crew ultimately fall under the command of the upper ranks of the Liberty Navy.
Project Guardian
Authorization - *******
Confirmed Access Approved
Loading Data
Callsign: Guardian.206
Ship: LAAS-206 "Guardian" Kushan Freighter
Base: Project Guardian Docking Station at Norfolk Shipyard
Several advancements have been made to the Guardian AI making it capable of handling heavier systems. The AI can now control a more powerful shield and it can handle more complex weapons systems allowing it to utilize more weapons. Unfortunately, the ship that the LAAS-059 utilizes is not capable of holding the upgrades. Unit 059 will be scrapped from its current ship and placed into storage after being upgraded to Unit 206's model. It will be used in later plans to place it within an armored transport as a heavy armor assault ship or a gunboat as a fast attack ship.
Ten days ago we began looking at the ship databases and found the Kushan Freighter to be the best option. Though its classed as a frighter, just like the Armored Transport it is able to do very well offensively. Two Kushan Freighters were ordered last week and were supposed to arrive today. We received one, along with the transport they were on, which was slightly damaged. The pilot in command of the transport claimed the attack was made by a pilot by the name of Cale Cross. More details will be in the next transmission.
The Guardian System on Unit 059 has reached its limit in potential.
In it's last battle totaling over 10 veteran piloted ships destroyed within half an hour.
Recently, a scout patrol sent out to assess the damages on various installations due to a heavy ion storm. A few days ago, they reported an unknown ship that was apparently disabled by the storm. The patrolling ships towed it to ||||||||||||||| in case it contained any survivors. To our surprise the ship had no signs of human influence. There was no cockpit, it had a robotic arm and a power source that, while not unheard of, has never been seen before or had any construction method that even in theory looked like it would work.
After running numerous other tests, it was found that this ship was constructed by itself, or at least, others like it. We also found pieces of data that were left over from the ion storm, most of which was probably erased during the ion storm, some of it in ways similar to the Guardian System. However, overall, the unknown ship's data was more complex than anything humanly possible. Just a single block of this ship's left over data was equivalent to what we would have used to program at least three Guardian Units. Our tests also found a very interesting weapons system, it took a while to compile all of the data but from what could be guessed, some of its weaponry was damaged during the storm.
We decided that after erasing the remaining data, this ship would be the perfect base for Unit 059's systems. The storage capabilities of the ship allowing the system to reprogram itself and change its actions based on the environment it was in. Since the Guardian System on Unit 059 no longer needs access to information databases at Norfolk, its effective range is limitless.
Although we couldn't add some of the external security systems as we did with the BDR-804 during its original construction, we were able to add some internal security programming. Though not as effective the technicians will try to maintain control of it from Norfolk Shipyards should anything happen.
Decrypting Additional Data
Destination: Norfolk Shipyards
Source: ---------
Comm ID: ---------
Encryption/Routing Code: GSX0359
[font=Times New Roman]Until further notice.
Control, development, and maintenance of Unit 059 has been given to the lead technician, ID 9048245.
New events have required me to go even further into my mission and will be unable to make contact for some time after today.
The data I have collected so far has been transmitted.
It should prove useful in extending the range and overall functions of the system.