docs: chose your tea engagement

docs/modules/bmm-bmad-method/index.md

@@ -40,6 +40,8 @@ First know there is the full BMad Method Process and then there is a Quick Flow
   - Implementation in minutes, not days
   - Has a specialized single agent that does all of this: **[Quick Flow Solo Dev Agent](./quick-flow-solo-dev.md)**
 
+- **Testing posture (optional)** - Choose TEA engagement: none, TEA-only (standalone), or integrated by track. See **[Test Architect Guide](./test-architecture.md)**.
+
 ## 🤖 Agents and Collaboration
 
 Complete guide to BMM's AI agent team:

docs/modules/bmm-bmad-method/quick-start.md

@@ -179,6 +179,16 @@ Once epics and stories are created:
 
 **Why run this?** It ensures all your planning assets align properly before you start building.
 
+#### Optional: Testing Posture (TEA)
+
+Testing is not mandated by BMad. Decide how you want to engage TEA:
+
+- **No TEA** - Use your existing team testing approach
+- **TEA-only (Standalone)** - Use TEA workflows with your own requirements and environment
+- **TEA-integrated** - Use TEA as part of the BMad Method or Enterprise flow
+
+See the [Test Architect Guide](./test-architecture.md) for the five TEA engagement models and recommended sequences.
+
 #### Context Management Tips
 
 - **Use 200k+ context models** for best results (Claude Sonnet 4.5, GPT-4, etc.)

docs/modules/bmm-bmad-method/test-architecture.md

@@ -6,6 +6,38 @@
 - **Mission:** Deliver actionable quality strategies, automation coverage, and gate decisions that scale with project complexity and compliance demands.
 - **Use When:** BMad Method or Enterprise track projects, integration risk is non-trivial, brownfield regression risk exists, or compliance/NFR evidence is required. (Quick Flow projects typically don't require TEA)
 
+## Choose Your TEA Engagement Model
+
+BMad does not mandate TEA. There are five valid ways to use it (or skip it). Pick one intentionally.
+
+1. **No TEA**
+   - Skip all TEA workflows. Use your existing team testing approach.
+
+2. **TEA-only (Standalone)**
+   - Use TEA on a non-BMad project. Bring your own requirements, acceptance criteria, and environments.
+   - Typical sequence: `*test-design` (system or epic) -> `*atdd` and/or `*automate` -> optional `*test-review` -> `*trace` for coverage and gate decisions.
+   - Run `*framework` or `*ci` only if you want TEA to scaffold the harness or pipeline.
+
+3. **Integrated: Greenfield Simple (BMad Method)**
+   - Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
+   - Phase 4: per-epic `*test-design`, optional `*atdd`, then `*automate` and optional `*test-review`.
+   - Gate: `*trace` Phase 2.
+
+4. **Integrated: Brownfield Enterprise**
+   - Phase 2: baseline `*trace`.
+   - Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
+   - Phase 4: per-epic `*test-design` focused on regression and integration risks.
+   - Gate: `*nfr-assess` (if not done earlier) and `*trace` Phase 2.
+   - For brownfield BMad Method, follow the same flow with `*nfr-assess` optional.
+
+5. **Integrated: Greenfield Enterprise**
+   - Phase 2: `*nfr-assess`.
+   - Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
+   - Phase 4: per-epic `*test-design`, plus `*atdd`/`*automate`/`*test-review`.
+   - Gate: `*trace` Phase 2 and archive artifacts as needed.
+
+If you are unsure, default to the integrated path for your track and adjust later.
+
 ## TEA Workflow Lifecycle
 
 TEA integrates into the BMad development lifecycle during Solutioning (Phase 3) and Implementation (Phase 4):