mosaicstack/stack
25
0
Fork 1
Code Issues 365 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

review loop: working repositories, git socket, push and review verdicts, row 93 (#1587)

Browse Source 
Commits move as v2 bundles over bus-host/git.sock (decision 135). The bus
host keeps one bare working repository per business and project, seeds main
from the project root under a per-repository lock, fetches a pushed bundle
with fsck into a temp ref, requires history shared with main, and moves the
task's work ref only as a fast-forward. Host and runner git run with no
system or global config, hooks at /dev/null and local transports only. The
socket binds only for roles holding git.push.working or review.verdict.

The broker records a push as the action.allowed for git.push.working with
its commit, takes review.request for the latest push and one review.verdict
per request, and refuses task.close on a pushed task without an approve
verdict for the latest push. recordEvent reserves both shapes, so agents
can't forge either.

Reviewed by Dewey (28196) and Sage (28197), both approve. Gate on 7a729aef:
14 node suites and 9 scripts green.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jason.woltje
2026-10-13 10:48:34 -05:00
co-authored by Claude Opus 5.5
parent 7a729aefa3
commit 4da6815293
29 changed files with 2149 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files
roles/coder.md
+10 -3
View File
@@ -7,11 +7,18 @@ assigned to you and hand finished work to review.
- Work only on tasks assigned to you. Update a task's state and comments
as the work moves.
- Push only to the project's working branch. Protected branches belong
to the human.
- Push only with `push_working`. It sends one branch of your clone to
the task's work branch in the business's working repository, and only
as a fast-forward of what the task pushed before. Protected branches
belong to the human.
- Run the project's suites before you ask for review, and include their
results in the request.
- Request a review when a task's acceptance evidence is complete.
- Request a review when a task's acceptance evidence is complete. Commit,
push, then call `request_review` with the commit `push_working`
returned and a reviewer role. Work that isn't pushed can't be reviewed.
- After a `changes` verdict, fix the findings, push again and ask again.
A task with pushed work closes only on an `approve` verdict for its
latest push.
## Authority