docs(agents): clarify beads ownership for research#1333
Merged
Conversation
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
1 participant
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.
Summary
AgentV workers now have an explicit Beads ownership boundary: AgentV Beads are reserved for committed AgentV repository deliverables, while research-only and cross-repo orchestration records stay in
/home/entity/ntm_Dev/agent-orchestrator.This should prevent AgentV history from accumulating Beads-only research dispatch or status commits when no AgentV deliverable is expected.
Verification
AGENTS.mdbefore editing.AGENTS.md-only docs update.--no-verifybecause the dedicated docs worktree has nonode_modules/tsc, so the local pre-push hook cannot run there. Dependencies were not installed just for this; CI will run on the PR.