Reverse spec drafted

Projects directory

Portfolio list and entry point for active and historical Projects.

Observed route/admin/projectsFuture Spec 07 →

Current maturityFunctional portfolio grid with prototype Project data

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

The live Projects directory is an enterprise-grid portfolio for two seeded Projects. It exposes Workspace search, four operational metrics, row selection, sixteen sort options, export, configurable columns and a structured New Project form. The directory correctly labels the current workflow position as Current phase, but Project phase values and health labels are rendered in lowercase. The page describes the record as a durable project book; the canonical domain term remains Project Record.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Page header	Operations center, Projects, durable project-book description and New project action.	Verified live
Portfolio metrics	Active Projects 2, On Track 1, Open budget $1,320,000 and Average progress 20%.	Verified live
Search and count	Search projects input and 2 Projects count.	Verified live
Sort	A–Z/Z–A controls across Project, Project ID, Current phase, Progress, Health, Location, Budget and Target.	Verified live
Enterprise grid	Selection, Project, Project ID, Current phase, Progress, Health, Location, Budget, Target and Actions columns.	Verified live
Seeded Projects	Rosedale Residence PR-00001 and Oakville New Build PR-00002 open dedicated Project routes.	Verified live
New Project form	Requires Project Template, Project name and Client identity; includes addresses, assignments, matching criteria, Project Snapshot and Vision.	Verified without creating a record

User journeys

Current flows

Find and open a Project

Search or sort the portfolio
Review authorized phase, progress, health, location, budget and target
Select the Project row
Open its canonical Project Record

Create a Project

Select New project
Choose a published Project Template
Enter Project and Client information
Optionally enter assignments, matching and financial planning data
Create the Project

State model

Current and expected states

Loading

Metrics initially show zero and the directory displays Loading projects….

Populated

Two Projects and calculated portfolio metrics appear.

Needs Attention

Oakville is labeled needs attention without a visible reason in the directory.

No completion target

Target displays an em dash for both Projects.

Create form incomplete

Create project remains disabled until required data is present.

Empty, error or partial data

Not observed.

Product rules

Non-negotiable boundaries

Project is the canonical domain noun; Project Book may describe an experience but never a second record type.
Project workflows use phases; Pipeline Records use stages.
Project ID must be stable, unique and distinct from the URL slug.
Budget metrics and exports obey financial-field permissions.
Progress and health are calculated from governed inputs and expose supporting reasons.
Creation references an immutable published Project Template version.

Dependencies

Project RecordProject Template versionClient EntityDesigner and Provider EntitiesEnterprise data gridPermissionsCurrency and address field standardsAudit trail

Known current limitations · 6 mapped

What is missing, broken or unverified

Future Spec 07 owns closure →

Only two seeded Projects are represented.
Phase and health values use lowercase display labels.
Health reasons are absent from the directory.
Export output, columns behavior and bulk selection actions were not exercised.
Create Project duplicates a large amount of Project Opportunity information without an explicit conversion context.
The observed Workspace still uses legacy Proper Gallery data.

Future alignment

Required evolution

01Adopt glossary-governed labels and title casing.
02Add saved views, filters, owners, Provider requirements, Client, template and date ranges.
03Expose health reasons and progress methodology.
04Use the same create command for direct creation and idempotent Project Opportunity conversion.
05Add empty, partial, permission-redacted and recoverable error states.

Current baseline

Acceptance record

The live portfolio metrics, columns, records and form sections are inventoried.
No Project was created during review.
Project Phase terminology is separated from Pipeline Stage terminology.
Legacy and presentation-only labels are identified.

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