Reports and operational intelligence
Audience-specific Registry, Designer Studio and Provider reporting built from authorized canonical records.
Coming soon — no routeFuture Spec 15 →Current-state summary
Reports appears in primary navigation as a non-routable # link with no Coming soon badge. No report catalogue, dashboard, metric definition, filter, drilldown, export or scheduled delivery surface exists. The future product must separate Registry network intelligence from Designer Studio business reporting and Provider operational/business reporting rather than exposing one generic dashboard.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Navigation | Disabled # link without Coming soon label. | Verified live |
| Report catalogue | Absent. | Verified absent |
| Metric definitions | No formula, owner, time zone, currency, grain, freshness or as-of metadata exists. | Verified absent |
| Filters and drilldown | Absent. | Verified absent |
| Export and schedule | Absent. | Verified absent |
User journeys
Current flows
Registry operating review
- Choose Registry report
- Set market/date/category scope
- Review network, application, Matchmaking, Project, Provider and transaction health
- Drill into authorized records
- Export or schedule permitted summary
Designer Studio review
- Choose Studio report
- Review Pipeline, Project, workload, time, budget, procurement, revenue and Client-response metrics
- Drill into own records
Provider review
- Choose Provider report
- Review Offers, win rate, Work Orders, capacity, SLA, exceptions, invoicing and payments
- Drill into own Provider Jobs
State model
Current and expected states
Implied but not labelled.
Not represented.
Not represented.
Not represented.
Not represented.
Product rules
Non-negotiable boundaries
- Registry, Designer Studio and Provider reports are separate audience scopes over shared metric services.
- Every metric has a definition, owner, dimensions, grain, time zone, currency behavior, freshness and source lineage.
- Reports never bypass record or field permissions.
- Dashboard projections are not independent business state.
- Exports apply the same access controls and record their actor and scope.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 15 owns closure →- No report implementation exists.
- No audience separation is visible.
- No metric catalogue, data lineage, freshness, drilldown, export or scheduling can be verified.
Future alignment
Required evolution
- 01Label Reports Coming soon immediately.
- 02Implement Spec 15 and its governed metric catalogue.
- 03Build separate Registry, Designer Studio and Provider report catalogues.
- 04Add permission-safe drilldown, saved filters, exports, scheduled delivery and freshness indicators.
Current baseline
Acceptance record
- Reports is not described as working.
- The three audience scopes are explicit.
- No metric ships without a governed definition and source lineage.
- Exports and drilldowns cannot reveal inaccessible records or fields.
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