Reverse spec drafted

Project Builder

Reusable Project templates, phases, tasks, milestones, forms and Provider Requirements.

Observed route/admin/settings/projectsFuture Spec 07 →

Current maturityVisible Project Template builder requiring operational expansion

Evidence confidencePartially verified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

Project Builder exists as the reusable template surface behind the seven canonical Project Phases. Earlier live review confirmed Project Templates and task-oriented setup, but the future contract must add milestones, dependencies, forms, Items and Budget Categories, Provider Requirements, deliverables, calendars, resources and versioned publication without forking the Project service.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Template directory	Project Template entry point exists in Settings.	Verified in prior Projects pass
Seven Phases	Concept, Design, Design Package, Construction Administration, Decorating, Procurement and Installation govern Project setup.	Canonical future contract
Operational configuration	Current depth does not evidence complete milestones, dependencies, Items, budgets, Provider Requirements or resources.	Known gap
Versioning	Published-version and Project-instance lineage are not verified.	Requires verification

User journeys

Current flows

Publish Project Template

Create draft
Configure seven Phases
Add tasks, milestones, forms, deliverables and dependencies
Add Item/Budget schemas and Provider Requirements
Validate
Publish immutable version
Instantiate Project with lineage

State model

Current and expected states

Draft

Expected; not fully reviewed.

Published

Version contract required.

Archived

Required for future selection without breaking Projects.

Product rules

Non-negotiable boundaries

Project Phase is not Pipeline Stage.
Templates seed records but do not remain hidden mutable truth.
Existing Projects retain their originating template version.
Provider Requirements and Item/Budget configuration use shared canonical services.

Dependencies

Spec 07 ProjectsSpec 12 Tasks/Calendar/ResourcesProvider RequirementsDynamic formsItems and budgetsVersioning

Known current limitations · 2 mapped

What is missing, broken or unverified

Future Spec 07 owns closure →

Complete live builder anatomy was not re-exercised in this Settings pass.
Advanced operational primitives are not evidenced.

Future alignment

Required evolution

01Apply Spec 07 correction contract.
02Add validation, preview and impact analysis.
03Preserve the seven-Phase process while allowing optional work within Phases.

Current baseline

Acceptance record

All seven canonical Phases remain explicit.
Published versions are immutable.
Projects do not silently change when a template is edited.
Provider and commercial handoffs are configurable.

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