- GroupVM preserves homogeneous collection behavior without Current.
- Children are still owned and lifecycle-managed by the group.
- The group itself may be selected by its own parent.
- Groups and composites publish the same VM collection-change contract.
- Move changes order without reconstructing, reparenting, or replacing the child.
- Batch updates collapse many mutations to one Reset.
- Lifecycle orchestration matches CompositeVM without selection work.
- Use groups for toolbars, notification stacks, peer panels, and capability rows.
- Use CompositeVM when current selection matters.
- Use AggregateVM when child roles are fixed and heterogeneous.