Reverse spec drafted
Photography
Portfolio, shoot types, usage rights, deliverables, equipment, travel, scheduling and post-production capabilities.
Observed route
/admin/providers?category=photographyFuture Spec 05 →Current-state summary
Photography is one of the nine canonical Provider Categories. The live Providers directory contains zero provisioned Workspaces and exposes only an All filter, so this Category has no discoverable directory view, count, sample profile or Category-specific operational module. The category contract below records what must appear when the shared Provider Profile is configured for Photography.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Shared Provider identity | No live Provider row or profile exists. Required shared identity includes legal/display name, Provider ID, contacts, address, markets, Service Areas, Network Status and Workspace relationship. | Verified absent from live directory |
| Category Qualification | Must identify Photography qualification status, verification dates, services and readiness without creating a duplicate Provider Entity. | Future requirement from Spec 05 |
| Category profile data | Portfolio, shoot types, aesthetic, equipment, travel, crew, styling support, turnaround, retouching, deliverable formats and usage-right packages. | Required category contract; not implemented live |
| Matching Profile | Aesthetic fit, Project type, location, date availability, deliverables, usage, budget, turnaround and special equipment. | Required category contract; not implemented live |
| Credentials and evidence | Insurance, portfolio provenance, references, model/property release practices, usage-right terms and drone certification where applicable. | Required category contract; not implemented live |
| Operational handoff | Brief, shot list, scheduling, access, capture, selects, retouching, review, final delivery, licences and archive. | Required Project/Provider workflow; not implemented live |
User journeys
Current flows
01
Discover qualified Provider
- Open Providers
- Choose Photography
- Review count, readiness and Service Area filters
- Open a qualified Provider Profile
- Review Category Qualification, capabilities, capacity and evidence
02
Use Provider on a Project
- Create a Project Provider Requirement
- Run Matchmaking for Photography
- Review eligible Match Candidates
- Issue Work Package or Offer
- Accept commercial scope
- Create Project Assignment and Provider Job
- Operate the work and evidence in the Provider Workspace
State model
Current and expected states
Category unavailable
The Providers filter contains only All.
Zero qualified Providers
No Category-specific empty state, recruitment action or count is shown.
Qualified and active
No live example exists.
Credential action required
No live example exists.
Paused, suspended or offboarding
No live example exists.
Product rules
Non-negotiable boundaries
- Provider Category is the canonical label; Provider Type is a current UI term to retire.
- One Provider Entity may hold multiple Category Qualifications without duplicate profiles or Workspaces.
- Category configuration extends shared modules rather than forking the Provider application.
- Qualification, Network Status, Workspace Status, readiness and Matchmaking eligibility are distinct states.
- Directory counts remain visible at zero so network gaps are actionable.
- Category-specific fields, Credentials and operational data obey permissions and freshness rules.
Dependencies
Provider EntityProvider Category registryProvider Category QualificationProvider WorkspaceMatching ProfileCredential serviceProvider ApplicationsProjects and Work PackagesOffers, Proposals, Work Orders and AssignmentsCategory-specific Provider operations
Known current limitations · 4 mapped
What is missing, broken or unverified
Future Spec 05 owns closure →- No approved Provider Workspace exists in the live directory.
- The Category is not present in the filter.
- There is no sample profile, readiness model, credential summary, Matchmaking projection or Project operating view.
- Route behavior for the proposed category query is not implemented.
Future alignment
Required evolution
- 01Expose this Category in the Providers directory at zero and populated counts.
- 02Build its application and Category Qualification through Spec 05.
- 03Render shared identity plus the Category-specific profile contract above.
- 04Connect Matchmaking, Work Packages, commercial records and the relevant Project operating workflow.
- 05Add Category-specific dashboard and Provider Job projections without forking shared services.
Current baseline
Acceptance record
- The Category appears explicitly in the current-product library.
- Its absence from the live directory is not mistaken for completion.
- Shared and Category-specific data are distinguishable.
- No generic Provider profile is considered sufficient for this Category.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented