dev/nisse
2
1 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

The new loop's core: intake, restatement, go-ahead, threads (M2.1, PR B) #97

Merged
dongar merged 3 commits from loop-core into main 2026-10-03 16:42:57 +00:00
Conversation 1 Commits 3 Files Changed 17
+2199 -1
3 Commits
Author SHA1 Message Date
dongar 510d395ead Merge pull request 'Milestones and review in the new loop (M2.1, PR C)' (#98) from loop-milestones into loop-core
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m51s
Details 
Reviewed-on: dongar/nisse#98
Reviewed-by: Don Garrett <dgarrett@acm.org>
 2026-10-03 14:09:17 +00:00
dongarandClaude Opus 5.5 21744efac1 Milestones and review in the new loop (M2.1, PR C)
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m48s
Details 
A work item starts from a fresh workspace: fetch, set aside (never
discard) leftover changes, branches and unpushed commits, a clean default
branch, and a branch of its own (D3, #62). start_milestone cuts the
milestone's branch; finish_milestone commits only the work, pushes and
opens a PR that closes the issue, under an intent, adopting an open PR and
treating a closed one as the operator's answer (D4). Between runs the
loop watches each item's PR: operator comments and inline review notes
(#69) reach the item, a merge or close hands back to the driver. A review
fix is checked after it's pushed and goes out as a new PR if the PR merged
first (D5). At boot an interrupted publish is settled against Gitea (L8).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
 2026-10-02 23:53:02 +00:00
dongarandClaude Opus 5.5 f84bb70839 The new loop's core: intake, restatement, go-ahead, threads (M2.1, PR B)
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m44s
Details 
nisse_dev.loop runs alongside control.py, chosen with `loop: new`.
Issues assigned to the agent (by an operator, or filed by one) become work
items, each with a Matrix thread. A driver run is one model with tools
until it calls a waiting tool: restate puts rev-N up for a go-ahead, bound
to the revision on screen when the reply arrived; ask_human waits for an
answer; close_item closes the item and its issue. Before the go-ahead the
driver can look but not change or close anything. One item is active at a
time; replies in an item's thread go to it. On boot, an item cut off
mid-run waits on the operator, and waiting points are put up again.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
 2026-10-02 23:46:42 +00:00