@Woodrow_Ormand; no known instance of Drifter mind-napping or similar thing has occurred since the probable case of Hilen Tukoss. Neuromemetic intrusion is suspected in one case but unconfirmed, on the suspicion of neuromemetic warfare capacities for certain retrieved data structures. Work is on-going in this area, and is one of the reasons why we’re fairly certain we can prevent contamination, if it’s even a risk; essentially, we have experience, and the threat seems overstated. Of course, it does merit mentioning that much of this work is predicated upon verification and deployment of methods of data control and infomorph data transfer safety. However, we’re not going in dumb, equipped with only duct tape and baling wire, as the line goes.
Please understand that your initial statements posited our plan was unethical for a behavior we weren’t entertaining in the slightest. Since then, your apparent rationale for calling ARC’s actions unethical has seemingly changed. From my perspective, it’s almost as if you’re actively trying to construct arguments for why “ARC is bad and we should feel bad.”
Very simply, it’s because of this seeming rationale that why we often try to ignore you.
To elaborate on matters of ethics in infomorph personnel useage: all personnel will be made fully aware of all risks involved in any operation and provided appropriate compensation. Risks include euthanization of contaminated clones. However, we believe that establishment of a soft clone-style methodology for clone soldiers is not only possible, but readily achievable. We also believe that use of infomorph personnel for this operation will significantly reduce the risk of loss of life, provided that drones remain a probably ineffective solution for more than mapping or simple transport work, and that baseliner personnel remain significantly more exposed to the risks of the operation.
Essentially, it boils down to this: is it unethical for adequately informed and compensated personnel to voluntarily take risks? I would say no, it’s perfectly ethical on that basis.
@Kador_Ouryon; a life of peace sounds lovely, though perhaps not one all of us are able to achieve. Best of luck to you on your path.
@KnightGuard_Fury; hello! Please be aware that while the specifics are not usually well-known to capsuleers, ARC has a solid working familiarity with incremental mindstate transfer technology and the underlying cybernetics, likely better than most Capsuleer organizations, though certainly second to dedicated biotech concerns and naturally clone soldier organizations. It is for this reason that we’ve solicited response.
Without getting too deeply into the weeds, to give a working overview to demonstrate familiarity; incremental mindstate transfer technology is just that. The control architecture for the implant network is commonly described as a new lobe primarily replacing the thalamus, hippocampus and brainstem, from which it regulates consciousness, short term and long term memory formation, and most sensory and ambulatory functions. Incremental mindstate updates are transferred from the clone as experiences occur and skills are developed, essentially ‘streaming’ a changing consciousness to command infrastructure using difference files, versioning the backup. The clone soldier or Sleeper implants are incompatible with baseliner clones as a working architecture requires that the clone be essentially ‘grown’ with a cavity where the implant technology is inserted in later stages. As an aside, Drifter implant architecture is usually added as an addition to existing Sleeper implant infrastructure.
Please note that when I say ‘soft cloning,’ it’s a short-hand, not a technical proscription. As we both know, the technical differences in architecture prevent employment of identical methods. While something like a TEBS could possibly be devised to operate on those using Sleeper-derived implant technology, there’s simply been no point, and it seems like an excessive redundancy, unless someone’s thinking to use it for intelligence purposes, and even then it’d require intact retrieval of the brainstem implant anyway.
Now, I understand the useage of Capsuleer terminology is a jarring one for a clone soldier, but you already have a system that mirrors the operation of this. We just intend to be much more direct about it. Essentially, my understanding is this: incremental mindstate transfers don’t go to a fresh clone directly, but instead to databanks, usually aboard war barges, and are then burst-transmitted to MCCs or CRUs where they are uploaded into a waiting, fresh clone. My impression at present is that MCCs and other CRU infrastructure doesn’t use the irradiating wormhole-like technology of drop uplinks, which essentially function as ground-based cyno/bridge networks, untenable for use by baseliners who don’t have a death wish.
The notable thing, of course, is that the implant architecture doesn’t use entangled communications, but is instead via the usual local methods, not unlike fighter pilot cloning methodologies though clearly far more reliable.
So, when I say clone soldiers use an existing technology, it’s essentially this: that central clearing house for clone soldier consciousness transfers remains active even in cases when the clone soldier leaves transmission range. In such cases, it’s my understanding that the clone soldier is tagged as ‘MIA,’ and a fresh clone may be decanted with the most up-to-date infomorph, whether or not the clone soldier has been verified as being dead. Essentially, this mirrors soft-cloning technology in being able to preserve personnel despite unforeseen circumstances, but if anything is more flexible given that the infomorph backup is constantly being updated, whereas soft clones require a time-consuming and not inexpensive process.
Now, I’d been given to believe that while this isn’t expressly used to provide volunteers the ability to ‘back themselves up’ if necessary for an operation, it is a technology that is not unusually employed in the rare circumstance that a backup is needed.
Am I mistaken?