Reverse spec drafted

Record tab system

Reusable Overview, Activity, Notes, Files, Tasks, Communication, Matchmaking, Proposals and History modules.

Observed routeShared componentFuture Spec 16 →

Current maturityStrong reusable profile shell with incomplete module contracts

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

Project Opportunity profiles demonstrate the shared Overview, Activity, Notes, Files, Tasks, Communication, Matchmaking, Proposals and History tab pattern. Projects and Entity profiles reuse portions of it. The shell is visually consistent, but Communication and Proposals remain unavailable, Activity and History can duplicate content, and role-specific module composition is not yet governed from one registry.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Profile header	Back link, title, state, metadata and primary actions are consistent.	Verified
Overview	Composed summary cards and recent-work projections.	Verified
Operational tabs	Activity, Notes, Files, Tasks and Matchmaking have working examples.	Verified
Unavailable tabs	Communication and Proposals are disabled or incomplete.	Verified
History	Can duplicate Activity rather than present distinct immutable audit changes.	Verified conflict

User journeys

Current flows

Operate a record

Open Profile
Resolve audience/module registry
Review Overview
Enter task-specific module
Perform authorized action
Update shared record and projections
Return without losing context

State model

Current and expected states

Module available

Working tabs render content.

Empty

Shared modules provide varying empty states.

Coming soon

Not consistently labelled.

Unauthorized

Redaction/removal behavior not explicitly evidenced.

Product rules

Non-negotiable boundaries

Tabs are projections over shared services, not duplicate stores.
Module availability is determined by record type, audience, feature readiness and permissions.
Unavailable modules are labelled Coming soon or omitted; they are never dead clicks.
Activity and History have distinct contracts.
Deep links preserve active tab.

Dependencies

Module registryProfilesActivity, Notes, Files, Tasks, Communications, Matchmaking and Commercial servicesPermissionsFeature flags

Known current limitations · 4 mapped

What is missing, broken or unverified

Future Spec 16 owns closure →

Dead/disabled modules are inconsistently labelled.
Activity/History purpose conflict.
Audience composition is not visible as one governed registry.
Deep-link and mobile overflow behavior are not fully verified.

Future alignment

Required evolution

01Create one module registry and availability contract.
02Reuse shared services across every profile.
03Add explicit loading, empty, unavailable, unauthorized and error states.

Current baseline

Acceptance record

Every tab has an owner and data contract.
No unavailable tab appears broken.
Activity and audit History are not duplicates.
Permissions apply before counts and content render.

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