Friday, July 28, 2023

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, Order

Any 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.

Comments

Kevan: City he/him

28-07-2023 21:30:35 UTC

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.

SingularByte: he/him

28-07-2023 21:43:07 UTC

That’s what the first half of the proposal is for; it creates a list of them that’s outside of any rule that people would have reason to modify, and specifically disallows you from removing them from it. That way, even if you manage to delete each and every other version of the key, it has this one to fall back on.

Admittedly I forgot to bold them in that rule, so I’ll just do that now.

lemon: she/her

28-07-2023 22:32:41 UTC

for

lemon: she/her

28-07-2023 22:33:01 UTC

oh — that was a bit early, i just realised. i’m sorry!

Bucky:

28-07-2023 22:36:57 UTC

for

JonathanDark: he/him

28-07-2023 23:04:18 UTC

for

JonathanDark: he/him

29-07-2023 02:36:58 UTC

I just realized that the Brevity rule is going to automatically make this Unpopular. Sorry…it just occurred to me today.

SingularByte: he/him

29-07-2023 08:56:43 UTC

I don’t believe it does get hit by brevity? The two bullet points it removes represent a good chunk of characters, which offsets the additions.

JonathanDark: he/him

29-07-2023 13:55:12 UTC

You’re right, my mistake. I forgot to count the removal of those first two bullet points.

Kevan: City he/him

29-07-2023 18:10:38 UTC

for