Skip to content

chore: raise loop-lane merge rung to c3-autonomous #1693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kyle-sexton wants to merge 1 commit into from
Closed

chore: raise loop-lane merge rung to c3-autonomous #1693

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/source-control.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ worker

## babysit_loop_merge

c2-mechanical
c3-autonomous

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep C3 changes behind human merge

For any merge-capable babysit-loop invocation that does not pass a lower merge cap, this makes C3 PRs eligible for unattended merge, even though plugins/autonomy/reference/guardrails.md:19-25 defines C3 as human-merge and provides no promotion path for that cell. The repository-specific profile is even more explicit: prompts/loops/loop-lane-prompts.md:1177-1185 records the operator's decision against this raise, notes that nearly the entire agent-ready backlog would become eligible, and requires amending the guardrail contract first. Revert this raise unless that governing policy and authorization are changed first.

Useful? React with 馃憤聽/ 馃憥.


## babysit_loop_grace_window_minutes

Expand Down
Loading