Skip to content

Gas City Convoy Workflow for Drupal Rigs

Classification: PROCEDURE. Not authority; the governing standard below owns the rules.
Authority: gas-city-factory-board
Platform Reference: https://docs.gascity.com/

1. Operating Model: Convoys & Beads

Every Drupal task executes inside a canonical Gas City Convoy tracking native Beads:

CONVOY (Objective / Grouping) ──> BEAD (Atomic Work Unit) ──> RIG (Drupal Workspace)
                                                               └──> AGENT (Worker)
                                                               └──> GITLAB MR (Delivery)

2. Standard Execution Lifecycle

1. CLAIM BEAD       : bd update <bead-id> --assignee=agent-drupal --status=in_progress
2. CREATE WORKTREE  : git worktree add worktrees/<bead-id> -b feature/<bead-id>
3. IMPLEMENT (CONTRIB FIRST) : Use Drush generators, recipes, and existing contrib modules
4. TEST & VERIFY    : Run PHPUnit / Drush tests locally
5. COMMIT & PUSH    : git commit -m "feat(<bead-id>): description" && git push -u origin feature/<bead-id>
6. OPEN MR          : Open GitLab MR targeting release/v0.1.x
7. VERIFY CI        : Verify pipeline passes in gitlab_components
8. CLOSE BEAD       : bd close <bead-id> (Auto-closes tracked convoy when all members close)
9. CLEAN WORKTREE   : git worktree remove worktrees/<bead-id>

3. Invariants

  • Never develop directly on NAS (/Volumes/AgentPlatform/... is prohibited).
  • Never target main directly; all feature MRs target release/v0.1.x.
  • No uncommitted code left behind in worktrees.
  • Pipeline waiting is not agent idle time; claim next ready bead while CI runs.