Skip to main content

Virtual characterization before real colonization. A glimpse at how sentient variants will people the stars.

The year is 2560,

A colonization star ship is on its way to a planet in the Trapezium open cluster in the Orion Nebula...discovered over a hundred years earlier. It was characterized to detail a few years later via autonomous systems.

The planet was found to be not quite human 1.0 habitable...but we weren't going to be sending human 1.0's there.

See in 2560, gene editing has been a routine and common practice in human populations going back 540 years. Humans have been thus able to radically conform themselves and their flora and fauna to the environs often far more inhospitable to human 1.0 life than Mars.

Evaluation of a trip to Orion Trapezium planet beta3 had been a 10 year affair once it was stamped as worthy of exploration. 10 years ago in 2350, most people hadn't heard of the system this point in time there are several billion recorded and characterized exo planets and humans have only gotten to a few dozen of them with our advanced but sub light drives.

One of the first steps for exploration plans for new planets is virtual characterization.

In 2550, virtual reality has achieved levels of cognitive integration that would seem like magic to us today. Rather than wear goggles and gloves 2550, virtual experiences are beamed into our brains and bodies using advanced modulating beams that allow us to go into an "inner sleep".

Construction of virtual experiences then proceed via this non invasive cognitive modulation. ESA not only trains interstellar astronauts using these systems but designs and builds the tools and equipment that will be used on a target planet.

Since beta3 had been fully characterized we knew everything about it's surface conditions, atmospheric gas percentages and geological formations. It was sort of like a planet Venus just a bit before the runaway green house took effect so like Venus was in the 2450's could be terraformed and harnessed readily.

Teams of astronauts would go into inner sleep and live on the virtual planet...these astronauts would not be the ones to actually visit the planet....those guys would be genetically enhanced to deal with the initial planetary conditions...or if the conditions were not to extreme could actually be designed to fit the planet ....since transexospermia had been embraced as a valid means of propagating Earth genetic information to remote worlds...even if the genetically "fitted" life forms propagated dramatically departed from what human 1.0's required to survive.

The world had thankfully four centuries ago, shed it's vestiges of bias regarding the equivalence of all sentient cognition regardless of substrate. On the trip to beta3 would be humanX.0's, enhanced helper species (genetically advanced dogs , bears mostly) plain old sentient Androids and even some human 1.0's all working together to ensure the planet could be properly "harnessed" for the needs of at least several populations of Earth sentients.

The particular qualities of beta3 made it open for colonization by multiple sentient forms explaining why so many varieties were involved. In the last 500 years such planets are rare...which the bulk of harnessed systems requiring either all of one type or another (though the Androids being mostly non bio tended to always accompany what ever enhanced biogenetic sentient that was conformed to the target planets environs).

All the details of harnessing the planet were figured out and tested in virtual inner sleep and then 3D printed on the edge of the solar system using materials mined from the ample distal mining facilities dotting the outer dwarf planets.

This star ship in fact was on it's way from Sol System Egress base 5 on Pluto and had been in transit for the last 35 years (ship time). A blink of an eye for all of the sentients on board which being all super mortal did not concern themselves with the 20th century fears of limited life span due to progressing senescence!

What a time of darkness that must have been!


Dom Saint-loth said…
This is the prologue for a scifi novel? If not, it should be...

Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…