feat: cross-rig support for beads-creation-expansion#1
Draft
feat: cross-rig support for beads-creation-expansion#1
Conversation
The formula now detects cross-rig projects (where tasks target different rigs based on file paths) and creates beads in the correct rig's DB. Changes: - Draft step: rig detection from file paths, Target Rig field per issue - Execute step: group tasks by rig, cd to rig beads path before bd create - Cross-rig deps use full bead IDs with prefix - Integration branches created per-rig - Review pass checks rig assignment correctness - Report includes rig column in all tables Single-rig projects are unaffected — cross-rig detection is opt-in based on whether tasks have different target rigs in the coverage matrix. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Mar 5, 2026
Each secondary rig now gets a local epic before task creation, enabling --parent to work natively and gt mq integration create to operate without manual branch creation. Updated report template with Local Epics mapping table and Integration Branches table to reflect the new workflow. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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
What changed
The formula's draft step now extracts a Target Rig per task by parsing file paths (e.g.,
node0/mayor/rig/src/...→ node0). The execute step groups tasks by rig and runsbd createfrom each rig's beads path. Cross-rig blocking deps use full prefixed bead IDs (e.g.,pe-abcblocksno-xyz). Integration branches are created per-rig.The completeness review agent also checks rig assignments match file paths.
Motivation
When a project spans multiple rigs (e.g., petals + node0 + lora_forge), the old formula created ALL beads in one rig with that rig's prefix. This meant node0 tasks had
pe-prefix and lived in petals' DB — wrong rig's witness/refinery/polecats couldn't work them natively. Required manual migration after the fact.Test plan
bd dep addworks across rig boundaries🤖 Generated with Claude Code