This is something I cooked up for my campaign before finding Arenamontanus' underground railroad article (which should mesh with this material relatively easily).
Comments, questions and criticism are welcome.
%%%%
Some hypercorps and many criminal cartels run real slavery operations. They can vary in form from wholly-virtual "digital sweatshops" to fully physical. What is common to all of them is that the operators do not offer any pay or compensation or do not intend to follow through with their promises. Some use psychosurgery to instill "slave mentality" on their victims while others offer reasonable (or even lucrative) salaries/payoffs and betray their workers in the end. In latter scenario it's common to delete the egos, reboot an older backup and put it back to work; this is known as "groundhog day loop" or "cookie monster loop".
Planetary Consortium officially condemns slavery as any other position would be utterly unpalatable to the public opinion which considers indenture dubious enough. PC makes lot of propaganda pointing to slavery cases and basically saying "Indenture is not slavery. This is real slavery and we don't tolerate it".
Getting caught running such operations is punished heavily: More than one criminal hypercorp has been dismantled and it's management permanently executed for such crimes. PC Oversight takes these cases seriously, nobody doubts that. And let's not get into what sorts of punishments and virtual hells anarchists and extropians have cooked up for clowns who get caught running these sorts of operations...
Most autonomists hold the cynical view that PC cares more about market distortions and "unfair advantage" caused by such operations than the actual slavery and that the only reason PC doesn't endorse this sort of real slavery is that it would start an instant revolt. The Accuracy of these assesments remains unknown.
While Firewall considers these sort of things as reprehensible, they're usually not existential threats; SOP is to anonymously tip off the relevant authorities and move on to more important matters. Of course, nobody is going to raise any fuss about a small and discreet pro bono job if there isn't anything more important going on.
Adventure seeds:
*Player Characters meet an indentured acquaintance who doesn't remember them at all. There isn't any backup restoration in his record since his resurrection and indenture, but you clearly remember tossing few beers with him in that isolated mining operation while smuggling those nanofab blueprints...
Recommended reading: Vernor Vinge's The Cookie Monster. The Scenario in this novella should be very easy to insert into any Eclipse Phase campaign with minimum tweaking.
Welcome! These forums will be deactivated by the end of this year. The conversation continues in a new morph over on Discord! Please join us there for a more active conversation and the occasional opportunity to ask developers questions directly! Go to the PS+ Discord Server.
Slavery in Eclipse Phase
Wed, 2010-08-25 14:11
#1
Slavery in Eclipse Phase
root@Slavery in Eclipse Phase
[hr] What does the Planetary Consortium think about this exact scenario when all of the slaves are forks of the person running the "sweatshops"? The answer to that question has very heavy implications for what is legally considered a "person" in the Planetary Consortium's domain.@-rep +1
|c-rep +1
|g-rep +1
|r-rep +1
]root@Slavery in Eclipse Phase
[hr] There are limits to how many forks will help a given task. Any computational task can be broken down into parallelizable processes and non-parallelizable tasks. Once there are enough forks working to cover the total parallelizable task domain, the rest are redundant. Also, there is no need to merge a fork at the end of the day. Suppose an intelligence named Adam is a particularly artistic simulspace designer, whose sculpted terrains are celebrated in all of the system. But little does the public realize that Adam almost never does any direct work on his simulspaces. In the beginning, Adam got a really powerful computer with gobs and gobs of storage, and a processor so powerful he nicknamed it "Arete". Adam makes an alpha in his image, and assigns it the task of filling the processor with an abundance of betas, who are further set to multiplying deltas. After some time, Adam will call this good, and reassign his army of deltas to specific tasks. The deltas are managed by the betas who answer to the alpha. They run in a x60 simulspace, and copy themselves into storage once per second, and work the rest of the time. The betas flag any sufficiently interesting and new skill development in the deltas, which is passed up to the alpha if it is something Adam might be interested in learning. Adam studies it, and has the alpha learn it as well. There is now a rate limit based on how fast the prime can absorb the new material learned by the deltas. We can speed this up by having Adam learn by merging. Mental trauma can be minimized by spinning of a large number of copies of a delta with the new skill, and a large number of betas to learn the skill. Keep merging until you get a pile of them that aren't crazy. Do this again with the betas and the alphas until you have a non crazy alpha that is a recent copy from Adam. Reintegrating with an alpha that has been out for less than a day isn't so bad, so Adam has now reaped the skill learning of one of his army of deltas. The probability of mental damage can made arbitrarily small using this method.@-rep +1
|c-rep +1
|g-rep +1
|r-rep +1
][img]http://boxall.no-ip.org/img/A_Rep.jpg[/img] 2 [img]http://boxall.no-ip.org/img/R_Rep.jpg[/img] 7 [img]http://boxall.no-ip.org/img/C_Rep.jpg[/img] 2
[img]http://i.imgur.com/qtBZ9.jpg[/img]
[img]http://i.imgur.com/AT25J.jpg[/img]
+1 r-Rep , +1 @-rep

