Monday, May 12, 2025

Proposal: Blind Spot

Popular, 6-1. Enacted by JonathanDark.

Adminned at 13 May 2025 14:12:54 UTC

In “The Break-In”, replace “If the Spot at that position in that Agent’s Route has an Extra Spot that is Connected to it” with:-

If the Spot at that position in that Agent’s Route has an Extra Spot (at that position in that Agent’s Route) that is Connected to it

Uphold the Concierge’s attempted performances of the “If the Spot at that position in that Agent’s Route has an Extra Spot” steps in the Break-In Action they undertook on the 10th of May.

Enact a new rule, “Room Service”:-

At any time the Concierge may update the Fame, Infamy and Successes of Agents to the values they would currently have if the most recent Break-In action had instead been processed under the interpretation that “has an Extra Spot that is Connected to it” included Extra Spots set by other Agents, and then repeal this rule.

The Concierge may not perform any dynastic actions outside of this rule while this rule exists.

As discussed in comments on What Happened Last Night, the Extra Spot step of Breaking-In is ambiguous. Its presumably-intended reading is that each Extra Spot only applies to the Spot at the same point in the same Agent’s route; I read it more literally and interpreted it as applying to all Spots in that Agent’s route; Clucky points out that if read literally it should actually apply to all Spots in all Agents’ routes.

This amends the Extra Spots step to explicitly reflect its spirit, and reruns the Break-In under the most literal interpretation of it, if my attempt at a literal interpretation was insufficiently so.

Comments

DoomedIdeas: he/him

12-05-2025 15:45:47 UTC

for

Clucky: he/him

12-05-2025 16:01:41 UTC

against upholding how it was run doesn’t seem right to me. unfairly gives the win to the guards.

Trapdoorspyder: he/him

12-05-2025 16:03:20 UTC

for

Clucky: he/him

12-05-2025 16:11:29 UTC

Kevan previously ran extra spots under the intended wording despite extra spots not having positions, so I really don’t understand why we’d want to switch to hyper literal interpretations now.

Clucky: he/him

12-05-2025 16:12:52 UTC

Also would still be nice to allow https://blognomic.com/archive/did_someone_call_shenanigans to fully resolve and allow us to get to the bottom of what really happened before we uphold the breaking in

Kevan: he/him

12-05-2025 16:21:02 UTC

The first three Break-Ins were upheld by a CfJ, so any literal reading from here would regard them as valid.

The uphold in this proposal is to allow the Break-In to be unambiguously closed, given that there’s some disagreement over whether I legally completed it. The actual Success counts get updated by the reassessment action, which may or may not resolve differently.

You’re welcome to propose a further “reassess Break-In #4 outcomes as if Extra Spots only applied to specific Spots” review instead of or on top of this, if you think that a quorum would support applying the Extra Spot fix retroactively.

Clucky: he/him

12-05-2025 16:29:46 UTC

People are going to play the game in a way that assumes the ruleset will get interpreted in a consistent manner

Previously, the way you ran the break-ins showed you thought there was enough context to make it clear it applied to the specific agent’s route. To me, that means if we also add a clause about position there is still enough context to make it clear it also only applies to that position.

JonathanDark: he/him

12-05-2025 17:18:32 UTC

I’m planning to withhold my vote until https://blognomic.com/archive/did_someone_call_shenanigans fully resolves.

ais523: Supervisor

12-05-2025 17:51:48 UTC

for

Kevan: he/him

12-05-2025 17:55:03 UTC

[Clucky] There’s also the higher level consistency of always interpreting the ruleset literally, which is what I was aiming for in choosing which way to jump here.

Players are also welcome to propose “don’t reassess Break-In #4 after all, revert any change made by Room Service” if they think a semi-literal reading is the best way to go.

Clucky: he/him

12-05-2025 19:13:31 UTC

@Kevan When its not consistent with how previous rounds were run, feels like that is an incredibly unfair way to run things

Darknight: he/him

12-05-2025 22:18:39 UTC

for

Kevan: he/him

13-05-2025 07:57:24 UTC

[Clucky] That you characterised the middle reading as “100% wrong” in your comments on What Happened Last Night suggested that I should pick one of the other two interpretations.

JonathanDark: he/him

13-05-2025 14:12:08 UTC

for