@pmelab/gtd 48.0.0 → 50.0.0

package/src/workflows/feature/refactor-first.feature

@@ -121,7 +121,7 @@ Feature: a refactor-first judgment walks one fixed path to the review gate
       [{"id":"AC-1","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "build.review.composing"
+    Then the process rests at "build.review.reviewing"
     And "src/calc.ts" contains "op(a, b, 1)"
     And "src/calc.ts" contains "subtract"
     And the commit subjects end with:
@@ -145,7 +145,7 @@ Feature: a refactor-first judgment walks one fixed path to the review gate
       gtd(agent): implement.building → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → build.review.composing
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the commit "gtd(human): idle → unwind" has a body containing "Gtd-Var: flag_risk_tier=0"
     And the commit "gtd(agent): seam.naive → seam.check" has a body containing "Gtd-Kept:"

package/src/workflows/feature/refactor-rebuild.feature

@@ -242,7 +242,7 @@ Feature: refactor-first writes a refactor note, refactors on its own, then rebui
       [{"id":"AC-1","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "build.review.composing"
+    Then the process rests at "build.review.reviewing"
     And "src/calc.ts" contains "op(a, b, -1)"
     And "src/acceptance.test.ts" contains "[AC-1]"
     And ".gtd/REFACTOR-NOTE.md" does not exist
@@ -260,7 +260,7 @@ Feature: refactor-first writes a refactor note, refactors on its own, then rebui
       gtd(agent): implement.building → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → build.review.composing
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the output lines of gtd "slices" start with:
       """

package/src/workflows/feature/refactor-review.feature

@@ -646,7 +646,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "build.review.composing"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a praise-only one-shot footnote signs off and the feature slice follows
@@ -688,7 +688,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "build.review.composing"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a one-shot footnote judged edit that collecting leaves out refuses naming its anchor
@@ -1003,7 +1003,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "build.review.composing"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a praise-only refactor review still signs off and the feature slice follows
@@ -1038,7 +1038,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "build.review.composing"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a nit fix in the refactor slice that changes a non-stray is refused, though a glob stray widens the write access
@@ -1228,11 +1228,11 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
       And the resting step's content contains the hash of the commit "gtd(check): refactor.build.review.closing → implement.building"
       Given step "build.quality.correctness.reviewing" changes nothing
       When the process is driven
-      Then the process rests at "build.review.composing"
+      Then the process rests at "build.review.reviewing"
       And the commit subjects end with:
         """
         gtd(check): implement.closing → build.quality.correctness.reviewing
-        gtd(agent): build.quality.correctness.reviewing → build.review.composing
+        gtd(agent): build.quality.correctness.reviewing → build.review.reviewing
         """
 
   Rule: a refactor package never carries a test file, and demoted headings stop at ######

package/src/workflows/feature/review-answers.feature

@@ -1,7 +1,7 @@
 @inmem
 Feature: every note in the review is answered with one tick
 
-  Each note gtd writes to `.gtd/REVIEW.md` ends in three boxes — fix as
+  Each quality note in `.gtd/REVIEW.md` ends in three boxes — fix as
   suggested, won't fix, or the human's own answer written over the
   placeholder. The gate refuses to land until every note holds exactly one
   tick. A fix goes to the nit batch, a won't-fix is dropped and recorded in
@@ -74,7 +74,45 @@ Feature: every note in the review is answered with one tick
       Should subtract round? The criterion does not say.
       """
     And step "build.quality.sorting" runs its script
-    And step "build.review.composing" runs its script
+    And step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+      """
+    And step "build.review.reviewing", when prompted with "- `## AC-1 ignores floating point`", writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+      """
+    And step "build.review.reviewing", when prompted with "worked on the human's nits", writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      - [ ] ./src/calc.ts#2-2 — now rounds the difference
+      """
+    And step "build.review.carrying" runs its script
+    And judge step "build.review.ranking" answers:
+      """
+      []
+      """
     And judge step "build.quality.triage" answers:
       """
       [{"id":"Q1","answer":"noise","p":0.9},{"id":"Q2","answer":"noise","p":0.9},{"id":"Q3","answer":"design","p":0.9}]
@@ -88,8 +126,14 @@ Feature: every note in the review is answered with one tick
       """
       ## AC-1 ignores floating point
 
+      _critical: judge unsure_
+
       Should subtract round? The criterion does not say.
 
+      In the code:
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+
       Tick exactly one:
 
       - [ ] fix as suggested
@@ -141,7 +185,7 @@ Feature: every note in the review is answered with one tick
     And the process is driven
     Then the process rests at "build.review.await-review"
     And no commit body contains "build.review.triage"
-    And ".gtd/REVIEW.md" contains "## Fixed from your notes"
+    And ".gtd/REVIEW.md" contains "now rounds the difference"
     And ".gtd/REVIEW.md" does not contain "AC-1 ignores floating point"
     And ".gtd/TODO.md" does not exist
     When gtd lands
@@ -176,8 +220,10 @@ Feature: every note in the review is answered with one tick
       gtd(judge): build.review.triage → build.review.fix.nits.fixing
       gtd(agent): build.review.fix.nits.fixing → build.health.check
       gtd(check): build.health.check → build.review.closing
-      gtd(check): build.review.closing → build.review.composing
-      gtd(check): build.review.composing → build.review.await-review
+      gtd(check): build.review.closing → build.review.reviewing
+      gtd(agent): build.review.reviewing → build.review.ranking
+      gtd(judge): build.review.ranking → build.review.carrying
+      gtd(check): build.review.carrying → build.review.await-review
       """
     And ".gtd/REVIEW.md" does not contain "AC-1 ignores floating point"
 

package/src/workflows/feature/review-gate.feature

@@ -57,7 +57,7 @@ Feature: a feature process ends at the human review
       """
       [{"id":"AC-1","answer":"yes","p":0.9}]
       """
-    And step "build.review.composing" writes ".gtd/REVIEW.md" with:
+    And step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
       """
       # Review: abc1234
 
@@ -69,6 +69,11 @@ Feature: a feature process ends at the human review
         new subtract function
       """
     And step "build.review.closing" runs its script
+    And step "build.review.carrying" runs its script
+    And judge step "build.review.ranking" answers:
+      """
+      []
+      """
 
   Scenario: a feature process ends at the review gate
     When the process is driven
@@ -78,8 +83,10 @@ Feature: a feature process ends at the human review
     And the commit subjects end with:
       """
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → build.review.composing
-      gtd(check): build.review.composing → build.review.await-review
+      gtd(check): implement.closing → build.review.reviewing
+      gtd(agent): build.review.reviewing → build.review.ranking
+      gtd(judge): build.review.ranking → build.review.carrying
+      gtd(check): build.review.carrying → build.review.await-review
       """
 
   Scenario: a sign-off ends the process at idle
@@ -93,6 +100,8 @@ Feature: a feature process ends at the human review
 
       ## calc
 
+      _critical: judge unsure_
+
       - [x] ./src/calc.ts#2-2
         new subtract function
       """
@@ -102,7 +111,9 @@ Feature: a feature process ends at the human review
     And ".gtd/REVIEW.md" does not exist
     And the commit subjects end with:
       """
-      gtd(check): build.review.composing → build.review.await-review
+      gtd(agent): build.review.reviewing → build.review.ranking
+      gtd(judge): build.review.ranking → build.review.carrying
+      gtd(check): build.review.carrying → build.review.await-review
       gtd(human): build.review.await-review → build.review.closing
       gtd(check): build.review.closing → idle
       """
@@ -146,6 +157,8 @@ Feature: a feature process ends at the human review
 
         ## calc
 
+        _critical: judge unsure_
+
         - [ ] ./src/calc.ts#2-2
           new subtract function[^why]
 
@@ -164,6 +177,8 @@ Feature: a feature process ends at the human review
 
         ## calc
 
+        _critical: judge unsure_
+
         - [ ] ./src/calc.ts#2-2
           new subtract function
         """
@@ -214,8 +229,10 @@ Feature: a feature process ends at the human review
         gtd(agent): implement.building → implement.health.check
         gtd(check): implement.health.check → implement.coverage
         gtd(judge): implement.coverage → implement.closing
-        gtd(check): implement.closing → build.review.composing
-        gtd(check): build.review.composing → build.review.await-review
+        gtd(check): implement.closing → build.review.reviewing
+        gtd(agent): build.review.reviewing → build.review.ranking
+        gtd(judge): build.review.ranking → build.review.carrying
+        gtd(check): build.review.carrying → build.review.await-review
         """
 
     Scenario: a design numbering new behaviour at or below an earlier ID is refused

package/src/workflows/feature/reviewer-walkthrough.feature

@@ -0,0 +1,240 @@
+@inmem
+Feature: a reviewer walks the human through the feature's code
+
+  The feature's final review is written by a reviewer turn
+  (`build.review.reviewing`): chunks grouped by concern, each pointing at its
+  code, so the phone shows it. Every finding the quality laps left gets a chunk
+  of its own, headed exactly as the prompt gives it, holding the pointers to the
+  code it cites; gtd then adds the finding's text and the answer boxes
+  (`build.review.carrying`). A chunk pointing at no code, or a finding left out,
+  is refused.
+
+  Background:
+    Given the shipped workflows, as gtd install scaffolds them
+    And an environment variable "GTD_QUALITYREVIEWS" set to "correctness"
+    And an environment variable "GTD_FLAGMODE" set to "false"
+    And a file "src/calc.ts" with:
+      """
+      export const add = (a: number, b: number) => a + b
+      """
+    And the working tree is committed as "feat: add calculator"
+    And a file "TODO.md" with:
+      """
+      # Add subtract
+
+      subtract(a, b) returns the difference.
+      """
+    And step "unwind" changes nothing
+    And step "start-gate.check" changes nothing
+    And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
+      """
+      # Requirements
+
+      ## Acceptance Criteria
+
+      - AC-1: subtract(a, b) returns a - b.
+      """
+    And step "design.gate.answer" changes nothing
+    And step "seam.naive" writes "src/calc.test.ts" with:
+      """
+      it("[AC-1] subtracts", () => {})
+      """
+    And step "seam.naive" writes "src/calc.ts" with:
+      """
+      export const add = (a: number, b: number) => a + b
+      export const subtract = (a: number, b: number) => a - b
+      """
+    And step "seam.check" changes nothing
+    And step "implement.applying" runs its script
+    And step "implement.health.check" changes nothing
+    And step "implement.closing" runs its script
+    And judge step "implement.coverage" answers:
+      """
+      [{"id":"AC-1","answer":"yes","p":0.9}]
+      """
+    And step "build.quality.correctness.reviewing" writes ".gtd/QUALITY.md" with:
+      """
+      # Quality
+
+      ## AC-1 ignores floating point
+
+      Should subtract round? The criterion does not say.
+      """
+    And judge step "build.quality.triage" answers:
+      """
+      [{"id":"Q1","answer":"design","p":0.9}]
+      """
+    And step "build.quality.sorting" runs its script
+    And step "build.quality.closing" runs its script
+    And step "build.review.carrying" runs its script
+    And judge step "build.review.ranking" answers:
+      """
+      []
+      """
+
+  Scenario: the finding gets its text and answer boxes under the reviewer's pointers
+    Given step "build.review.reviewing" is prompted with "- `## AC-1 ignores floating point`:"
+    And step "build.review.reviewing" is prompted with "> Should subtract round? The criterion does not say."
+    And step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      The new export.
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+      """
+    When the process is driven
+    Then the process rests at "build.review.await-review"
+    And ".gtd/REVIEW.md" contains:
+      """
+      ## Subtract
+
+      _critical: judge unsure_
+
+      The new export.
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+
+      ## AC-1 ignores floating point
+
+      _critical: judge unsure_
+
+      Should subtract round? The criterion does not say.
+
+      In the code:
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+
+      Tick exactly one:
+
+      - [ ] fix as suggested
+      - [ ] won't fix
+      - [ ] _your answer_
+      """
+    And no commit body contains "build.review.composing"
+    And the commit subjects end with:
+      """
+      gtd(agent): build.review.reviewing → build.review.ranking
+      gtd(judge): build.review.ranking → build.review.carrying
+      gtd(check): build.review.carrying → build.review.await-review
+      """
+
+  Scenario: a chunk pointing at no code is refused
+    Given step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      The new export, with no pointer.
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+      """
+    Then driving the process is refused with "Subtract — points at no code"
+
+  Scenario: a finding the reviewer left out is refused
+    Given step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+      """
+    Then driving the process is refused with "AC-1 ignores floating point — no chunk of its own"
+
+  Scenario: a risk the reviewer marks is fixed before the human sees the review
+    Given step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      - [ ] ./src/calc.ts#2-2 — Risk: overflows on large numbers
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+      """
+    And step "build.review.fix.risks.fixing" changes nothing
+    And step "build.health.check" changes nothing
+    When the process is driven
+    Then the process rests at "build.review.await-review"
+    And the commit subjects end with:
+      """
+      gtd(agent): build.review.reviewing → build.review.ranking
+      gtd(judge): build.review.ranking → build.review.carrying
+      gtd(check): build.review.carrying → build.review.fix.risks.fixing
+      gtd(agent): build.review.fix.risks.fixing → build.health.check
+      gtd(check): build.health.check → build.review.reviewing
+      gtd(agent): build.review.reviewing → build.review.ranking
+      gtd(judge): build.review.ranking → build.review.carrying
+      gtd(check): build.review.carrying → build.review.await-review
+      """
+
+  Scenario: a standard conflict the reviewer writes itself is refused
+    Given step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Standard conflict 0123abcd
+
+      - [ ] ./src/calc.ts#2-2 — copied over
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+      """
+    Then driving the process is refused with "Standard conflict 0123abcd — gtd writes conflicts"
+
+  Scenario: two chunks with one title are refused
+    Given step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+      """
+    Then driving the process is refused with "AC-1 ignores floating point — a second chunk with this title"
+
+  Scenario: a risk marked in a finding's chunk is refused, never fixed
+    Given step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — Risk: no rounding
+      """
+    Then driving the process is refused with "no `Risk:` in a quality finding's chunk"

package/src/workflows/feature/seam-rejection.feature

@@ -100,7 +100,7 @@ Feature: rejected naive passes walk one fixed path through the steer gate to the
     And step "implement.applying" runs its script
     When gtd lands
     And the process is driven
-    Then the process rests at "build.review.composing"
+    Then the process rests at "build.review.reviewing"
     And the commit subjects end with:
       """
       gtd(human): idle → unwind
@@ -124,7 +124,7 @@ Feature: rejected naive passes walk one fixed path through the steer gate to the
       gtd(check): implement.applying → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → build.review.composing
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the commit "gtd(human): idle → unwind" has a body containing "Gtd-Var: flag_risk_tier=0"
     And the commit "gtd(agent): seam.naive → seam.check" has a body containing "Gtd-Kept:"

package/src/workflows/feature/seam.feature

@@ -152,7 +152,7 @@ Feature: the naive pass and seam judge decide how a feature is built
       [{"id":"AC-1","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "build.review.composing"
+    Then the process rests at "build.review.reviewing"
     And "src/calc.ts" contains "subtract"
     And the commit subjects end with:
       """
@@ -160,7 +160,7 @@ Feature: the naive pass and seam judge decide how a feature is built
       gtd(check): implement.applying → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → build.review.composing
+      gtd(check): implement.closing → build.review.reviewing
       """
     And ".gtd/REQUIREMENTS.md" does not exist
 

package/src/workflows/feature/severity-budget.feature

@@ -0,0 +1,111 @@
+@inmem
+Feature: the review's ranking is batched to the judge's budget
+
+  `build.review.ranking` puts as many chunks in one judgment as the budget's
+  even share still holds whole; the rest go to the next. A chunk too big to
+  fit even alone is cut, and a cut chunk is critical.
+
+  Background:
+    Given the shipped workflows, as gtd install scaffolds them
+    And an environment variable "GTD_QUALITYREVIEWS" set to "correctness"
+    And an environment variable "GTD_FLAGMODE" set to "false"
+    And an environment variable "GTD_JUDGEBUDGETBYTES" set to "150"
+    And a file "src/calc.ts" with:
+      """
+      export const add = (a: number, b: number) => a + b
+      """
+    And the working tree is committed as "feat: add calculator"
+    And a file "TODO.md" with:
+      """
+      # Add subtract
+
+      subtract(a, b) returns the difference.
+      """
+    And step "unwind" changes nothing
+    And step "start-gate.check" changes nothing
+    And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
+      """
+      # Requirements
+
+      ## Acceptance Criteria
+
+      - AC-1: subtract(a, b) returns a - b.
+      """
+    And step "design.gate.answer" changes nothing
+    And step "seam.naive" writes "src/calc.test.ts" with:
+      """
+      it("[AC-1] subtracts", () => {})
+      """
+    And step "seam.naive" writes "src/calc.ts" with:
+      """
+      export const add = (a: number, b: number) => a + b
+      export const subtract = (a: number, b: number) => a - b
+      """
+    And step "seam.check" changes nothing
+    And step "implement.applying" runs its script
+    And step "implement.health.check" changes nothing
+    And step "implement.closing" runs its script
+    And judge step "implement.coverage" answers:
+      """
+      [{"id":"AC-1","answer":"yes","p":0.9}]
+      """
+    And step "build.quality.correctness.reviewing" writes ".gtd/QUALITY.md" with:
+      """
+      # Quality
+
+      ## AC-1 ignores floating point
+
+      Should subtract round? The criterion does not say.
+      """
+    And judge step "build.quality.triage" answers:
+      """
+      [{"id":"Q1","answer":"design","p":0.9}]
+      """
+    And step "build.quality.sorting" runs its script
+    And step "build.quality.closing" runs its script
+    And step "build.review.carrying" runs its script
+
+  Scenario: a chunk the budget cuts is listed as critical, the others judged in batches of their own
+    Given step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## Subtract
+
+      - [ ] ./src/calc.ts#2-2 — subtract(a, b)
+
+      ## AC-1 ignores floating point
+
+      - [ ] ./src/calc.ts#2-2 — returns the raw difference
+      """
+    And judge step "build.review.ranking", when its questions contain "C1.security", answers:
+      """
+      [{"id":"C1.security","answer":"no","p":0.9},{"id":"C1.reversibility","answer":"two-way","p":0.9},{"id":"C1.blastRadius","answer":"local","p":0.9},{"id":"C1.newConcept","answer":"no","p":0.9}]
+      """
+    And judge step "build.review.ranking", when its questions contain "C2.security", answers:
+      """
+      [{"id":"C2.security","answer":"no","p":0.9},{"id":"C2.reversibility","answer":"two-way","p":0.9},{"id":"C2.blastRadius","answer":"local","p":0.9},{"id":"C2.newConcept","answer":"no","p":0.9}]
+      """
+    When the process is driven
+    Then the process rests at "build.review.await-review"
+    And ".gtd/REVIEW.md" contains:
+      """
+      ## AC-1 ignores floating point
+
+      _critical: judge unsure_
+      """
+    And ".gtd/REVIEW.md" contains:
+      """
+      ## Subtract
+
+      _could_
+      """
+    And the commit subjects end with:
+      """
+      gtd(agent): build.review.reviewing → build.review.ranking
+      gtd(judge): build.review.ranking
+      gtd(judge): build.review.ranking → build.review.carrying
+      gtd(check): build.review.carrying → build.review.await-review
+      """