# What Is the Architect's Role in the SwarmForge Four-Pack? 5 Responsibilities Explained > Discover the architect's vital role in the SwarmForge four-pack. Learn how they ensure design integrity, enforce rules, harden code, and signal project completion for unclebob/swarm-forge. - Repository: [Robert C. Martin/swarm-forge](https://github.com/unclebob/swarm-forge) - Tags: architecture - Published: 2026-08-28 --- **In the SwarmForge four-pack workflow, the architect serves as the final quality gate who ensures overall design integrity, enforces dependency rules, hardens code against mutations, and signals project completion through a terminal broadcast.** The `unclebob/swarm-forge` repository implements a structured multi-agent coding workflow where four specialized roles collaborate sequentially. Understanding the architect's position at the end of this chain is essential for teams adopting this AI-assisted development methodology. --- ## The Four-Pack Workflow Overview The SwarmForge four-pack follows a strict handoff sequence: ``` specifier → coder → refactorer → architect → Done ``` Each role transforms incoming work and passes it forward. The architect receives the **refactorer's output** and performs final validation before marking a task complete. According to the project [[`README.md`](https://github.com/unclebob/swarm-forge/blob/main/README.md)](https://github.com/unclebob/swarm-forge/blob/main/README.md), this design ensures that architectural concerns receive dedicated attention rather than being distributed across earlier stages. --- ## Architect Responsibilities in the Four-Pack The architect's duties span five core areas, as documented in the source files. ### 1. High-Level Structural Oversight The architect defines and validates module boundaries, layering schemes, and dependency directions across the entire codebase. This responsibility appears in [[`README.md`](https://github.com/unclebob/swarm-forge/blob/main/README.md) lines 32-38](https://github.com/unclebob/swarm-forge/blob/main/README.md#L32-L38), which establish the architect as the sole role authorized to modify cross-cutting architectural decisions. ### 2. Dependency Direction Enforcement Using rules defined in [[`swarmforge/handoff-protocol.md`](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/handoff-protocol.md) lines 170-174](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/handoff-protocol.md#L170-L174), the architect confirms that components depend only on allowed lower-level layers. This prevents: - Circular imports - Layer violations - Unsafe cross-module dependencies ### 3. Mutation Hardening and DRY Review The architect scans for mutation-prone code patterns, eliminates duplicate logic, and applies "hardening" transformations that improve resilience to future changes. These duties are explicitly listed in [[`README.md`](https://github.com/unclebob/swarm-forge/blob/main/README.md) lines 37-38](https://github.com/unclebob/swarm-forge/blob/main/README.md#L37-L38). ### 4. Soft Gherkin Mutation Generated Gherkin acceptance specifications occasionally leak implementation details into the code. The architect refines these specifications to maintain expressiveness without excessive constraint, as noted in the same `README` section covering architect duties. ### 5. Final Completion Notification Once validation passes, the architect issues a **terminal broadcast**—the definitive handoff that closes the workflow cycle. --- ## Terminal Broadcast: Closing the Cycle The terminal broadcast represents the architect's final action in the four-pack. This handoff type, defined in [[`swarmforge/handoff-protocol.md`](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/handoff-protocol.md) lines 85-89](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/handoff-protocol.md#L85-L89), simultaneously notifies all prior roles that the task reaches `Done` status. ### Example: Architect-to-All Handoff ```text type: git_handoff to: specifier,coder,refactorer priority: 50 task: user-profile-feature commit: a1b2c3d9e0 ``` This broadcast differs from standard chain handoffs by targeting multiple previous roles rather than a single successor. --- ## Batch-Back Synchronization Beyond the terminal broadcast, the architect performs a **batch-back** operation sending each prior role a merge-only copy of the final commit. This synchronization mechanism, described in [[`README.md`](https://github.com/unclebob/swarm-forge/blob/main/README.md) lines 317-319](https://github.com/unclebob/swarm-forge/blob/main/README.md#L317-L319), ensures all participants remain aligned with the canonical project state. ### Example: Using the Helper Script ```sh # From the architect's worktree merge_and_process.sh architect a1b2c3d9e0 ``` The [[`merge_and_process.sh`](https://github.com/unclebob/swarm-forge/blob/main/merge_and_process.sh)](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/merge_and_process.sh) script validates the task name, canonicalizes abbreviated commit hashes, and queues handoffs for distribution—functionality detailed in [[`handoff-protocol.md`](https://github.com/unclebob/swarm-forge/blob/main/handoff-protocol.md) lines 53-58](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/handoff-protocol.md#L53-L58). --- ## Key Source Files for Architect Implementation | File | Purpose | |------|---------| | [[`README.md`](https://github.com/unclebob/swarm-forge/blob/main/README.md)](https://github.com/unclebob/swarm-forge/blob/main/README.md) | Four-pack workflow overview and architect duty list | | [[`swarmforge/handoff-protocol.md`](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/handoff-protocol.md)](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/handoff-protocol.md) | Handoff types, chain rules, terminal broadcast specification | | [`swarmforge/roles/architect.prompt`](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/roles/architect.prompt) | Prompt template defining architect agent inputs/outputs | | [[`swarmforge/merge_and_process.sh`](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/merge_and_process.sh)](https://github.com/unclebob/swarm-forge/blob/main/swarmforge/merge_and_process.sh) | Utility for validating and queuing final handoffs | --- ## Summary The architect in SwarmForge's four-pack workflow occupies a critical terminal position with these key functions: - **Validating structural integrity** through module boundary and layering review - **Enforcing dependency discipline** to prevent architectural decay - **Hardening code quality** via mutation resistance and DRY principle application - **Refining specifications** through soft Gherkin mutation - **Orchestrating closure** via terminal broadcast and batch-back synchronization This role transforms the four-pack from a linear pipeline into a guarded, quality-controlled development process where architectural concerns receive explicit rather than incidental attention. --- ## Frequently Asked Questions ### What makes the architect different from the refactorer in the four-pack? The refactorer focuses on local code quality improvements—renaming, extraction, and internal restructuring—while the architect operates at system scale. The architect enforces cross-module dependency rules, validates layering integrity, and performs final hardening transformations that the refactorer's narrower scope does not address. ### Can the four-pack workflow run without an architect? The SwarmForge source code treats the architect as mandatory in four-pack configuration. The [`handoff-protocol.md`](https://github.com/unclebob/swarm-forge/blob/main/handoff-protocol.md) specifies that only the architect can issue terminal broadcasts, meaning no other role possesses the mechanism to mark tasks complete. Omitting this role would break the defined workflow closure. ### What is a "soft Gherkin mutation"? Soft Gherkin mutation refers to the architect's refinement of acceptance test specifications that have become overly concrete or implementation-coupled. The architect adjusts these specifications to maintain their expressive value for behavior documentation while removing brittle constraints that would break with legitimate implementation changes. ### How does batch-back differ from the terminal broadcast? The **terminal broadcast** signals workflow completion to all roles simultaneously. The **batch-back** separately delivers merge-only commit copies to each prior role, allowing them to update their local state without reprocessing the entire handoff chain. These are complementary operations: one communicates status, the other distributes state.