FA-83205 / Go territory scoring / Member archive

The 1k to 1d step is counted as two ranks · case 05

Games across the kyu/dan boundary get an extra handicap stone.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Input [rank_a, rank_b] as Nk (1..30) or Nd (1..9); 1k and 1d are one rank apart. Equal ranks -> [rank_a, 0, 65]; one rank apart -> [weaker, 0, 5]; otherwise [weaker, min(diff, 9), 5]. Invalid ranks -> "invalid". The first element is the player taking black.

Why this case matters

Go servers and scoring tools compute this value automatically; a wrong answer changes a game result.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
handicap case 0	`["2k", 5, 5]`	`["2k", 4, 5]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.