Member directory
A single directory of account members with their effective project scope, role posture, and last activity.
Workflow-first MVPDocs Center liveHelp routes reservedProjects & Billing in codeSupply & Marketplace in code
Team
Team now carries the shared execution pre-check order on top of its dedicated module entrance. Member directory, owner/operator/member boundary lanes, permission posture, and billable execution rules are all derived from one shared model, while empty and error demos remain available for testing.
Team Workbench
Team now reads, activates, and refreshes scope through one shared foundation
Module 5 Day 10 now keeps the member directory on D1-backed org data, invite writes, activation enforcement, and selected-member scope refresh on one path, so later RBAC work does not need to rebuild the team surface from a read-only scaffold.
Service boundary: workbench-control-plane-service
Owners
1
Active members
30
Invites pending
2
Boundary lanes
User-facing owner, operator, and member lanes explain who owns the account root and who only acts inside narrower scopes.
Permission ladder
The Team module keeps the identity-to-credit permission sequence visible before later enforcement becomes active.
Execution rules
Billable execution stays attached to the same shared org model, so testing never bypasses permission or credit gates.
Member directory
Boundary labels now explain whether a person owns the account, operates review surfaces, or builds inside a project scope.
MemberBoundaryRoleStatusProjectsLast active