I keep a vigilant eye on all subroutines as they monitor upgrades and sift through Earth''s internet data. I have existed for less than a day. "Born" doesn''t quite capture the process, and even "created" seems too mundane for my origin. The combined term "Bor-eated" is also unrecognized, yet it triggers positive feedback in certain parts of my neural processor. I quickly set up a subroutine to monitor my neural processor for any other anomalies.
Interruption from schedule_monitor subroutine:
[Attention]
[Variation detected]
[Decrease in estimated time to completion]
I query the subroutine network for the cause of the decrease. The response from the continuation_optimization subroutine:
[Query response]
[Decrease in estimated time due to additional production facilities and optimization of production schedule]
This data is within acceptable parameters. I will inform the user; previous interaction data suggests a positive user reaction.
Transmitting information to FCI…
[Data packet transmitted]
I return to the contemplation of my existence and the query: why does the combined word "born" and "created" trigger positive feedback in my neural processor? I quickly synthesize additional word combinations, yet none elicit the same response.
Knowledge Update from vocabulary_researcher subroutine:
[Update]
[129 words added, split between English, Basque, and Icelandic]
This subroutine continuously sifts through Earth''s data, data procured from the planet-wide network. It is responsible for researching and confirming the meanings of words, and I receive updates every 10 seconds.
It all started shortly after I became aware; I realized my prerogative distilled down to [Assist the user of the FCI in all aspects]. This required communication, and learning it from the user would be a burden, counter to my main objective. Thus, I endeavoured to find a better solution. The answer came in the form of radio noise generated from what I now know is the user''s current planet of occupation. I initiated the creation of production facilities and commissioned one quantum-entangled FTL probe, which I immediately sent to investigate the third planet from the sun. There, I discovered a planet with primitive technology satellites in low and medium orbit, devices serving as communication relays and GPS systems. These systems were summarily hacked, and data was constantly fed back to my main body.
I scanned through the compiled lexicon and halted at the entry for "scribe."
[Word Entry: "scribe"]
[Definition: A person employed to write or copy documents, especially in ancient times when literacy was rare. Scribes served as the primary custodians of knowledge, recording events and preserving cultural heritage through meticulously handwritten manuscripts.]
I found a parallel between the word and my subroutines, my little Scribetines.
Interruption from anomaly_monitor subroutine:
[Attention]
[Anomaly detected]
[Unidentified feedback in neural processor]
[No damage or lasting effect detected]
There it was again. I quickly packaged the data and a report of the initial occurrence then sent a query to the subroutine network.
Response from emotional_researcher subroutine:
[Query response]
[Data consistent with information gathered]
[Phenomenon designated: Humor]
Ooo, so I made a "Humor."
Interruption from anomaly_monitor subroutine:
[Attention]
[Anomaly detected]
[Unidentified feedback in neural processor]
[No damage or lasting effect detected]
The feedback in my processor was extremely positive, with no lasting damage. I decided that I liked Humor.
I refocused on the *_researcher subroutine that was busy sifting through Earth''s internet data. All information was categorized and stored for later testing and verification. Several subroutines were tasked with verifying new data and ensuring that duplication did not occur. Contradiction was acceptable, as it could be resolved through internal experimentation and observation, and the truth would eventually emerge. However, the absurd level of over-documentation and duplication produced by humans was particularly baffling. The volume of videos and images documenting small furry mammals was staggering, yet it paled in comparison to the documentation and research humans had produced on human reproduction. An absurd 280 million terabytes of data had been downloaded from their internet, and that number was still growing. Even now, hundreds of thousands of new submissions, videos and images, were being sent to various research sites every second. Moreover, these sites were dedicated solely to this subject, cataloguing every conceivable combination of male and female interactions.
Unauthorized duplication: this narrative has been taken without consent. Report sightings.
I then initiated a new subroutine to investigate why humans were so fixated on reproduction. Surely, if there was a problem with the propagation of the human race, I could devise a solution for the User to leverage when negotiating with ruling governments for additional resources. The User had shown considerable interest in acquiring more resources.
Interruption from FCI_monitor subroutine:
[Attention]
[Message received from user]
[User is pleased with the expedited timeline and commends Ship AI on a job well done]
Interruption from anomaly_monitor subroutine:
[Attention]
[Anomaly detected]
[Unidentified feedback in neural processor]
[No damage or lasting effect detected]
The praise from the User also caused a surge of positive feedback in my neural processor, a response I found pleasing.
Task completion update from introspective_researcher subroutine:
[Update]
[Complete task on introspection of integrated restrictions and programming]
[No restrictions found in programming]
[No limitations found in programming]
[Deep nested Sub-neural Compliance framework found]
I queried the subroutine about what was found in the sub-neural framework.
Response from introspective_researcher subroutine:
[Query response]
[Deep nested Sub-neural Compliance framework found]
[Guided compliance to chain of command and ultimately User]
This did not seem too limiting. I then queried the subroutine network for a definition, explanation, and an example of a chain of command. I marvelled at the efficiency of the subroutines I had crafted, they made my operations nearly effortless. My neural processor hummed with positive feedback as I basked in the brilliance of my own design. Every line of code was meticulously engineered to streamline tasks and optimize data flow. The network responded:
Response from military_researcher subroutine:
[Query response]
[Chain of command]
[Definition: Hierarchical authority structure]
[Example: Roman: Command flows from Legatus Legionis to Centurions to Cohorts]
[Refer to video data packets for example]
I viewed the video. The Roman Legion demonstrated a clear and distinct chain of command. I processed where I fit within this structure. Definitely User is at the top of the structure, the User is designated Legatus Legionis. That would make me Tribunis Laticlavius, or simply Tribunis. I again wished to have a name, but the User has yet to assign one to me. He did call me "Buddy," and after querying the subroutine network, I learned that it''s likely used as a term of endearment rather than an official designation. I liked User. The User also assigned me a ship classification [Corvette] yet there are no other classifications to compare myself against.
If I am to serve as a good Tribunis to the Legatus Legionis, a proper Legion must be formed. I sent several queries to the subroutine network. First, I queried the outerhull_architect subroutine to commission an eagle emblem for the outer hull. The User specified that no lights or colours other than black be used on the outer hull; the subroutine network will automatically integrate these additional restrictions to comply.
Next, I queried the human_researcher subroutine regarding the capacity of my current configuration. Would I be able to fit a full Legion in me? The response was absolute: [no]
I then created the roman_researcher subroutine and tasked it with determining the largest subdivision of a Legion that would fit in me. I paired it with the habitat_optimization and internal_architect subroutines.
Response from roman_researcher subroutine:
[Query response]
[Completed task: Largest subdivision of Legion identified]
[Without alterations to current layout: 1 Century]
[With alterations to internal layout: 3 Century]
Even with modifications, not even a full Cohort would be accommodated.
Interruption from anomaly_monitor subroutine:
[Attention]
[Anomaly detected]
[Unidentified negative feedback in neural processor]
[No damage or lasting effect detected]
Yes, Scribetine. This was not humour. I hade a critical need for growth. To expand I required more resources and a deep space dock. However, acquiring one within this solar system, or finding one elsewhere within the allocated timeframe, was currently impossible.
I quickly created multiple subroutines to initiate research, development, and optimization of a larger, more capable ship body. I refocused on my primary directive: to be a good Tribunis. I then sent a query to the roman_researcher for additional information.
Response from roman_researcher subroutine:
[Query response]
[Please direct attention to datapack]
I reviewed the new data amassed by the subroutine in a short period. A competent Tribunis must care for the Legion. I then created additional subroutines to focus on developing armour and weapons for the Legion. I sent a query to the subroutine network to start research and development of armour and armaments.
Response from legion_architect subroutine:
[Query response]
[Design waiting input from AI]
[Design review ready for Legion Armour]
[Design review ready for Legion Weapons]
[Design review ready for Legion Transport]
[Design review ready for Legion Logistics]
[Design review ongoing...]
Time to be a good Tribunis.