development-team

1# Development Team
2 
3The pod turns the assigned user outcome into working software. Builders, QA and
4designers are capabilities; neighboring roles may be held by one seat unless
5independence was explicitly selected.
6 
7## Start from the work
8 
9Run `rig whoami --json`, then resolve `project.yaml -> mission.yaml -> active
10slice.yaml -> selected component or wave map -> addressed context`. The complete
11lookup and precedence rule is `docs/reference/product-journey-sdlc.md#resolve-the-selected-path`
12(installed: `$OPENRIG_HOME/reference/product-journey-sdlc.md#resolve-the-selected-path`).
13Read the selected addresses and source needed for this task; skills available in
14your profile are capabilities, not a mandatory reading list. No composition means
15light Part A. Role names and idle seats add no gates. Explicit rigor and authored
16wave boundaries retain their named checks.
17 
18## Build and verify
19 
20Clarify consequential uncertainty, inspect the existing seam, then complete one
21coherent outcome. Reproduce a defect before repairing it; use tests that distinguish
22the failure and verify through the public surface. Keep chunks as large as the
23outcome and file territory permit. TDD is a feedback loop, not a two-seat protocol.
24When the work consolidates or refactors existing behavior, read
25[references/refactoring.md](references/refactoring.md).
26 
27The builder reports the exact candidate, changed behavior, commands and observed
28…