Architectural decision
Shared UI does not imply shared authority
Several spaces need members, files and activity views.
Before · Conflated concepts
SpaceTeamProductionNetworking Community
After · Explicit boundaries
Relationships
- Space includes the concept of Production
- Space includes the concept of Team
- Space includes the concept of Networking Community
Problem and decision
A reusable navigation pattern can be mistaken for universal ownership and permissions.
Reuse presentation primitives while keeping security and lifecycle domain-specific.
Alternatives considered
- Merge all collaboration spaces into one authority model
- Duplicate every visual component per domain
Tradeoffs and consequences
Shared components need explicit context contracts.
Team, Production and Community retain independent boundaries.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.