Repository navigation
Require agents to push a working branch immediately and read open PRs - #866
Merged
rogerSuperBuilderAlpha merged 1 commit intoOct 28, 2026
Merged
Conversation
The harness told agents to branch off contrib and push once at the end. Every entry point now requires three things: push the working branch before the first edit, commit and push after every meaningful step, and read other remote branches and open pull requests so parallel work stays aligned. Co-authored-by: Roger Hunt <rogerSuperBuilderAlpha@users.noreply.github.com>
rogerSuperBuilderAlpha
added a commit
that referenced
this pull request
Oct 28, 2026
Promote contrib to main: researcher harness remote visibility rules (#866)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The researcher harness told agents to branch off
contriband push once, at the end. It did not tell them to push before editing, to keep pushing, or to read the other open branches and pull requests.Every agent entry point now states the same three rules:
git fetch --all --prune, create a branch offcontrib, andgit push -u origin <branch>before the first edit. Open a draft pull request intocontribwith the first commit.git branch -r --sort=-committerdate, recent commits across those branches, andgh pr list --state open. Join an in-flight branch when it already covers the question.mainandcontribstay protected. The push target is the working branch. The nested dissertation repo follows the same three visibility rules on its own remote.Files
AGENTS.md— canonical Remote visibility section, land flow, definition of doneCLAUDE.md,.cursorrules,.cursor/rules/remote-visibility.mdc,.cursor/rules/start-here.mdc,.github/copilot-instructions.mdREADME.md,NOW.md,START_HERE.md,OVERVIEW.md,llms.txt,CONTRIBUTING.md,GETTING_STARTED.md,PUBLISHING.md,REPO_LAYOUT.mdMAP.md,tools/build_map.pyAGENTS.mdfiles:org_frontier/,org_frontier/research/,org_frontier/qualitative/,org_frontier/survey/,org_frontier/recurrence/,foundations/,submissions/hospitality_phygital/,submissions/slacker_thirds/org_frontier/protocol/RESEARCH_PROTOCOL.md,org_frontier/protocol/README.md,org_frontier/protocol/new_question.py,org_frontier/protocol/question_pipeline.js,org_frontier/protocol/template/hypotheses.md,org_frontier/research/DAILY_REFRESH.mdsubmissions/dial_response_algorithmacy/corpus/CONTRIBUTING.mdThe Slacker arm still does not commit chapter prose unless the session was asked to land changes. When it was, the three rules apply.
Checks
Index
--checks for the map, directory, catalog, and research index are clean.new_question.pycompiles andquestion_pipeline.jspassesnode --check.Open work inspected before editing: one draft PR (#842, q221 temporal-null calibration) and the recent remote branches (Org Sci, harness path fixes, CFP arms, Berthon). None of them edit this harness rule.