Answer stability round 1: 0 🔴, 2 🟡 (0 misread); move hand_over into loop_claude and correct items 51 and 197

This commit is contained in:
2026-11-13 23:34:24 +01:00
parent c1924e51ef
commit aa0c7970bd
6 changed files with 6 additions and 7 deletions
+1 -1
View File
@@ -168,7 +168,7 @@ Install puts only `loop-claude` on `PATH`; call the others by their path, such a
- `judge_replay` imports `loop_claude`'s judge, verdicts, premises and records.
- `loop_claude` runs `chunk-preflight` as a process of its own.
- `loop_effects/` holds `Effects`: the processes, terminal, clock and git a tool reaches, injected so its tests can script them. loop-claude, both replay tools and `reviewer-merge-trials`' driver use it.
- `loop_state/` holds where loop-claude keeps its files (`paths.py`), which `rung_replay` reads too, and `hand_over.py`, which opens claude on the terminal for `/talk`.
- `loop_state/` holds where loop-claude keeps its files (`paths.py`), which `rung_replay` reads too.
- `machine_load/` takes the machine's heavy slots, its shared lock files, for `run_heavy`, and reads the memory share that loop-claude waits for. It also gives `mutate_changes` a slot's CPU count.
- `mattermost_dm/` sends the human a Mattermost DM, for `mattermost-dm` and for loop-claude through `loop_effects`.
- `model_routing/` holds the routing ladder, which loop-claude, `rule_hook`, both replay tools and `subagent-rung` read, and the list prices, which `routing_figures` and `transcript_archive` read.
+1 -1
View File
@@ -1,4 +1,4 @@
"""loop-claude: headless claude cycles, judged, that interrupt the human only for a decision that is theirs (loop/usage.py's help).
Its packages hold one concern each: cycle/ runs a cycle, loop/ runs the cycles, and project/ reads a checkout's files. Its paths and the way it opens claude for the human live in bin/loop_state/, and its effects in bin/loop_effects/. Each module at this level is imported by more than one package, or by a module at this level that is. A reader finds a module by its name, so the modules stay at one level. docs/decisions.md → `principles: about seven things per level, …` allows that.
Its packages hold one concern each: cycle/ runs a cycle, loop/ runs the cycles, and project/ reads a checkout's files. Its paths live in bin/loop_state/, and its effects in bin/loop_effects/. Each module at this level is imported by more than one package, or by a module at this level that is. A reader finds a module by its name, so the modules stay at one level. docs/decisions.md → `principles: about seven things per level, …` allows that.
"""
+2 -3
View File
@@ -3,7 +3,7 @@ import sys
import typing
import uuid
from loop_state.hand_over import claude_args, ClaudeCommand, hand_over
from loop_claude.hand_over import claude_args, ClaudeCommand, hand_over
from loop_effects.effects import Effects, say
from failure import Failure
from claude_code.transcript import human_turns, read_transcript
@@ -12,9 +12,8 @@ from model_routing.ladder import Rung
from loop_claude.direct_message import tell
ANSWER_QUESTION = "answer the question above"
# What the human types at loop-claude's terminal to open claude for the question; picked on 2026-10-17 by a bench of three readers seated as the README's audience.
# TALK, what the human types at loop-claude's terminal to open claude for the question, and ASK_ANSWER were picked on 2026-10-17 by a bench of three readers seated as the README's audience, as ~/.claude/CLAUDE.md → "Working loop" → "Bench a syntax with the people who write it." has it.
TALK = "/talk"
# ASK_ANSWER was picked on 2026-10-17 by a bench of three readers seated as the README's audience, as ~/.claude/CLAUDE.md → "Working loop" → "Bench a syntax with the people who write it." has it.
ASK_ANSWER = f"Answer ({TALK} opens claude, Enter stops the loop): "
+1 -1
View File
@@ -3,7 +3,7 @@ import pathlib
from routing_figures import archive
from routing_figures.calls import Call, calls, totals
from loop_state.hand_over import claude_args, ClaudeCommand, hand_over
from loop_claude.hand_over import claude_args, ClaudeCommand, hand_over
from loop_effects.effects import Effects, say
from failure import Failure
from loop_claude.loop.this_loop import Loop
+1 -1
View File
@@ -1,4 +1,4 @@
"""What loop-claude and the tools that replay its runs share: where its files are (paths.py), and how it opens claude for the human on its terminal (hand_over.py).
"""Where loop-claude keeps its files (paths.py), which the tools that replay its runs read too.
It doesn't import anything from loop_claude/.
"""