Reverse spec drafted

Pipeline record profile

Shared detailed record experience used by Project Opportunities and applications.

Observed route/admin/leads/:idFuture Spec 09 →

Current maturityRich reusable profile with working modules and unresolved canonical identity drift

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

The live Project Opportunity record is a shared profile shell with persistent identity, stage, metadata and module navigation. LD-101 Forest Hill Residence has seven working module tabs. Proposals and History are now correctly disabled and labeled Coming soon. The second pass confirmed that Actions can receive active styling but exposes no visible menu, the overflow button has no verified outcome, and the profile disagrees with its Pipeline row on identifier, stage and age. These are signs that the profile still projects a legacy Lead record rather than one canonical versioned Pipeline Record.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Record header	Shows back link, Project title, stage, record ID, age and source.	Verified live on LD-101
Primary actions	Open Matchmaking and Convert to Project are persistent. Actions toggles active styling without a visible menu; overflow has no verified behavior.	Verified live; conversion intentionally not executed
Tab navigation	Seven working tabs remain selectable. Proposals and History are disabled with Coming soon labels.	Verified live after product correction
Record body	Swaps dedicated modules for seven tabs while preserving header context.	Verified
Edit surfaces	Overview cards expose Edit actions and a standardized sectioned form.	Verified from live content and prior evidence
Canonical identity projection	Profile shows LD-101, Qualified and 2d while its Pipeline row shows PO-00001, Qualification and 3 days.	Verified live

User journeys

Current flows

Review a record

Open a Pipeline card
Confirm identity and stage
Review Overview
Open relevant work tab
Return without losing context

Convert to Project

Select Convert to Project
Validate readiness and required fields
Resolve Client
Create Project
Link conversion history

Encounter planned module

Review Proposals or History
See disabled state and Coming soon label
Remain in the current working tab

State model

Current and expected states

Record available

LD-101 loads the complete header and profile.

Record not found

A stale ID displayed Project Opportunity not found with a back link.

Dedicated tab active

Active state and correct body appear for seven tabs.

Planned tab

Proposals and History are visible for roadmap context but disabled and labeled Coming soon.

Header action without surface

Actions can become active without displaying a visible menu.

Conversion-ready or blocked

Button exists; readiness modal and validation were not tested.

Product rules

Non-negotiable boundaries

One canonical Pipeline Record ID, stage and timestamp projection must be used across board, table, profile, Activity and APIs.
Project Opportunities use PO identifiers in the active product; LD identifiers survive only as restricted migration aliases and redirect lookups.
Record identity and actions persist across tabs.
Tab visibility must reflect enabled modules and effective permissions.
Active tabs must render matching content; planned tabs remain disabled with an honest availability state.
Conversion must be idempotent and audited.
Shared record modules should be configured rather than copied for each entity type.

Dependencies

Pipeline recordClient resolutionRecord tab registryDynamic form systemTask, file, note and communication servicesMatchmakingProject conversion

Known current limitations · 7 mapped

What is missing, broken or unverified

Future Spec 09 owns closure →

Critical: profile and Pipeline directory disagree on the record ID, stage label and age.
Record URLs do not encode the selected tab, so refresh and direct-link behavior are limited.
Actions toggles active styling without a visible menu; overflow behavior is unverified.
Convert to Project is always visible, while readiness and required-field feedback were not observed.
The record still contains legacy Proper Gallery commission terminology.
Permission-based tab and field redaction were not validated.
Proposals and History have no module yet, although their disabled state is now accurate.

Future alignment

Required evolution

01Make the profile shell entity- and Pipeline-configurable.
02Use the canonical PO identifier and Pipeline Record route; retain old Lead URLs only as safe redirects.
03Give every enabled tab a routable deep link and correct empty/loading/error state.
04Replace legacy business terminology with Workspace-configured labels.
05Use one conversion framework for entity creation and Project creation outcomes.

Current baseline

Acceptance record

Header identity remains stable across working tabs.
Seven working modules render correct dedicated content.
Not-found behavior returns safely to the directory.
Proposals and History remain disabled until real modules exist.
Canonical ID, stage and age mismatches are visible as reconciliation blockers.
Conversion is not claimed as verified without executing it.

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