Hello! From all of us at Gagneux Industries, we thank you for your purchase of your SERIES-01 modular Robotic Liaison. Whether it’s a chef, soldier, playwright, or simply a companion, we hope that your G.I.R.L. will serve your needs in every way you hope for.
This technical manual will get into the more involved specifications of your G.I.R.L. unit (hereon referred to only as “unit”) and the various ins and outs that are required to both operate and maintain it. Units are, of course, machines, and all machines must be cared for and maintained from time to time. While we always suggest taking it to a certified Gagneux Industries retailer for a tune-up, we understand that sometimes it’s easier (and more discrete!) to be able to service your unit from home.
Our units are modular in nature and we at Gagneux Industries believe in the inherent intimacy that comes from servicing your own tech, and so we present to you your SERIES-01 specifications in full in the following pages.
A unit is comprised of modular pieces, but most SERIES-01 units come with the same set of standard pieces: a head, a torso, two (2) arms and two (2) legs, which are described here. Modular parts ordered from GI will come with their own manuals on maintenance and integration.
The head itself is considered by the unit’s codebase to be LIMB_00 which cannot be changed. Within the head is the PROCESSING_MODULE, a powerful computer that holds your entire unit. Damaging the processor means potentially losing your unit entirely! There is currently no way to back up a unit’s personality matrix.
Attached to the head unit are a variety of sensors, each denoted in the codebase by two separate names. The “eyes” of the unit are considered LIMB_OOa and also SENSOR_VISUAL. The “ears” are considered LIMB_OOb or SENSOR_AUDITORY (note: stock units come with basic humanoid ears, but Gagneux Industries does provide animal-style ears – they are still the same name within the codebase, and any humanoid ears lose function when animal-style ears are attached). The “nose” is considered LIMB_00c or SENSOR_OLFACTORY. The mouth is considered LIMB_OOd or SENSOR_MOUTH.
The next modular piece of the unit is the torso, or the CHASSIS_MODULE, sometimes just referred to as the CHASSIS. Stock units come with a humanoid torso of varying design, and are filled with various systems that are integral to unit upkeep. Shaped like a human heart is the ENGINE, which is the unit’s primary power source. Surrounding that is the COOLANT_SYSTEM which provides temperature control not only to the engine, but the entire body including the head module. There is also the FUEL_TANK for units who use solid and/or liquid fuels, as well as processing supplements.
A chassis has, typically, between five (5) and six (6) sockets. The topmost socket is used for a unit’s head module. On stock models, there are two (2) sockets for arms and two (2) sockets for legs. Within the code, arms are denoted as LIMB_01a and LIMB_01b (left and right from the unit’s perspective) and legs are denoted as LIMB_02a and LIMB_02b, in the same manner.
Auxiliary ports are occasionally included at the base of a unit’s spine, or along the unit’s back for “tail” and “wing” components. These are very rare and not included with the stock chassis. Sometimes, however, a unit will fault and provide erroneous error codes (or “phantom feelings”) regarding these two types of auxiliary ports, and so for erroneous error code purposes a tail limb is considered LIMB_T and wings are considered LIMB_W0, LIMB_W1, and so on for each subsequent wing.
When prompted – or occasionally, if bad enough, unprompted – a unit may provide an error code for something faulting within its system. There is a system to the error codes that provide for slightly easier access than simply referring to this manual.
Error codes are five digits long. The first digit in an error code is the system involved – 0 is for system-wide or computing errors, and each limb is numbered in sequence: head (1), torso (2), left arm (3), right arm (4), left leg (5), right leg (6). Any auxiliary parts may be queried by the administrator to find their designation.
The second digit in an error code determines whether the error is an internal system fault (0) or an external one (1). Internal faults are the result of something going wrong with the system, while external faults are the result of tension from outside influences.
Following are a list of the most common error codes.
Here's how to make a list:
Note that this error list is simply the most common errors, and also a list in progress. The contents of this list may change over time.
A stock unit does not typically have direct commands designated out of the box, and these must be installed by their owner or handler at the time of set-up. There are, however, commands that can be given for primarily diagnostic purposes, as described here. All of these codes should be preceded by ADMINCODE and the pin, if set up by the owner/handler.
GENERAL_DIAGA unit will run a general diagnostic and print whether or not it has recently rested, consumed solid fuel, refreshed its liquid fuels, and whether or not it has taken its appropriate timed supplements.
ERROR_DIAGA unit will produce a list of running errors that it is experiencing. Anything it is feeling that is “wrong” will be printed here.
QUERY: XWhere X is a running error code, a unit will attempt to provide more context and documentation on the error in question.
SOURCE: XWhere X is a running error code, a unit will attempt to find and print the source of the error in question, if possible. If impossible, it will simply print “Source Unknown”.
SYSTEMCHECK XWhere X is the name of a system such as “LIMB_00” or “COOLANT_SYSTEM”, the unit will attempt to print the current status of said system(s) and any current relevant error codes.
Now that you know what your unit has to say and how to ask for it, it's important to know how a unit can respond. Units can be modified later to communicate in many different ways - through emojis, for example, or using fancy prose and so on; this can also be changed on a per-user basis - but the stock default language that all units use is the same.
First, all units will provide system dialogue within square brackets, [Like so]. A unit might say, for example, [QUERY: Why are you asking for my error codes?] or [EMOTION(GRATEFUL): Thank you for being understanding.].
As seen in those examples, however, there are certain words and terminology a unit may use that is unfamiliar to some users, and so below is a list of standardized terms that units will use when responding in system dialogue. Note: Any terms with an asterisk after them (*) are prefixes and are used before specific types of statements.