BC
Brad CodyAdministrator
Current product→Access and application shell
Reverse spec drafted

Authenticated application shell

Persistent sidebar, workspace identity, page content area and shared authenticated navigation.

Observed route/adminFuture Spec 04 →
Current maturityWorking Admin shell with incomplete routes
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

The live Admin experience uses a persistent left navigation, an active Workspace card, a signed-in user area and a main content region. The Overview also exposes a top utility bar with Workspace search, Create, Help and Notifications. The Settings area swaps the primary navigation for a Settings-specific menu while preserving Workspace and user context.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Brand linkThe Design Registry wordmark links to /admin.Verified live
Active Workspace cardShows loading membership state, then Workspace name and context with a switch affordance.Verified loading and resolved states
Primary navigationAdmin navigation includes Overview, Pipelines, Applications, Matchmaking, Projects, Designer Studios, Providers, Clients, Assignments, Messages, Tasks, Proposals and Reports.Verified live
Settings entryLinks to /admin/settings/projects and replaces the primary menu with Settings navigation.Verified live
Top utility barOverview shows Workspace search, Create, Help and Notifications controls.Verified live
Signed-in user areaShows initial/avatar, identifier, access label and a three-dot account action.Verified live
Main content regionLoads the selected route and displays route-specific page title, content and actions.Verified live

User journeys

Current flows

01

Enter Admin

  1. Load /admin
  2. Render shell loading state
  3. Resolve signed-in User and Membership
  4. Resolve active Workspace
  5. Enable authorized shell and content
Observed result

Verified. Loading labels are replaced by Proper Gallery / Registry Administration and brad@bradcody.io / administrator.

02

Open Settings

  1. Select Settings
  2. Navigate to a Settings route
  3. Replace primary module navigation with Settings navigation
  4. Preserve active Workspace and user identity
  5. Offer Exit Settings
Observed result

Verified on /admin/settings/teammates.

03

Navigate modules

  1. Select a routed navigation link
  2. Load the module within the shared shell
Observed result

Most links use routes; Messages, Proposals and Reports are currently placeholders.

State model

Current and expected states

Workspace loading

Shows Loading Workspace…, Checking membership, Signed-in user and Loading access.

Workspace resolved

Shows Proper Gallery, Registry Administration, signed-in email and administrator access.

Admin navigation

Displays operational modules plus Settings.

Settings navigation

Displays Teammates, Teams, Role Labels, Workspace Profile, Project Builder, Pipeline Builder, Applications, Notifications, Task Builder and Data Reconciliation plus Exit Settings.

Incomplete route

Messages, Proposals and Reports appear in navigation but currently point to #.

Product rules

Non-negotiable boundaries

  • The active Workspace determines data and navigation context.
  • Hidden navigation is not authorization.
  • Workspace context must be resolved before protected data is trusted.
  • The Settings shell preserves the active Workspace and signed-in user.
  • Shared shell components should be reused for Admin, Designer, Provider and Client experiences with permission-filtered navigation.
Dependencies
Supabase sessionUser profileWorkspace MembershipActive Workspace resolverNavigation configurationRoute authorizationWorkspace-scoped data services

Known current limitations · 6 mapped

What is missing, broken or unverified

Future Spec 04 owns closure →
  1. Messages, Proposals and Reports have non-routable placeholder links.
  2. The resolved Workspace still displays the legacy name Proper Gallery.
  3. Loading content is visibly rendered before membership and Workspace resolution.
  4. Designer, Provider and Client shell variants have not been validated.
  5. Mobile, tablet, offline and connectivity behavior have not been validated.
  6. The repository implementation has not yet been traced for this reverse spec.

Future alignment

Required evolution

  • 01Replace legacy Workspace naming and seed data.
  • 02Complete all top-level routes or visibly label unavailable modules.
  • 03Generate navigation from Workspace type, Provider category, enabled modules and effective permissions.
  • 04Add responsive navigation and connectivity/data freshness behavior.
  • 05Prevent Workspace-loading flicker from revealing stale or previous-context content.

Current baseline

Acceptance record

  • Brand, Workspace context, navigation, user identity and content region are present.
  • Loading and resolved shell states are distinguishable.
  • Settings preserves context and provides Exit Settings.
  • Known placeholder routes and legacy naming are explicitly recorded.

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
← Feature inventoryOpen Future Spec 04 →