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

Shared Provider Profile

Shared Provider identity, Category Qualifications, capabilities, Service Areas, Matching Profile, Credentials, capacity and operational records.

Observed route/admin/providers/:idFuture Spec 05 →
Current maturityShared Provider Profile required; no live record available
Evidence confidenceKnown limitation
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

No Provider Profile can be opened because the live directory contains zero approved Provider Workspaces. The required model is one canonical Provider Entity and Workspace with shared identity, people, Network Status, Category Qualifications, Matching Profile, Credentials, capacity, Offers, Assignments, Project Jobs, commercial work and Activity, extended by one or more Category-specific modules.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Identity and standingAbsent; must include Provider ID, display/legal names, contacts, addresses, Relationship Owner, Network and Workspace status.Future requirement
Category QualificationsAbsent; one Provider may hold multiple independently governed qualifications.Future requirement
Matching ProfileAbsent; must combine shared Service Areas/capacity with Category-specific eligibility and fit data.Future requirement
CredentialsAbsent; category requirements determine applicable Credentials and review dates.Future requirement
People and accessAbsent; must reuse Teammates, Teams, Role Labels and Access Roles from the Provider Workspace.Future requirement
OperationsAbsent; Offers, Project Assignments, Provider Jobs, Proposals, Work Orders, Invoices, Files, Tasks, Communication, Performance, Activity and History must reuse shared modules.Future requirement

User journeys

Current flows

01

Approve and provision

  1. Approve Provider Application
  2. Resolve or create Provider Entity
  3. Create Category Qualification
  4. Provision Workspace and Owner Membership
  5. Seed Category profile and dashboard
  6. Publish to authorized directory views
Observed result

Defined in Spec 05; no live example available.

02

Add another Category

  1. Submit additional Category Application
  2. Review Category-specific evidence
  3. Approve new Qualification
  4. Extend the same Profile and Workspace
Observed result

Must not create a duplicate Provider.

State model

Current and expected states

Pending Application

Belongs to the Application Pipeline, not the approved directory.

Provisioning

Directory copy mentions provisioning but no row/state is visible.

Active

No example exists.

Category action required

No example exists.

Paused, Suspended or Offboarding

No example exists.

Product rules

Non-negotiable boundaries

  • One Provider Entity and Workspace may support many Category Qualifications.
  • Provider Profile is not an Application record.
  • Category-specific modules configure shared services instead of creating separate applications.
  • A Provider controls its own Workspace profile subject to governed verification fields.
  • Registry-only scoring, comparisons, risk and internal Notes never appear in the Provider Workspace.
  • Administrative Access Sessions use protected support-access rules.
Dependencies
Spec 05 Applications and provisioningProvider Category registryWorkspace and MembershipsSpec 08 Access RolesSpec 10 Matchmaking and AssignmentsSpec 06 commercial recordsSpec 07 Project JobsSpec 16 category workflows

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 05 owns closure →
  1. No live Provider Profile exists to verify.
  2. No Category-specific navigation, fields, dashboards or operational views can be inspected.
  3. The current directory cannot distinguish zero Providers from a failed load without deeper diagnostics.

Future alignment

Required evolution

  • 01Implement shared Provider Profile shell.
  • 02Add all nine category extensions below.
  • 03Reuse Designer Studio shared modules where semantics match.
  • 04Connect Provider Workspace profile editing, Category verification, Project Jobs and commercial operation.

Current baseline

Acceptance record

  • The missing live implementation is explicit.
  • One Provider/many Qualifications is protected.
  • Every Provider Category has its own product-library profile.

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 →