Reverse spec drafted

Teams

Create and maintain groups used for organization, assignment and operational routing.

Observed route/admin/settings/teamsFuture Spec 03 →

Current maturityWorking empty-state Team directory

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

Teams provides a zero-state directory with New team, Team, Members and Team lead columns, sorting, Export and Columns. Its page copy correctly states that Teams organize work without changing Workspace access.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Directory	Zero Teams with shared grid controls.	Verified live
New team	Creation entry point is visible; form and persistence were not exercised.	Visible only
Access explanation	Explicitly says Teams do not change Workspace access.	Verified live

User journeys

Current flows

Create Team

Open Teams
Select New team
Name Team
Choose one optional Team Lead
Add eligible Memberships
Save
Expose Team to supported assignment and routing controls

State model

Current and expected states

Empty

No Teams exist.

Active

Not evidenced.

Archived

Not evidenced.

Product rules

Non-negotiable boundaries

Teams do not grant permissions.
Members must hold active Memberships in the same Workspace.
A Team Lead is an operational designation, not automatic authority.
Archived Teams remain resolvable in history.

Dependencies

Workspace MembershipsAssignment pickersTask routingNotificationsReporting

Known current limitations · 2 mapped

What is missing, broken or unverified

Future Spec 03 owns closure →

No populated Team or creation form was reviewed.
No archive, membership history or downstream usage is visible.

Future alignment

Required evolution

01Complete Team lifecycle in Spec 03.
02Reuse Teams in Tasks, Projects, queues and notifications.
03Preserve permission neutrality in every picker.

Current baseline

Acceptance record

Zero state is explicit.
Team is never described as an Access Role.
Same-Workspace membership is enforced.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented