BC
Brad CodyAdministrator
Current product→Entities and profiles
Reverse spec drafted

Providers directory

Provider list grouped and filtered by qualified Provider Category.

Observed route/admin/providersFuture Spec 05 →
Current maturityPolished empty directory without Category architecture exposed
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

The live Providers directory has shared search, metrics, sort, export, columns and an application-review link, but contains zero provisioned Provider Workspaces. Its only Category filter option is All. As a result, none of the nine canonical Provider Categories, their counts, recruitment gaps, Category Qualifications or profile requirements are discoverable.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
HeaderRegistry · Provider network, Providers and approved Workspace description.Verified live
Application handoffReview applications links to /admin/applications.Verified live
MetricsProvider Workspaces, Network Active, Available and Teammates are all zero.Verified live
Category filterOnly All is present.Critical omission verified live
GridProvider Workspace, Provider Type, Market, Services, Capacity, Readiness, Teammates, Updated and Actions.Verified live
Empty stateApproved Provider Workspaces will appear after provisioning completes.Verified live

User journeys

Current flows

01

Browse a Provider Category

  1. Open Providers
  2. Choose one of nine Provider Categories
  3. Review qualified, available, onboarding and action-required counts
  4. Filter Service Area, services, readiness, capacity and Credentials
  5. Open Provider Profile
Observed result

Blocked because categories and Provider rows are absent.

02

Recruit into a gap

  1. Open a zero-count Category
  2. Review market and service gaps
  3. Start application invitation or recruitment workflow
Observed result

No category-level empty state or action exists.

State model

Current and expected states

No Provider Workspaces

All metrics are zero and one generic empty row appears.

Category zero

Not represented individually.

Qualified Provider

No example exists.

Readiness or Credential action

No example exists.

Product rules

Non-negotiable boundaries

  • The directory always exposes all nine canonical Provider Categories and zero counts.
  • Use Provider Category, not Provider Type.
  • One Provider may have multiple Category Qualifications without duplicate Entity or Workspace rows.
  • Network Status, Category Qualification, readiness, capacity and Workspace Status remain separate.
  • Contact and commercial fields obey permissions and export restrictions.
Dependencies
Provider Category registryProvider EntitiesCategory QualificationsProvider WorkspacesApplications and provisioningCredentialsCapacityEnterprise data gridPermissions

Known current limitations · 5 mapped

What is missing, broken or unverified

Future Spec 05 owns closure →
  1. No Provider records exist.
  2. Only All appears in the category filter.
  3. The grid uses Provider Type rather than Provider Category.
  4. No Category counts, qualification states, recruitment actions or profile examples exist.
  5. Search, export and columns cannot be validated with data.

Future alignment

Required evolution

  • 01Show all nine Category cards/filters and counts.
  • 02Add Category Qualification and readiness summaries.
  • 03Provide category-aware empty states and recruitment/application actions.
  • 04Open one shared Provider Profile extended by Category modules.
  • 05Connect availability and capacity to source-aware scheduling data.

Current baseline

Acceptance record

  • The empty live state and every missing Category are explicit.
  • Zero Providers is not represented as feature completion.
  • All nine Provider Category profiles appear in the product library.

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 05 →