Reverse spec drafted

Pipeline Builder

Pipeline stages, colours, transition requirements, fields, forms, automation and outcomes.

Observed route/admin/settings/pipelinesFuture Spec 09 →

Current maturityPartial builder with missing governance and execution depth

Evidence confidencePartially verified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

The live Pipeline directory and builder establish governed and Workspace-created Pipelines, but earlier review found incomplete stage-transition requirements, field/form governance, automation configuration and outcome semantics. Legacy Lead identifiers and routes also remain in the product and must be treated as migration aliases only.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Pipeline identity	Directory distinguishes available Pipelines but retains legacy Lead language elsewhere.	Verified in prior Pipeline pass
Stages and colours	Core configuration is visible; full semantic/reporting mapping is incomplete.	Partially verified
Transition requirements	Required-field and guarded transition behavior is not complete enough for production governance.	Known gap
Forms and automation	Future depth includes versioned forms, recipient-safe communication automation and idempotent domain actions.	Future requirement

User journeys

Current flows

Publish Pipeline

Create draft
Define stable record type and outcomes
Configure Stages, colours and SLAs
Configure fields/forms and transition requirements
Register automations
Validate migration impact
Publish immutable version

State model

Current and expected states

Draft

Expected builder state.

Published

Immutable version required.

Retired

Must preserve existing Pipeline Records.

Invalid configuration

Validation coverage is incomplete.

Product rules

Non-negotiable boundaries

Stage IDs and system meanings remain stable when labels change.
Pipelines create or qualify Entities; they do not replace Projects.
Automations emit idempotent commands from Domain Events.
Legacy Lead routes and LD identifiers are aliases only.
Published definitions are immutable.

Dependencies

Spec 09Dynamic formsDomain EventsNotifications and communicationsPermissionsMigration and audit

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 09 owns closure →

Missing builder depth is recorded in Spec 09.
Legacy Lead language remains.
Migration preview and rollback are not evidenced.

Future alignment

Required evolution

01Complete Spec 09 rather than layering one-off builders.
02Add Clients, Projects and general Workspace Pipelines.
03Add transition gates, automation testing, version comparison and migration preview.

Current baseline

Acceptance record

No builder surface is called complete without transitions, fields, forms, automation, outcomes and versions.
Stage customization cannot corrupt reporting mappings.
Legacy aliases are retired from user-facing UI.

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