Proposal: Initialisation Key Resilience
Reaches quorum 5-0 and is enacted -SingularByte
Adminned at 30 Jul 2023 10:29:36 UTC
Create a subrule of Machinist Agendas called Known Initialisation Keys with the text:
Initialisation Keys include:
Coal, Housing, Valves, Facilities, Power, Function, Damaged Parts, Repair Log, Destroyed, Graffiti, Flea Market, Lockdown, Components, Surroundings, Destination, OrderAny machinist may bold any instance of these listed Initialisation Keys anywhere in the dynastic ruleset.
In the rule Machinist Agendas, if there is a bullet point starting with “Initialisation Keys may not be”, replace that bullet point and the next one with:
* Machinists must not remove all instances of a given Initialisation Keys from either the rule Known Initialisation Keys, or from the rest of the dynastic ruleset.
An alternative to Key Punch. Now we don’t have to worry about accidental unboldings and can freely move keys around or consolidate copies of them when useful to do so, but without the implication that you’re free to just start deleting as many as you want.
Kevan: Concierge he/him
Not sure this works. Isn’t the problem that if we carelessly unbold a Key it stops being one and “The text string of an Agenda must include exactly 2 different Initialisation Keys.” will cause all Agendas with that word in them to reset to blank? This proposal allows us to re-bold the word, but the Agendas will have already imploded by that point, it won’t bring them back.
“The text string of an Agenda must include exactly 2 different Initialisation Keys.” seems like the crux point, and should probably be removed, or amended to “When created…” - we know that the existing Agendas must all have two Keys, and the only possible future ones are Reserve Agendas from the Emperor.