H.4.1 Team Boundaries

Repository layout influences team work but does not determine responsibility.

• Domain teams can own end-to-end flow; component teams concentrate expertise but can become a queue.
• Platform teams provide a service or paved road; federated models keep decisions near ecosystems while adding coordination.
• Enabling and migration teams should transfer capability or finish a bounded transition rather than become accidental permanent owners.
• Choose collaboration, facilitation, or service interaction deliberately and state when the mode ends.
• Evaluate boundaries through cognitive load, dependency direction, review wait, incidents, and cross-boundary change frequency.