BC
Brad CodyAdministrator
Current product→Pipelines and record experience
Reverse spec drafted

Pipeline directory

Workspace list and entry point for available governed and Workspace-created Pipelines.

Observed route/admin/pipelinesFuture Spec 09 →
Current maturityWorking intake surface over a partially connected workflow configuration
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

The live Pipelines route is the shared intake entry point. It exposes Project Opportunities version 1 with Admin conversion to Project and matching during intake, plus metrics, swim lanes and a table. Retry recovered an initial load failure and loaded three records across six stages. A second pass found the deeper Settings directory contains two published workflows and nine draft Provider-application workflows, while only Project Opportunities is selectable on this operational route. More importantly, the New opportunity form is still driven by the legacy Lead schema and stage list rather than the published six-stage workflow.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Page identityShared intake engine label, Pipelines title and explanatory copy define the module purpose.Verified live
Primary actionsConfigure pipeline links to the workflow directory. New opportunity opens a 43-field legacy Lead form; creation was not submitted.Form and all field groups reviewed live
Active Pipeline selectorShows Project Opportunities as the selected Pipeline.Verified live; multi-Pipeline switching not tested
Governance summaryShows Published, Version 1, Admin converts to project and matching available during intake.Verified live
Operational metricsShows open records, open value, weighted value, attention, conversion readiness, active stages and version.Verified with 3 records, $1.645M open and $777,250 weighted
View controlsSwim lanes and Table share a 3 records / 6 stages count. Table includes selection, sorting, export and a configurable column manager.Verified live in second pass
Workflow directory relationshipSettings lists Project Opportunities and Designer Applications as Published plus nine Provider application workflows as Draft.Verified live
Load recoveryA failed first load showed an inline error and Try again; retry succeeded without leaving the page.Verified live

User journeys

Current flows

01

Review intake

  1. Open Pipelines
  2. Resolve active Pipeline
  3. Review governance and metrics
  4. Scan stages and records
  5. Open a record
Observed result

Verified through opening Forest Hill Residence / LD-101.

02

Recover from load failure

  1. Receive inline load error
  2. Select Try again
  3. Reload Pipeline data
  4. Restore metrics and stages
Observed result

Verified; retry recovered three records.

03

Configure Pipeline

  1. Select Configure pipeline
  2. Open workflow directory
  3. Choose Project Opportunities
  4. Create a draft
  5. Configure and publish
Observed result

Directory and published builder verified. Only Overview and Stages/next steps currently have implemented content; six other sections are placeholders.

04

Create opportunity

  1. Select New opportunity
  2. Complete core, contact, Project, qualification, assignment, matching and snapshot fields
  3. Create record
Observed result

Form reviewed but not submitted. Its legacy stage choices do not match the active published workflow and therefore fail the configuration-as-source-of-truth requirement.

State model

Current and expected states

Loading

Shell can resolve before Pipeline data; dedicated skeleton behavior was not captured.

Loaded

One published Pipeline, metrics, six stages and three records are present.

Load failed

Shows a Workspace-scoped error and Try again.

No records

Individual empty stages show No records with a zero count.

Multiple Pipelines

Operational selector exposes only Project Opportunities; Settings contains eleven workflow definitions serving intake and applications.

Product rules

Non-negotiable boundaries

  • Pipeline data is scoped to the active Workspace.
  • The active published workflow is the only source of stage, transition, field and outcome configuration.
  • Published version and conversion ownership must be visible.
  • Summary values derive from records and stage probabilities rather than editable dashboard numbers.
  • Retry must not duplicate records or mutate stage state.
  • Application workflows may share the engine without appearing as operational lead Pipelines in the wrong directory.
Dependencies
Active WorkspacePipeline definitions and versionsPipeline recordsStage probabilitiesRecord ownershipSettings Pipeline BuilderProject conversion service

Known current limitations · 6 mapped

What is missing, broken or unverified

Future Spec 09 owns closure →
  1. Critical: New opportunity uses legacy stages that do not match the published workflow.
  2. The workflow directory and operational selector expose different notions of available Pipelines without explaining the scope difference.
  3. The first data request failed once before successful retry.
  4. Search, filtering and cross-Pipeline reporting are not visible on the directory surface.
  5. The selected Workspace and form fields still use legacy Proper Gallery naming.
  6. New opportunity submission, validation and duplicate detection were not tested.

Future alignment

Required evolution

  • 01Support governed Registry Pipelines and Workspace-created general CRM Pipelines through one directory.
  • 02Expose Pipeline type, owner, version and health consistently.
  • 03Replace visible legacy Lead IDs, labels and routes with canonical Pipeline Record identity; keep LD aliases only for redirects and audit.
  • 04Add resilient loading, filters and saved views without fragmenting the shared engine.
  • 05Preserve historical records against the version under which they were created.

Current baseline

Acceptance record

  • The active Pipeline, publication state and version are visible.
  • Conversion and matching configuration are summarized.
  • Metrics reconcile to the visible Pipeline.
  • A recoverable error state exists.
  • Records can be opened from the current view.
  • Creation is explicitly flagged as configuration-divergent until it consumes the active published workflow.

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 09 →