jann wrote:
Cassandra wrote:
The rules text, examples, commentary and spirit say that a group is considered "alive", if a permanent stone of its colour can be positioned on the board AFTER the group has been captured.
You are free to invent new rules, but J89 enable doesn't work this way, even among the official examples.
Quote:
In contrast, the disappearance of Black's group at the left "enabled" nothing.
Black is always free to fill his own territory. Nobody can prevent him from doing so.
The right side was not B territory, especially the intersections with big W seki string. Even with your incorrect interpretation, B can play new alive stones (even AFTER the capture of his left!) on the right at intersections where he could not have played at originally, if W haven't tried to capture his left. So even with the (nonexistent) timing constraint you logic doesn't work here.
jann,
I did not invent new rules.
But YOU will have do make up your mind:
If you wanted to consider L&D globally, you would have to also accept "enable" globally.
If you wanted to have "enable" only locally, you would have to consider L&D also locally. And in this case, Black's group at the left would be more than dead outright.
And I do not think that it is so very surprising that capturing something would enable you to occupy points that you were not able to occupy before. If you liked this idea of yours, you could turn everything on the board "alive" that could, but yet has not been, taken off the board.
If you are able to occupy the SAME points at the right before AND after Black's group at the left was taken off the board, this occupation is completely independent from what happened at the left. Just filling your own territory, for what reason ever.
------------------------------------
What is the reason that you do not like the result at all?
Would you have wanted anything else but "Black at the left is dead; at the right, there is a double-ko seki"? If so, what?
_________________
The really most difficult Go problem ever:
https://igohatsuyoron120.de/index.htmIgo Hatsuyōron #120 (really solved by KataGo)