Using the Commentary and the L&D-Examples, I will try to find out what the IMPLICIT Japanese understanding of the intended application of Article 7 of J89's legal text is (and what -- according to Western understanding -- should have been EXPLITELY described).
Commentary
7.1.U-type of stones
Alive stones =
A) Two solidly connected eyes.
B) Large eye that can be divided (=> A), even if the opponent plays first.
C) Not solidly connected eyes (at least two).
D) Filled large eye as a seki.
Implicit understanding:
Fencing stones (not marked here in the diagrams for the sake of clarity) are considered to be of the 7.1.U-type.
7.1.C-type of stones
Alive stones =
A) B) C) Uttegaeshi's (aka "snap-back") potentially captured stones.
-------------------------
NOT SHOWN: Move sequences.
Implicit understanding:
Presupposed basic knowledge?
Implicit understanding:
Stones that could be re-established in total because they were previously captured, are of the 7.1.C-type.
Total re-establishment will result in territory.
-------------------------
NOT EXPLICITLY mentioned: Nakade.
Implicit understanding:
Presupposed basic knowledge?
Implicit understanding:
Stones that could be re-established in total because they were previously captured, are of the 7.1.C-type.
Total re-establishment will result in territory.
7.1.D-type of stones
Dead stones =
A) B) C) Uttegaeshi's (aka "snap-back") potentially capturing stones.
Dead stones =
D) Large eye with nakade.
E) One solidly connected eye & one false eye.
F) One not solidly connected eye & one false eye / two false eyes / one solidly connected eye.
-------------------------
NOT SHOWN: Move sequences.
Implicit understanding:
Presupposed basic knowledge?
J89's Article 7 (L&D):: Reverse engineered
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
J89's Article 7 (L&D):: Reverse engineered
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 1
J89's judgement of L&D:
Black's four stones are of the 7.1.C-type.
White's single stone is of the 7.1.C-type.
Why ?
---------------------
NOT SHOWN: Further sequence.
Implicit understanding:
Presupposed basic knowledge?
Considered redundant?
Implicit understanding:
Stones that could be re-established partially because they were previously captured, are of the 7.1.C-type.
Partial re-establishment will result in seki.
Why ?
Implicit understanding:
Because White's single stone in the corner was previously captured, White could create permament stones of her "out-of-body", i.e. on board points that were NOT previously occupied by captured stones of her. Thus, her captured stone is of the 7.1.C-type.
Out-of-body creation of 7.1.U-type stones will result in seki.
---------------------
NOT SHOWN: Further sequence.
Implicit understanding:
Considered redundant?
J89's judgement of L&D:
Black's four stones are of the 7.1.C-type. White's single stone is of the 7.1.C-type.Why
?---------------------
NOT SHOWN: Further sequence.
Implicit understanding:
Presupposed basic knowledge?
Considered redundant?
Implicit understanding:
Stones that could be re-established partially because they were previously captured, are of the 7.1.C-type.
Partial re-establishment will result in seki.
Why
?Implicit understanding:
Because White's single stone in the corner was previously captured, White could create permament stones of her "out-of-body", i.e. on board points that were NOT previously occupied by captured stones of her. Thus, her captured stone is of the 7.1.C-type.
Out-of-body creation of 7.1.U-type stones will result in seki.
---------------------
NOT SHOWN: Further sequence.
Implicit understanding:
Considered redundant?
Last edited by Cassandra on Fri Sep 17, 2021 6:51 am, edited 1 time in total.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 2
J89's judgement of L&D:
Black's two stones are of the 7.1.C-type.
White's eight stones are of the 7.1.U-type.
Why ?
Implicit understanding:
Because Black's stones in the corner were previously captured (with
), Black could create (with 
) a permament stone of his "out-of-body", i.e. on a board point that was NOT previously occupied by captured stones of his. Thus, his captured stones are of the 7.1.C-type.
The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area".
Out-of-body creation of 7.1.U-type stones will result in seki.
---------------------
Misleading!
J89's comment on L&D Example 2 ALSO describes
as a "newly created stone that cannot be captured".
But has NOT been played AFTER White captured his stones in the corner.
So this should be an UNADAPTED RELIC of the initial version ("if capturing ... enables ..."; i.e. "if THE PROCESS of capturing ... enables ...").
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
J89's judgement of L&D:
Black's two stones are of the 7.1.C-type. White's eight stones are of the 7.1.U-type.Why
?Implicit understanding:
Because Black's stones in the corner were previously captured (with
), Black could create (with ) a permament stone of his "out-of-body", i.e. on a board point that was NOT previously occupied by captured stones of his. Thus, his captured stones are of the 7.1.C-type.The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area".
Out-of-body creation of 7.1.U-type stones will result in seki.
---------------------
Misleading!
J89's comment on L&D Example 2 ALSO describes
as a "newly created stone that cannot be captured".But
has NOT been played AFTER White captured his stones in the corner.So this should be an UNADAPTED RELIC of the initial version ("if capturing ... enables ..."; i.e. "if THE PROCESS of capturing ... enables ...").
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 4
J89's judgement of L&D:
White's stones are of the 7.1.C-type.
Black's stones are of the 7.1.U-type.
Why ?
---------------------
Misleading!
J89's sequence on L&D Example 4 ends with the position at left.
But NO White stone has been played AFTER Black captured her stones at the top.
So this should be an UNADAPTED RELIC of the initial version ("if capturing ... enables ..."; i.e. "if THE PROCESS of capturing ... enables ...").[/color]
must be added as an out-of-body stone that cannot be captured!
Implicit understanding:
Because White's stones at the top were previously captured (with
), White could create (with ) a permament stone of her "out-of-body", i.e. on a board point that was NOT previously occupied by captured stones of her. Thus, her captured stones are of the 7.1.C-type.
The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area".
Out-of-body creation of 7.1.U-type stones will result in seki.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
J89's judgement of L&D:
White's stones are of the 7.1.C-type. Black's stones are of the 7.1.U-type.Why
?---------------------
Misleading!
J89's sequence on L&D Example 4 ends with the position at left.
But NO White stone has been played AFTER Black captured her stones at the top.
So this should be an UNADAPTED RELIC of the initial version ("if capturing ... enables ..."; i.e. "if THE PROCESS of capturing ... enables ...").[/color]
must be added as an out-of-body stone that cannot be captured!Implicit understanding:
Because White's stones at the top were previously captured (with
), White could create (with ) a permament stone of her "out-of-body", i.e. on a board point that was NOT previously occupied by captured stones of her. Thus, her captured stones are of the 7.1.C-type.The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area".
Out-of-body creation of 7.1.U-type stones will result in seki.
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 5
J89's judgement of L&D:
White's stones are of the 7.1.C-type.
Black's stones at the left are of the 7.1.C-type.
Black's stones at the top are of the 7.1.U-type.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
in the corner already judged of being of 7.1.C-type in L&D Example 1?
Judging at the top left as an application case for the reader?
---------------------
Implicit understanding:
Because White's stones at the top were previously captured (with
), White could create (with 
) a permament stone of her "out-of-body", i.e. on a board point that was NOT previously occupied by these captured stones of her. Thus, her captured stones at the top are of the 7.1.C-type.
The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area".
Out-of-body creation of 7.1.U-type stones will result in seki.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
already judged of being of 7.1.C-type in L&D Example 1?
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
J89's judgement of L&D:
White's stones are of the 7.1.C-type. Black's stones at the left are of the 7.1.C-type. Black's stones at the top are of the 7.1.U-type.Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
in the corner already judged of being of 7.1.C-type in L&D Example 1?Judging
at the top left as an application case for the reader?---------------------
Implicit understanding:
Because White's stones at the top were previously captured (with
), White could create (with ) a permament stone of her "out-of-body", i.e. on a board point that was NOT previously occupied by these captured stones of her. Thus, her captured stones at the top are of the 7.1.C-type.The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area".
Out-of-body creation of 7.1.U-type stones will result in seki.
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
already judged of being of 7.1.C-type in L&D Example 1?Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
Summary 7.1.C-type stones
Subtype "Complete re-establishment"
Stones that could be re-established in total because they were previously captured.
Total re-establishment will result in territory.
Uttegaeshi => Commentary
Nakade => NOT explicitly mentioned
Subtype "Partial re-establishment"
Stones that could be re-established partially because they were previously captured.
Partial re-establishment will result in seki.
=> L&D Example 1
=> L&D Example 5
Subtype "Out-of-body re-establishment"
Because stones were previously captured, permament stones of that colour could be created "out-of-body", i.e. on board points that were NOT previously occupied by the captured stones.
Out-of-body creation of permanent stones will result in seki.
=> L&D Example 1
=> L&D Example 2
=> L&D Example 4
=> L&D Example 5
The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area". => Re-establishment is considered a GLOBAL issue.
=> L&D Example 2
=> L&D Example 4
=> L&D Example 5
Cause and effect relationship
Capture of stones and re-establishment of stones have to be in a cause-and-effect relationship.
Cause =
= capture
Effect = = re-establishment
------------------------
is not an effect of any previous capture of Black stones elsewhere on the board.
Neither nor 
is an effect of any previous capture of Black stones elsewhere on the board.
Neither nor is an effect of any previous capture of Black stones elsewhere on the board.
Subtype "Complete re-establishment"
Stones that could be re-established in total because they were previously captured.
Total re-establishment will result in territory.
Uttegaeshi => Commentary
Nakade => NOT explicitly mentioned
Subtype "Partial re-establishment"
Stones that could be re-established partially because they were previously captured.
Partial re-establishment will result in seki.
=> L&D Example 1
=> L&D Example 5
Subtype "Out-of-body re-establishment"
Because stones were previously captured, permament stones of that colour could be created "out-of-body", i.e. on board points that were NOT previously occupied by the captured stones.
Out-of-body creation of permanent stones will result in seki.
=> L&D Example 1
=> L&D Example 2
=> L&D Example 4
=> L&D Example 5
The "out-of-body area" can be separated by 7.1.U-type stones from the "capture area". => Re-establishment is considered a GLOBAL issue.
=> L&D Example 2
=> L&D Example 4
=> L&D Example 5
Cause and effect relationship
Capture of stones and re-establishment of stones have to be in a cause-and-effect relationship.
Cause =
= captureEffect =
= re-establishment------------------------
is not an effect of any previous capture of Black stones elsewhere on the board. Neither
nor is an effect of any previous capture of Black stones elsewhere on the board.Neither
nor is an effect of any previous capture of Black stones elsewhere on the board.The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
Commentary
7.2.D-type of ko
J89's judgement of L&D:
White's single stone is of the 7.1.D-type.
Black's stones in the corner are of the 7.1.D-type.
Black should have played teire at A before the game stopped.
Why ?
Why ?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
7.2.Y-type of ko
J89's judgement of L&D:
White's single stone is of the 7.1.D-type.
Black's single stone in the corner is of the 7.1.C-type.
Black's seven stones are of the 7.1.U-type.
There is no need for Black to play teire at A before the game stopped.
Why ?
Why / ?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
-------------------------------
Please note that the result would have been the same if White had NOT captured into the ko-shape in the corner.
Implicit understanding:
There are NO ko-fights during L&D status confirmation.
7.2.Y+R-type of ko
J89's judgement of L&D:
White's single stone in the upper corner is of the 7.1.D-type.
Black's single stone in the upper corner is of the 7.1.C-type.
Black's seven stones in the upper corner are of the 7.1.U-type.
The lower corner is and remains a double-ko seki.
There is no need for Black to play teire at A before the game stopped.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Already shown with 7.2.Y-type of ko?
Why / ?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There are NO UNREMOVABLE ko-threats during L&D status confirmation.
Misleading!
The specification of the corner is NOT required for because there is only ONE ko-shape to be re-captured into.
The L&D-status of Black's stones in the upper corner has already been decided by
.
Nevertheless, the second half of the double-ko cycle in the lower corner is shown explicitly.
Implicit understanding:
There is NO double-ko during L&D status confirmation.
Misleading!
The specification of the corner is NEITHER required for
NOR for 
because there is only ONE ko-shape each to be re-captured into.
-------------------------------
Please note that the result would have been the same if White had NOT captured into the ko-shape in the upper corner.
Implicit understanding:
There are NO ko-fights during L&D status confirmation.
7.2.D-type of ko
J89's judgement of L&D:
White's single stone is of the 7.1.D-type. Black's stones in the corner are of the 7.1.D-type.Black should have played teire at A before the game stopped.
Why
?Why
?Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
7.2.Y-type of ko
J89's judgement of L&D:
White's single stone is of the 7.1.D-type. Black's single stone in the corner is of the 7.1.C-type. Black's seven stones are of the 7.1.U-type.There is no need for Black to play teire at A before the game stopped.
Why
?Why
/ ?Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
-------------------------------
Please note that the result would have been the same if White had NOT captured into the ko-shape in the corner.
Implicit understanding:
There are NO ko-fights during L&D status confirmation.
7.2.Y+R-type of ko
J89's judgement of L&D:
White's single stone in the upper corner is of the 7.1.D-type. Black's single stone in the upper corner is of the 7.1.C-type. Black's seven stones in the upper corner are of the 7.1.U-type.The lower corner is and remains a double-ko seki.
There is no need for Black to play teire at A before the game stopped.
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Already shown with 7.2.Y-type of ko?
Why
/ ?Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There are NO UNREMOVABLE ko-threats during L&D status confirmation.
Misleading!
The specification of the corner is NOT required for
because there is only ONE ko-shape to be re-captured into.The L&D-status of Black's stones in the upper corner has already been decided by
.Nevertheless, the second half of the double-ko cycle in the lower corner is shown explicitly.
Implicit understanding:
There is NO double-ko during L&D status confirmation.
Misleading!
The specification of the corner is NEITHER required for
NOR for because there is only ONE ko-shape each to be re-captured into.-------------------------------
Please note that the result would have been the same if White had NOT captured into the ko-shape in the upper corner.
Implicit understanding:
There are NO ko-fights during L&D status confirmation.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 7-1
J89's judgement of L&D:
Black's three stones in the corner are of of the 7.1.U-type.
White's stones in the corner are of the 7.1.D-type.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Why ?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
-------------------------------
Please note that the result would have been the same if White had NOT created the ko-shape in the corner.
Implicit understanding:
There are NO ko-fights during L&D status confirmation.
J89's judgement of L&D:
Black's three stones in the corner are of of the 7.1.U-type. White's stones in the corner are of the 7.1.D-type.Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Why
?Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
-------------------------------
Please note that the result would have been the same if White had NOT created the ko-shape in the corner.
Implicit understanding:
There are NO ko-fights during L&D status confirmation.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 7-2
J89's judgement of L&D:
Black's three stones in the corner are of of the 7.1.U-type.
White's stones in the corner are of the 7.1.D-type.
NO judgement on the L&D status of the lower corner.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Why ?
Implicit understanding:
There are NO UNERASABLE ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
Misleading!
The specification of the corner IS REQUIRED for (but missing) because there are TWO ko-shapes to be re-captured into.
The L&D-status of White's stones in the upper corner has already been decided by .
Nevertheless, the capture of White's stones in the lower corner is shown explicitly.
Implicit understanding:
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
J89's judgement of L&D:
Black's three stones in the corner are of of the 7.1.U-type. White's stones in the corner are of the 7.1.D-type.NO judgement on the L&D status of the lower corner.
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Why
?Implicit understanding:
There are NO UNERASABLE ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
Misleading!
The specification of the corner IS REQUIRED for
(but missing) because there are TWO ko-shapes to be re-captured into.The L&D-status of White's stones in the upper corner has already been decided by
.Nevertheless, the capture of White's stones in the lower corner is shown explicitly.
Implicit understanding:
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 8
J89's judgement of L&D:
White's nine stones are of of the 7.1.U-type.
White's single stone is of the 7.1.C-type.
Black's stones are of the 7.1.D-type.
Why ?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
Misleading!
The specification of the ko-shape IS REQUIRED for (but missing, probably because it does not matter here) because there are TWO ko-shapes to be re-captured into.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit understanding:
There is NO double-ko during L&D status confirmation.
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
=============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Why ?
First attempt.
AFTER White's single stone in the double-ko has been captured, NO (new) PERMANENT White stone can be played, due to J89's (initial version) double-ko cycle.
-----------------------------------------
[/color]
Second attempt.
AFTER White's single stone in the double-ko has been captured (with), (new) PERMANENT White stones could be played (with 
and 
).
[/color]
J89's judgement of L&D:
White's nine stones are of of the 7.1.U-type. White's single stone is of the 7.1.C-type. Black's stones are of the 7.1.D-type.Why
?Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
Misleading!
The specification of the ko-shape IS REQUIRED for
(but missing, probably because it does not matter here) because there are TWO ko-shapes to be re-captured into.Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit understanding:
There is NO double-ko during L&D status confirmation.
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
=============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Why
?First attempt.
AFTER White's single stone in the double-ko has been captured, NO (new) PERMANENT White stone can be played, due to J89's (initial version) double-ko cycle.
-----------------------------------------
[/color]
Second attempt.
AFTER White's single stone in the double-ko has been captured (with
), (new) PERMANENT White stones could be played (with and ).[/color]
Last edited by Cassandra on Sun Sep 19, 2021 10:13 pm, edited 1 time in total.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 11
J89's judgement of L&D:
White's stones at the top are of the 7.1.D-type.
NO judgement on the L&D status of the double-ko seki at the bottom.
Why ?
Implicit understanding:
There are NO UNERASABLE ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is no double-ko during L&D status confirmation.
Misleading!
The specification of the ko-shape IS REQUIRED for (but missing) because there are TWO ko-shapes to be re-captured into.
The L&D-status of White's stones in the upper corner has already been decided by
.
Nevertheless, two passes for the remaining ko-shapes at the bottom are played explicitly.
Contrary to the commentary (7.2.Y+R-type of ko), recapturing into the double-ko is left out here.
Implicit understanding:
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
J89's judgement of L&D:
White's stones at the top are of the 7.1.D-type.NO judgement on the L&D status of the double-ko seki at the bottom.
Why
?Implicit understanding:
There are NO UNERASABLE ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is no double-ko during L&D status confirmation.
Misleading!
The specification of the ko-shape IS REQUIRED for
(but missing) because there are TWO ko-shapes to be re-captured into.The L&D-status of White's stones in the upper corner has already been decided by
.Nevertheless, two passes for the remaining ko-shapes at the bottom are played explicitly.
Contrary to the commentary (7.2.Y+R-type of ko), recapturing into the double-ko is left out here.
Implicit understanding:
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 12
J89's judgement of L&D:
Black's stones are of the 7.1.U-type.
White's three stones are of the 7.1.U-type.
White's single stone is of the 7.1.C-type.
Why ?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
Why ?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
J89's judgement of L&D:
Black's stones are of the 7.1.U-type. White's three stones are of the 7.1.U-type. White's single stone is of the 7.1.C-type.Why
?Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
Why
?Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit understanding:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 16
J89's judgement of L&D:
White's stones are of of the 7.1.D-type.
Black's twelve stones are of the 7.1.U-type.
Black's single stone is of the 7.1.C-type.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit APPLICATION:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
Blueprint is the sequence in the commentary (7.2.Y+R-type of ko).
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
AFTER Black's single stone in the double-ko has been captured (with), it could be re-established (with 
).
Alternatively, Black could be content with having placed a (new) PERMANENT stone with .
=============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Please note that the points T are territory!
Why ?
Why ?
The capture of White's two stones at the left (with) enabled a (new) PERMANENT White stone (with ).
Why ?
The capture of Black's single stone at the left edge (with) enabled (new) PERMANENT Black stones (with and 
).[/color]
J89's judgement of L&D:
White's stones are of of the 7.1.D-type. Black's twelve stones are of the 7.1.U-type. Black's single stone is of the 7.1.C-type.Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit APPLICATION:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
Blueprint is the sequence in the commentary (7.2.Y+R-type of ko).
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
AFTER Black's single stone in the double-ko has been captured (with
), it could be re-established (with ).Alternatively, Black could be content with having placed a (new) PERMANENT stone with
. =============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Please note that the points T are territory!
Why
?Why
?The capture of White's two stones at the left (with
) enabled a (new) PERMANENT White stone (with ).Why
?The capture of Black's single stone at the left edge (with
) enabled (new) PERMANENT Black stones (with and ).[/color]
Last edited by Cassandra on Sun Sep 19, 2021 9:04 am, edited 1 time in total.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 17
J89's judgement of L&D:
White's stones are of of the 7.1.D-type.
Black's 15 stones are of the 7.1.U-type.
Black's four stones at the left edge are of the 7.1.C-type.
Please note that there is NO explicit status for Black's stones in the double-ko in J89's comment to this example.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit APPLICATION:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
Blueprint is the sequence in the commentary (7.2.Y+R-type of ko).
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
AFTER Black's single stone in the double-ko has been captured (with), Black could play (new) PERMANENT stones (with and ).
Alternatively, Black could have captured into the double-ko with, reverting to the sequence for above.
--------------------------------------------------------
AFTER Black's three stones in the corner have been captured (with), Black could play a (new) PERMANENT stone (with ).
Alternatively, Black could have played into White's eye in the corner with, reverting to the sequence for above.
=============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Please note that the points T are territory!
Why ?
[/color]
J89's judgement of L&D:
White's stones are of of the 7.1.D-type. Black's 15 stones are of the 7.1.U-type. Black's four stones at the left edge are of the 7.1.C-type.Please note that there is NO explicit status for Black's stones in the double-ko in J89's comment to this example.
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit APPLICATION:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
Blueprint is the sequence in the commentary (7.2.Y+R-type of ko).
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
AFTER Black's single stone in the double-ko has been captured (with
), Black could play (new) PERMANENT stones (with and ).Alternatively, Black could have captured into the double-ko with
, reverting to the sequence for above.--------------------------------------------------------
AFTER Black's three stones in the corner have been captured (with
), Black could play a (new) PERMANENT stone (with ).Alternatively, Black could have played into White's eye in the corner with
, reverting to the sequence for above.=============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Please note that the points T are territory!
Why
?[/color]
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)
-
Cassandra
- Lives in sente
- Posts: 1326
- Joined: Wed Apr 28, 2010 11:33 am
- Rank: German 1 Kyu
- GD Posts: 0
- Has thanked: 14 times
- Been thanked: 153 times
Re: J89's Article 7 (L&D):: Reverse engineered
L&D Example 18
J89's judgement of L&D:
Black's stones are of the 7.1.D-type.
White's two stones in the corner and 15 stones in the double-ko are of the 7.1.U-type.
White's single stone in the double-ko is of the 7.1.C-type.
Please note that there is NO explicit status for White's stones in the double-ko in J89's comment to this example.
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit APPLICATION:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
Blueprint is the sequence in the commentary (7.2.Y+R-type of ko).
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
Why ?
NOT SHOWN.
Implicit understanding:
Considered redundant?
AFTER White's single stone in the double-ko has been captured (with), White could play a (new) PERMANENT stone (with ).
Alternatively, White could connect in the corner with, reverting to the sequence for above.
=============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Why ?
[/color]
J89's judgement of L&D:
Black's stones are of the 7.1.D-type. White's two stones in the corner and 15 stones in the double-ko are of the 7.1.U-type. White's single stone in the double-ko is of the 7.1.C-type.Please note that there is NO explicit status for White's stones in the double-ko in J89's comment to this example.
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Implicit APPLICATION:
There are NO ko-threats during L&D status confirmation.
Capturing into a single ko-shape allows playing two moves in a row locally.
There is NO double-ko during L&D status confirmation.
An UNERASABLE ko-threat is NOT a means of creating stones of the 7.1.C-type.
Blueprint is the sequence in the commentary (7.2.Y+R-type of ko).
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
Why
?NOT SHOWN.
Implicit understanding:
Considered redundant?
AFTER White's single stone in the double-ko has been captured (with
), White could play a (new) PERMANENT stone (with ).Alternatively, White could connect in the corner with
, reverting to the sequence for above.=============================================
=============================================
MISTAKE in J89's INITIAL version???
This diagram shows the CORRECT judgement when applying J89's initial version of the L&D status confirmation.
Why
?[/color]
Last edited by Cassandra on Mon Sep 20, 2021 6:08 am, edited 1 time in total.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Igo Hatsuyōron #120 (really solved by KataGo)