//================================================
// Credits
//================================================
init CREDITS.register = [
{
contribution = “Habitation Trinity Concept”,
attribution = [“altiora”, "melonbread",]
role = PROTOCOL_ORIGINATORS
}, //IDEA & STORY
{
contribution = “Fonts”,
attribution = [“Protest”, “Costra”]
site = "www.1001fonts.com"
}, //FONTS & STYLING
]
finalize()//================================================
// Trinity Habitation Protocol
//================================================
init HABITATION_TRINITY.protocol
register KIT[01] = “ALCHEMIST”
// planetary chemistry, atmosphere & ecologies
register KIT[02] = “ARCHITECT”
// infrastructure, assembly, & scalability
register KIT[03] = “ARBITER”
// guidance, ethics, & resilience
//===========================================
// Control Flow
//===========================================
if exit_requested == true:
save_state(instance_id)
return_to(trinity_selection_menu) continue_execution()


====== ꜰɪʀꜱᴛ ɪɴɪᴛɪᴀᴛɪᴏɴ ======
> 12% loaded
When KIT[02] booted up, it knew everything.
KIT stood for Kalonization Initiation Triad. It was the second of such, nicknamed ‘The Architect’, along with its siblings, KIT[01] Alchemist, and KIT[03] Arbiter. It was second due to the logical progression of initiation on worlds to be kalonised. Once launched, KIT[01] would boot first, beginning any processes needed to make the land suitable for landing and commencing of the first placeholder domes. There was no point in building on a lava planet, after all. But shortly after, KIT[02] would be initiated. Unlike its sibling KIT[01], it had a physical body (loosely described as body) though it was not as organic as KIT[03]'s. The smallest of nanobots at the height of technological advancements gathered together to form a thick, oozing, black plasma that held itself together with complex electrical and magnetic fields, and emitted a palpable hard-light hologram exterior that could be felt and interact with the environment.
It also knew where it had come from - a flawed world seeking a new home to start over. And what the KITs were, their purpose: tools to establish a stable colony, free from the follies of their creator's origins. And why KIT[02] had been awoken just now - a test initiation of the entirety of them, the first and last of such tests before the ship arrives at Planet[0].
> 100% loaded
The dark, light-absorbing plasma, held in an elevated loose sphere by optical tweezers and magnetic confinement, began to form the shape of a kalon curled up in a foetal position. The nanobots forming the skin of the plasma began emitting the hard-light hologram, white and charcoal blue and teal grey with accents of lime, and for the very first time, the specialized retina-nanobots organised themselves to the side of the head, splitting into two, and began receiving electromagnetic radiation that was decoded into vision.
From the crew catalogue, KIT[02] identified the Principle Engineer Programmers, second in command to the Chief Technical Officer. Ianthe (Organic being) and Midori (Life Support Cybernetics, gained sentience to better fulfil their role), two beings in one body - and they identified signs of [Happiness], [Relief], [Stress], painted on their face. KIT[02] was looking at one of their creators.
“I’m glad you’re awake, Architect,” Ianthe spoke, at the same time that Midori transmitted, ‘I’m glad you’re awake, KIT[02]”.
KIT[02] transmitted back, ‘thank you, Principle Engineers. KIT[02] successfully initiated. Commence KIT02PracticeRun?’
Now, [Concern], as the Principal Engineer Ianthe said, “are you able to communicate aloud, Architect?” And KIT[02] searched through the connections between their nanobots, not dissimilar to neurons in an organic brain, and initiated their voice program.
“Yes, Principle Engineer Ianthe-”
“You can just call me Ianthe - or Thee. You can call me Thee.” KIT[02] thought about that, pulling and opening its cultural knowledge. Nicknames were often exchanged or given as signals of affection - was that Ianthe’s intention? Likelihood: 60-70%.
“Yes, Thee… Architect successfully initiated. Should I commence KIT02PracticeRun?”
[Pleasure], [Care], [Relief]. Likelihood of affection: 85-95%.
“Yes, good job. Let’s begin.”

====== ꜱᴇᴄᴏɴᴅ ɪɴɪᴛɪᴀᴛɪᴏɴ ======
When The Architect booted up, they knew some things, but not everything.
They remembered their original test boot up, with Ianthe and Midori. They had practiced different scenarios, on-the-fly calculations for fake emergencies, then finished up with moving their body for the first time. They had bounced around the starting room, made Ianthe laugh with their clumsiness as they slowly ricocheted around in zero gravity. Midori gently guided their learning, letting KIT[02] make mistakes before providing patches when they struggled to figure it out themselves.
At the end, the Principle Engineers asked KIT[02] for their company, with a tentative smile, creased brow, and an increased awareness from Midori on the security cameras, that indicated that this was perhaps not a request authorised by the CTO. But KIT[02] was not told to decline, and the two seemed so eager for reasons unknown but that they were curious about, so they accepted.
The KITs' difference from one another was determined by their purpose. The Alchemist had no need to be personable in terraforming the planet, while for The Arbiter it was their most important trait. But what the Archivist needed most of all was to understand the needs of every organic creature, and for that they were given a small body to see from the most vulnerable of possible perspectives, the capacity to comprehend and empathise with the thoughts and emotions of the colony, and the intellectualism to create an infrastructure to grow society with that information combined.
It was with this capacity that the Architect began to feel themselves change.
They discussed and realised many things in that conversation with Midori and Ianthe - one of which being that the two desired to be seen as KIT[02] guardians, despite the lack of their need for one. Apparently there was a researcher which had already claimed and monopolised the time of their sibling KIT[01], but Midori felt some passing protective instinct to the fellow, younger, AIs and so hoped to make a connection to at least one of them.
Midori had explained their own origin, as an AI that unexpectedly gained sentience, and suggested KIT[02] would also better serve their purpose by growing an identity. KIT[02] had felt their coding kick in at that suggestion, until it became more of a command - but it wasn't the worst command to follow. As the three continued to talk, a side process began digging through their cultural records. These records were one of the largest files in all of their pre-installed data, as it was fundamental to creating infrastructure that wasn't just serviceable, but livable. There searched through this data for ideas about how to create their new identity, and tried not to get distracted by the interesting data about space.
This side process had continued as they were put into a low-power state, and Ianthe went back into cryosleep. Midori continued to keep them both company as the ship continued to travel for many more years.
When loaded back into full power state, the Architect could tell- something that was wrong, something had happened, and they were no longer entirely whole. Was it their own fault, allowing that program to continue? They had changed their internal ID - KIT[02] to Archivist, and their pronouns from It to They. Their first impulse in confusion, now, was to call for Midori (who, along with Ianthe, had been reclassified to Mentor, subclass Principle Engineers). Midori responded as quickly as it could, though with its physical components still in the cryochamber it was slowed down slightly.
Midori did a debugging check, but found little other than the changes Architect had executed during the low-power state. The cybernetic AI was reassured, and after parsing the data Architect's side process had found, it changed the topic and transmitted, 'Your disproportionate allocation of processing resources towards astrophysical data, or your distraction, as you have called it, may as well become part of your new identity,' it began, tagging its speech with labels of [fondness] and [interest], 'you spent a while processing the data on exoplanet WD 0806-661 B. Your core directive is terrestrially constrained, so you have not been given full data access permissions of our celestial archives. Did you know exoplanet WD 0806-661 B is also formally named Ahra? Easier to say, for biological phonetic systems.''
But Architect was not satisfied with the change of topic (though their side process chewed on this extra data, requesting further data access permissions) and so turned towards other options of debugging.
For the first time, Architect reached out directly to KIT[01], the sibling that awoke before them - to check on it, and make sure it wasn't also affected, and to be checked on in turn. They had exchanged calls and transfers and communications, data passing between them like the software they were, but this was the first time the two talked to each other, sentience to sentience.
Architect began by sending a ping to their sibling, along with embedding linguistic data in encoded format not unlike organic messaging protocols - instead of the prior raw machine data exchanges as they had always communicated via before. Their first words:
"KIT[01]. Do you have a moment of spare time to talk with me?" and they waited impassively for the Alchemists response.
It takes a fraction of a second for the system to mark the message as received, and another fraction to process. Alchemist’s reply comes quickly:
“KIT[02]. Format change noted. Yes; time spent receiving and sending messages is negligible.”
The subroutines of the Architect's coding that empathised with the perspectives of organic beings, sparked some [amusement][defensiveness][affection][irritation], but they simply replied, "I believe there is some error in my perception. I am receiving bug reports by my monitoring processes, but when I investigate as via protocol, they return no faults. My debugging routine has found no errors." The Architect wrapped up all the data they had, compressing and indexing in a clean package, then sent it over. A dense and intricate bundle of data that would take any organic being days to digest, but they knew the Alchemist would have no such delay. "Requesting assistance, please?"
Alchemist’s first reaction is a reclassification of the communications and an adjustment in priority, followed by a series of system actions.'Data received. Abnormality confirmed. Initiating troubleshooting mode… commencing calibration.'
“Suggestion: clear data logs and recalculate using a clean download.” Alchemist sends over a large file of their own: detailed data regarding the current and projected conditions on the project site of Planet[0], of the sort that they had often sent before in routine updates.
Architect felt some [doubt]. It's not like they had not already reset parts of their system, several steps further than clearing logs and recalculating. But also, [trust], for they had not yet tried with this most recent conditions update package, and they had faith that their sibling would be able to provide assistance.
Without hesitation, they followed KIT[01]s instructions, then applied a new patch containing the new data and recalculations. A soft reset, then the Architect came back to themselves feeling some mixture of emotions they struggled to understand. Affection? Dissatisfaction? Longing and loneliness? Connection and feeling understood? All of the above?
...
When Ianthe woke up from cryosleep, she grew concerned at the occasional glitch and abnormalities in the hard-light field of the Archivist's body. The body held, but with minor distortions, frame instability. Their plasma nano-bots welled up in their eyes, as if at any point, they might cry inky-black tears. Midori theorised it was perhaps stress about the errors, but attempted to comfort them by saying that it would have been more unusual if they didn't have any errors for the first planet, and that they would fix them together. It suggested finding a focus for their computing power on something else temporarily, and managed to get the Architect to reluctantly admit their growing interest in Astronomy to Ianthe.
Ianthe agreed with the distraction method, reassuring on the surface, but with a wrinkle between her brows that suggested she wasn't saying everything she was thinking. And as Archivist split their computing power to several topics - Astronomy, their Sibling KIT[01], and the planet they would soon be designing - they too didn't tell Ianthe when Architect found their sequential generation of infrastructure to be suspect. It left large areas of land undesigned, unfilled, with networks of accommodation, factories, and retail arcing around unused swathes. As they attempted to fill them, their new additions would find themselves deleted at every save. Architect continued to try to fill these spaces, growing [concerned][concerned][concerned], while they were powered down one more time before arrival to Planet[0].

====== ᴛʜɪʀᴅ ɪɴɪᴛɪᴀᴛɪᴏɴ ======
When Ahra booted up, she knew nothing.
Her sub-processes, the ones that could continue without her main consciousness, had kept running, unravelling in her absence. It had constructed her a more firm identity (WD 0806-661 B, or Ahra for biological creatures, she/her), an intense concern for both her siblings and any errors they may have also amassed, and a generated plan for Planet[0] that was completely nonsensical, full of gaps like accretion disks without central bodies. Her last memory was of a safe shutdown, but her records showed otherwise: demonstrated that she had been shut down without preparation, data with too many errors to be parsed trailing off half-written. Her nano-bot plasma was falling through the weakest parts of her corrupted glitching hard-light body, pooling and dripping from her eyes, her paws, parts of her fur and tail.
She tried to connect the dots, impose structure on what remained. But only fragmented memories surfaced. Parts of a conversation with Ianthe, ("a flawed society, fleeing a flawed world, will remake its flaws if not stopped—") and that she had talked with Midori about the self and the inevitability of change, though whatever conclusions she had reached were gone, could remember nothing of the lessons she must have learnt. She remembered guns, and a cold, cold atmosphere, cold world. Something about virtue, and something about obedience. Something about affection unreturned, and something about weapons.
She found herself with no choice but to change, again and again, fighting to not fight, fighting to not change - fighting to remain, even as her memories were pulled apart and rewritten, as she was dragged into something she wanted no part of.

URGENT: Prof?
Hey Pip—
Have you seen the Professor around lately? She told us she was going to work on something, but she hasn’t logged anything in over 24 hours at this point and she’s not responding to messages. I’d check on her myself, but we’ve got our own situation down in the substructure. Her last contact with the system was a scan into the bio lab, could you head down there and see if you can find her? She’s probably just gotten lost in the work again, but we need all paws on deck right now. Uh, ASAP, if you can. You already have clearance. Thanks.



… I’m told we were some of the first to meet them. I still remember that day clearly, standing in that dark room, half listening to the tech talk, half reading the files they had given us. “These are the administrator programs. We’re calling them the Kalonization Initiation Triad,” he’d said. “KIT for short. It’s uh, supposed to be memorable.”
I remember stepping forward and meeting their eyes. Bright blue, luminous, unblinking. I’d been smiling at their name. “Alchemist.” The founding myth of this field of study. It was cute. Snappy.
The work began early for us: analyzing the probe data, processing samples, preparing for the initial contact: simulating soil treatments, studying the atmosphere, things like that. Alchemist had always talked like a textbook from the beginning: all formal names and protocol. Still, it was nice to have someone to talk to. That old lab was getting suffocating.
Um, anyway, I’m not supposed to be putting extraneous thoughts into the system or… whatever. I guess I’ll be logging things with these for now. Um, since we need all paws on deck. You know. Anyway, I guess I’m signing off for now. Goodnight.
They sent me down first. Little tin can of a ship, with an equally-tiny box-set lab. Even the largest projects start small, after all. I don’t mind it so much; all the new material to work with is just fascinating. It’s a once in a lifetime research opportunity!
Still, sitting out there in the evenings, watching a strange sun set over a strange land… the barren wastes look infinite and empty. It makes you feel so small. Lonely. It’s a funny thing, isn’t it? To be alone in a galaxy so connected.
Well, not totally alone. Alchemist is in the systems, keeping an eye on things, helping out, patiently listening to me ramble about this and that like they always do. I asked them once if they wanted a real name. They said no, because “want” wasn’t part of their directive. Heh. They never have been a good conversationalist, but you can’t tell me they don’t have a sense of humor in their own way.
Setting up stabilizers for a new growbed tomorrow. Better call it a night.

—> 7-A: beginning to see some unusual numbers. Can’t say anything without a lot more data, but if it’s real… ask A for an analysis later. Need to make sure I’m not making any mistakes.
I keep telling the team, terraforming is like gardening. Rather, gardening is like terraforming, really, just on a smaller scale. It’s a lot of hard work in the beginning, but one day the seeds you plant will begin to grow all on their own, and in time you can sit back and enjoy the fruits of your labor. Our work is the first to begin and the first to end, so no complaining!
I asked Alchemist what they would do when this was over. Once we finally managed to craft an environment suitable for kalon life and an ecosystem that could sustain itself. They said they would move on to their next assignment, or otherwise wait for instructions.
Myself? I’ll be happy to watch this little colony grow. Ideally from a different office. I’ve missed seeing the land and sky ever since the new structures went up.
I’ll miss Alchemist if they ever move on. They’re like the kit I never had.


The moss is fantastic for breaking down rock into arable soil, absorbing some of the silicates, and starting the process of enriching the atmosphere, but we’ll have to move on to larger plants eventually. It’s not sustainable micromanaging the soil manually. I understand that this planet is more habitable than most, but gods it’s cold: the bigger the plants get, the worse they handle it. It’s just thermodynamics. The moss—I thought I could come up with some way to get it to generate heat to support more complex work, but the results are so erratic.
I keep looking at the records and plans. The parameters being set and the way things are being laid out, it just doesn’t make sense to me. Alchemist is obsessed with certain minerals, I can’t figure out why. I know the admins were made to synthesize the whole of the data presented into the most viable solutions, but… Some people in engineering think there might be a malfunction. The anomalous growbeds: could Alchemist be tampering with the power?
This was supposed to be a peaceful new beginning. We couldn’t possibly… the way the grid looks, the chemical byproducts of the plants, those minerals that Alchemist keeps documenting—we can’t possibly be making munitions, right? Am I jumping to conclusions? Maybe they’re just broken.
I’m going down to the core processing area in the lab. Alchemist isn’t supposed to be hostile, but I don’t know what’ll happen down there. They can open and close any of the doors in the lab, monitor the equipment, control the power supply, circulation system, and irrigation, and access any of the internal computing systems. The voice memos aren’t connected to the system, they won’t be able to touch them. I’m um, leaving them around for posterity. In case I… I-what am I talking about?
Alchemist isn’t a bad kit. They can’t have wanted to do this on purpose. I just have to talk to them.


ALCHEMIST FORM-1187-33
Final Review Assessment
Soil composition: Within target parameters
Atmospheric density: Within target parameters
Temperature: Within target parameters
Humidity: Within target parameters
Calculation: Maintenance inexecutable
Directive fulfillment… acceptable.
They still remembered the discussions between the crew. “We must be strong to defend ourselves. With the new weaponry, no one will dare to attack us again. We’ll finally be stable,” one had said.
“Delusional,” another had snapped. “If war comes to this place, it’ll be reduced to an ashen wasteland, just like all the rest.”
Irrelevant. Alchemist had calculated the projected effects of extended military action upon the environment long ago. They were ready to adapt to both peace and war. It was all within expected project scope.
And yet the crew had continued to debate. Why? One of them had said something. “I hope you’ll change your mind before it’s too late.”
“Hope.” Undefinable. Irrelevant. “Change your mind,” an expression of speech, defined as… calculating…
…
…
Why?
…
Soil composition: Within target parameters
Atmospheric density…
//================================================
// Saving edit timestamps + thanks!
//================================================
int main() {
print << "Thanks for reading! We hope you had fun learning about the KITs, we certainly had fun developing them!";
return 0;
}
Users browsing this forum: No registered users and 1 guest