plans: rows 137 and 139, land-work keeps its human-only check; only the host land op accepts an arbiter, carried by whichever lands second (Dewey 0515)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-16 13:18:38 -05:00
parent 5661bd233b
commit b2a2d741c4
1 changed files with 16 additions and 3 deletions
@@ -321,7 +321,13 @@ survive a reseed.
  Whichever of 137 and 139 lands second carries the refusal and its test.
  Sage checks this at each landing: a row that lands first leaves it out,
  and the row that lands second is not done without it.
- `read.mjs` keeps its cli-resolved check. Row 139 relaxes it.
+- land-work's own check in `read.mjs` does not change: a merge it lands
+  must be resolved by the human through the CLI, because canonical
+  `refactor` stays the lead's landing (PRD 1.5, Mos's Q4). Only the host
+  land op's copy of the check, in the shared module, accepts a decision
+  its arbiter resolved (REQ-DEC-2). Whichever of 137 and 139 lands second
+  makes the host op accept it, with the test: an arbiter-resolved merge
+  decision raised by merge-gate lands through the host op.
 - Canonical `refactor` is never a target. land-work.sh keeps working for
  Sage's landings.
 - BUILD.md names the change to push and fetch behaviour that the seed
@@ -427,9 +433,12 @@ Jason on 2026-10-15.
 - `packages/business/src/vocabulary.mjs`, GATED_ONLY and the new hard-wait
  actions
 - `packages/bus/src/broker.mjs`, GATED and decision.raise routing
- the `read.mjs` cli-resolved check that row 137 keeps
+- if row 137 has landed, the host land op's resolution check in its
+  shared module. land-work's own human-only check in `read.mjs` does not
+  change (sage-0516, on Dewey 0515).
 - `roles/*.json`, grants only as the PRD 1.5 text requires
- tests in the bus and business packages, and READMEs
+- tests in the bus and business packages, and READMEs; in
+  `scripts/test-land-work.sh`, only the arbiter-resolved `not-human` case

 ### What ships

@@ -453,6 +462,10 @@ Jason on 2026-10-15.
  to the arbiter, for an uncited decision still going to the human, for a
  stale spec citation, and for the land refusal: a coder raises a cited
  merge decision, the arbiter approves it, and the land refuses.
+- Whichever of 137 and 139 lands second makes the host land op accept an
+  arbiter-resolved merge decision, as row 137's brief says. Row 139 always
+  adds a test that land-work still refuses an arbiter-resolved merge
+  decision with `not-human`.

 ### Out of scope