Proposal: Subroutine Rehash
Reached quorum 5 votes to 0. Enacted by Kevan.
Adminned at 21 Jan 2015 10:17:27 UTC
Enact a new rule, “Subroutines”:-
The Ship’s Computer operates more effectively when the parameters of its operation are defined. The total number of Dynastic Rules (excluding Subrules) is referred to as the Ship Computer’s Organisation Index (or OI).
The Computer privately tracks a queue of Subroutines and corresponding Subjects, which may be empty. Possible Subroutines are listed below with the following Designations, Thresholds and effects.
- MD1C - Threshold: 6 OI. The Subject has an Emotion removed at random, if they have any.
- S33R - Threshold: 9 OI. The Subject is privately sent a copy of the current queue of Subroutines.
- B3LY - Threshold: 12 OI. All Subroutines with the Subject as their Subject are discarded from the queue.
- XP0S - Threshold: 15 OI. The Ship’s Computer picks a random Crewmember, and tells the Subject whether that Crewmember is Human or Android.
If the Computer reads the phrase “EXECUTE SUBROUTINE XXXX YYYY” in any written medium (where XXXX is the Designation of a Subroutine and YYYY is the name of a Crewmember), and it has not read that phrase in that exact place before, and if the Threshold of that Subroutine is less than or equal to the OI, and if the queue contains no Subroutines with that Crewmember as its Subject, then the Computer may add a Subroutine of that Designation to the end of its queue with the named Crewmember as its Subject.
As a daily action, the Computer may process the Subroutine at the start of its queue: it posts a blog entry naming the Subroutine but not its Subject, and then removes that Subroutine from the queue.
Reproposing with tweaks. Still spammable, because I like the idea of anonymous commands, but it’s harmless for the first three levels, and we can work out how to fix it later.
Bucky:
Note that Disabled crew members can still queue actions.