Development record

2026-10-10 — Five points spc-2609212015054359 step 1 (scope 3, the host judgement before a drain's lane opens; itd-82 criterion 2) left open, settled by lane-1 of run-2610101724174688 in building it. (1) The host-pass shape is the loop's own: the drain writes one request, `.abcd/.work.local/run/drain-judgement.request.md`, records the issue and the sha256 of the remedy it shows in its state as `judging`, and opens nothing; the host writes strict JSON to `.abcd/.work.local/run/drain-judgement.json` and hands it back with a new flag on the bare verb, `abcd drain --judgement <file>`, which accepts only that path. The answer echoes `issue` and `remedy_sha256`, so an answer written for an earlier request, or over a remedy rewritten since, cannot be taken for this one; a remedy rewritten while the answer is out refuses the answer and the next move asks again. (2) The spec's yes/no carries a kind with a yes, `user-visible` or `trust-rule` (`trust-rule` when both, since it names the decision a person owes first), and a yes is routed exactly as a lane's hand-back of the same kind (promoted with `capture promote`, or flagged as needing a decision record with the reason as its question), with `from: "judgement"`; the intent's press release routes "an issue that needs a decision" by kind whatever found it, and a second routing for the judgement alone would be a design the record does not ask for. (3) The request tells the host to answer yes when the remedy does not let it tell, since the judgement guards a failure that runs one way and can only hand back. (4) An answer over an issue that left the eligible set since the request is recorded with `applied: false` and a note and decides nothing, which is criterion 2's "never makes an ineligible issue eligible" at the moment the answer arrives; a no is bound to the remedy's digest, so a rewritten remedy is asked about again before its lane opens. (5) `--max` keeps counting lanes, as it did: an issue the judgement hands back opened no lane, and the intent's "issues attempted" is read as lanes attempted. `abcd build <iss-N>`, a person's own start of one issue's lane, asks no judgement: the judgement is the drain's unattended pass, and the person typing the id is the judgement.