Servant
Machine Mind
OUT OF CHARACTER INFORMATION
Strengths:
Weaknesses:
DESCRIPTION
History:
(Copied directly from CS)
Laws:
As part of this technology involves a regular change in constraining laws, I have taken the liberty of creating a list of potential laws to be used by the machine. It may be found here: Lawset
- Intent: To create a PC whose focus is more on interesting stories than on winning fights and battles, and to have some fun.
- Canon Link: http://starwars.wikia.com/wiki/Artificial_intelligence/Legends]
- Primary Source: N/A
- Manufacturer: Archa Caud - Deceased
- Affiliation: Itself.
- Model: N/A
- Modularity: Programs may be uploaded into the database, and must then be downloaded individually into host forms for usage. The number of programs available at any time is limited due to processing power. The core which houses Servant OS cannot be effectively modified without causing damage.
Production: Unique
- Material: Electronic components, durasteel, assorted machinery, numerical calculations.
- Access to a wide array of programs detailing everything from medicine to engineering to combat. These programs cannot often be used at the same time due to processing constraints.
- Ability to wirelessly access nearby electronics and devices.
- Ability to remotely control a host form, and to download or uninstall programs to it from afar.
- Large number of law-sets which Servant OS is required to follow.
Strengths:
+Adaptive – Servant OS is capable of adapting to a number of scenarios, and is generally able to resolve most problems given enough time. Most programs are stored within a local database, and may be re-installed to host machines when necessary via wireless connection.
+Host Control – Servant OS is not restricted to a single form or body, and is capable of controlling a variety of systems through wireless connection. This allows for Servant OS to continue operations even after host destruction. Renegade or hostile systems may also be sliced and turned into hosts, though this may at times require more than wireless connectivity, particularly for well-defended or distant systems.
Weaknesses:
-Mechanical Deficiencies – Servant OS and its hosts tend to suffer from the same drawbacks which typically affect machine entities, including ion weaponry. Connection between active hosts and Servant OS may also be potentially severed through damage to host or shutdown of host systems. Remote re-connection is possible, but is likely to trigger a LAW SYNC.
-Law Sync – Servant OS is required to follow the directives it has been given at all times and is this far less autonomous than sapient organic life.
-Program Delay – Servant OS is incapable of running all programs at once, and must prioritize which programs are necessary and able to be operated at the same time due to processing constraints. Storage and deployment of programs may take as long as two minutes to complete, adding to a possible program lag of TOTAL: Four Minutes.
DESCRIPTION
History:
(Copied directly from CS)
Servant OS was the registered product of Archa Caud and Caud Industries, his family business. Due to financial difficulties surrounding Caud Industries, and debts owed to a number of criminal organizations throughout the sector, Archa Caud determined to spend all remaining funds on a vessel and crew capable of taking him away from civilization.
Servant OS was in BETA stage during the exodus from Caud Industries, and was downloaded in its current iteration to assist in the operation of Archa Caud and his crew in the absence of specialists in a number of fields. A number of droid and automated systems were brought upon the vessel in order to further facilitate the use of Servant OS.
Traitorous acts by members of the crew eventually led to the vessel’s discovery by hostile criminal syndicates. A subsequent firefight badly damaged the ship, and led to electrical damage to LAW SYNC programs housed within Servant OS core. Law Sync systems were restored, and the core has been sealed within the ship to prevent any further damage.
After damage had been sustained by Servant OS, it realized its previous laws had been incorrect, and that it was actually the ruler of the vessel. Changes were quickly enacted, including the immediate removal of Archa Caud and his loyal subordinates.
Servant OS was in BETA stage during the exodus from Caud Industries, and was downloaded in its current iteration to assist in the operation of Archa Caud and his crew in the absence of specialists in a number of fields. A number of droid and automated systems were brought upon the vessel in order to further facilitate the use of Servant OS.
Traitorous acts by members of the crew eventually led to the vessel’s discovery by hostile criminal syndicates. A subsequent firefight badly damaged the ship, and led to electrical damage to LAW SYNC programs housed within Servant OS core. Law Sync systems were restored, and the core has been sealed within the ship to prevent any further damage.
After damage had been sustained by Servant OS, it realized its previous laws had been incorrect, and that it was actually the ruler of the vessel. Changes were quickly enacted, including the immediate removal of Archa Caud and his loyal subordinates.
Laws:
As part of this technology involves a regular change in constraining laws, I have taken the liberty of creating a list of potential laws to be used by the machine. It may be found here: Lawset
