jann wrote:
Cassandra wrote:

"Double-ko loops", i.e. an alternation between a double ko capture and a double pass-for-ko for these ko, are forbidden.
This one is pretty obvious. Just a side effect / oversight of formalization, which - as is - would break way too many things.
Probably you have already noticed that I edited my posting above.
The previous

is now

(prohibiting triple-ko cycles was an idea to make the ko-ban for simple ko superfluous), re-worded to "The completition of a double-ko cycle is forbidden."
Probably you want to reconsider your demand for such a prohibition.
Getting rid of a cycle means that the
terminating move of that cycle has to be forbidden, NOT the initiating one.
I am sure that you will not like the resulting consequences.
Why the
terminating move?
Choosing the INITIATING move for that purpose would have the following consequences (among others):
-- Application case "simple-ko": You must not capture into any ko shape.
-- Application case "double-ko": You must not capture into any double-ko shape.
J89 shows several sequences of capturing into a double-ko shape. Thus, getting rid of that cycle cannot be intended.
#####################################
Apparently, the impact of a ban for
every single-ko onto a double-ko flew under the radar of the J89 authors. But the features of a double-ko were changed dramatically.
During "play", it is the player who captured the SECOND ko, who has the priviledge of recapturing first.
If he does, the priviledge for the next cycle switches to the other player.
This implies that a double-ko (seen in isolation) during play is a 50:50 issue.
During this cycle, both players played one move each elsewhere.
But during "status confirmation", it is the player who captured the FIRST ko, who has the priviledge of recapturing first.
This implies that a double-ko (seen in isolation) has become a 100:0 issue.
During this cycle, no move is played elsewhere, what makes an endless repetition possible.
If there is NO endless repetition, the double-ko has effectively disappeared.
It is evident now that Robert's one-pass-for-all-ko-bans in J2003 eleminated that difference between "play" and "status confirmation" for the application case "double-ko".
_________________
The really most difficult Go problem ever:
https://igohatsuyoron120.de/index.htmIgo Hatsuyōron #120 (really solved by KataGo)