Secborg Taser justification
Posted: Sun Dec 11, 2022 1:44 am
With the newest release of C.I.V.I.L. RIGHTS software tasers have been reintroduced to Cyborgs. It has simply changed into a 5 step process to make sure every shot is justified.
1.First time after selecting a taser and click on a criminal, you get a text prompt (which is a C.L.E.R.Y. Act approved line) reporting over the main radio what crime you are attempting to pursue the person you are targeting over.
2. (optional) Second time the criminal is pressed on, it repeats over security the crime from the first text prompt, the name of the room the borg is standing on, and the name of the criminal again, be it Captain Johnson, Unknown or Spacedragon.
3. Warning shot. Third time the cyborg has to click anywhere but the criminal, but shooting the cell in front of the criminal is allowed. When firing the warning shot, the cyborg sends out a message warning the criminal from step 2 to empty their hands and lay down, and accept police custody.
4.Real shot. 5 Seconds after a warning shot, a real shot would be enabled. This cannot be used to target someone who is laying down. This shot is targeted at the criminal, and is intended to allow the borg to get the target in cuffs.
5. After action report. All the messages generated by the previous steps, and the location data of step 4 are put on a text box on the AI's UI, reviewing the facts of the shooting, and giving the AI to approve or deny the next attempted shot at this target, as well as deny all further taser usage by the borg. That option is only available to Borgs slaved to the AI though, free borgs play by their own rules (and by that I mean the AI has to manually deny each of their action reports, and only allow that borg to have 1 shot on each named person). After action report could basically serve the function of saying this is what your laws are, this is what the facts of the case are, do you approve or deny that the borgs actions fell within those parameters, and therefore subsequently approve or deny them shooting at this person again in connection to said crime.
I understand this would probably be infeasible to code, but is an example of mixing LRP and MRP.
1.First time after selecting a taser and click on a criminal, you get a text prompt (which is a C.L.E.R.Y. Act approved line) reporting over the main radio what crime you are attempting to pursue the person you are targeting over.
2. (optional) Second time the criminal is pressed on, it repeats over security the crime from the first text prompt, the name of the room the borg is standing on, and the name of the criminal again, be it Captain Johnson, Unknown or Spacedragon.
3. Warning shot. Third time the cyborg has to click anywhere but the criminal, but shooting the cell in front of the criminal is allowed. When firing the warning shot, the cyborg sends out a message warning the criminal from step 2 to empty their hands and lay down, and accept police custody.
4.Real shot. 5 Seconds after a warning shot, a real shot would be enabled. This cannot be used to target someone who is laying down. This shot is targeted at the criminal, and is intended to allow the borg to get the target in cuffs.
5. After action report. All the messages generated by the previous steps, and the location data of step 4 are put on a text box on the AI's UI, reviewing the facts of the shooting, and giving the AI to approve or deny the next attempted shot at this target, as well as deny all further taser usage by the borg. That option is only available to Borgs slaved to the AI though, free borgs play by their own rules (and by that I mean the AI has to manually deny each of their action reports, and only allow that borg to have 1 shot on each named person). After action report could basically serve the function of saying this is what your laws are, this is what the facts of the case are, do you approve or deny that the borgs actions fell within those parameters, and therefore subsequently approve or deny them shooting at this person again in connection to said crime.
I understand this would probably be infeasible to code, but is an example of mixing LRP and MRP.