(Warning: written in the throes of a PF-hacker's high)
Greetings, all.
So, it's come to my attention that CCP did a little ...
narrowing ... of the prime fiction surrounding clones. Used to be we could all just merrily swan about shooting each other in bar fights and rely on the not-quite-not-PF device of the backup, or "soft clone."
I even seem to remember a CCP PF-maven being asked about it at some point and basically going "Eh, sure."
No more, evidently.
"The possibility looms that cloning may at some point take place outside the strictures of a capsule or a similar machine, though it's considered unlikely that it will ever be anything other than instantaneous."
IE, no putting human brain scans in cloud storage and no we don't care whether you can afford the storage space.
... Never mind the CEO of Zainou Biotech. Ignore him. He's crazy anyway.
And yet! And yet, there is still hope. Even without giving CCP the proverbial bird, we may yet be able to acquiesce to dramatic, gruesome, and possibly deserved out-of-pod demises at the hands of our fellow infomorphs without having to push the biomass button.
The method is simple: make it a little ...
evil.
Our dear authors, you see, went to great lengths to make the cloning process dark and gritty, but neglected to consider the possibility of cloning with one sending station, but multiple receivers. Naturally, creating multiple active copies of a single mind is apt to be highly illegal (might be worth going into this elsewhere). But nobody ever said they all had to be active.
Not all of these receivers need attach to clones that will ever wake up.
Let's say you set up a rig for a standard jump-clone contract, but, for a fee, you also offer a bit of "insurance." Instead of transferring to one new body, the client's consciousness is transferred to two-- one of which is kept at a secure location in a medically-induced coma. This clone need not possess arms, legs, or even the ability to survive unaided. Nor does it need to be repeatedly written to-- it can simply be disposed of and replaced each time the backup is updated.
When the time comes (confirmed death of the client, a particular time without contact from the client, whatever), the cloning agency simply executes a jump-clone type scan from the "backup," thereby restoring the capsuleer to life, naturally missing any memories that might have accrued since the backup was last updated.
Poof. Back you come.
This has the handy side effect of validating the various otherwise contradictory bits of PF that indicate that killing an out-of-pod capsuleer is just as futile as killing one in-pod, and the further handy quality of sticking to the PF's grimdark intent.
So. Thoughts?