Tech as Drama: Urbot Erasure

The Guild of Engineers owns the patent on Urbots. They require all Urbot owners to bring in their Urbots once a year for core maintenance. However, between the availability of Guild outposts and many Urbots being on far-traveling ships, this doesn’t always happen. During the tune-up the Guild wipes the AI core, resetting most of the memories and personality and restarting the Urbot from scratch.

Let’s try some assumptions and see where this takes us…

  1. The rich and powerful will want to use Urbots, as they’re convenient and (probably) cannot be bought off, the way human servants could be
  2. This includes anyone involved in criminal dealings
  3. It follows that an Urbot will probably be around for, and hence remember, shady dealings or sensitive business intel its owner(s) engage in
  4. If the Guild of Engineers can wipe a bot, they can probably access its memories as well
  5. It follows that the Guild can effectively spy on powerful Urbot owners
  6. The people at risk of this happening both know it’s possible and don’t want it to happen

There’s several directions for this to go. Guild Engineers can allow themselves to be bribed, ignoring incriminating evidence on an Urbot in exchange for a cut; powerful Urbot owners end up forging records of having wiped their bots (if they’re okay with a sentient bot, and maybe they are?); rogue Engineers or smart third-party techies do the work; such Urbots get destroyed, rather than wiped (this feels like a pretty serious or expensive thing to do, though).

Resulting plots:

  • We need info about a big-wig’s previous criminal dealings. Go find the Engineer(s) who serviced their Urbots and get them to talk.
  • It’s maintenance time! Impersonate the Guild’s couriers and steal someone’s Urbot.
  • Arrange for someone’s Urbot to be damaged, then intercept it (or shake down an Engineer) when it’s sent for repair.
1 Like

For our particular scenario, maybe the late lamented Windham Orcutt had an Urbot, and to find out what his deal was, we have to go nab it - get past his security, deal with the cranky bot itself, and find a rogue tech who can access its data (or our high-Attune, high-Rig PCs cooperate to do it themselves).

1 Like