Team
Team now acts as the front-end workbench for future membership, project scope, role boundaries, and execution permission checks. The data is still scaffolded, but it now flows through a shared workbench service boundary and includes empty and error demos for testing.
Team Workbench
Team is now framed around real roles and future permission gates
The page is still sample-backed, but it now models who owns the workspace, who can operate the platform, and where future RBAC checks must attach before execution begins.
Service boundary: module-1-shared-workbench-service · demo:error
Owners
--
Active members
--
Invites pending
--
Team state
Membership data is currently unavailable
This error-state demo models the future org or RBAC boundary failing before the member table loads.
Module 1 needs the shell now so Module 5 can later add real permission errors without changing the front-end structure.