Reverse spec drafted

Create and edit Task

Task form for title, description, Type, State, Priority, due date, Owner, Collaborators and linked record.

Observed route/admin/tasksFuture Spec 12 →

Current maturityWorking create form with a critical Edit defect

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

New Task opens a modal with Title, Description, Type, State, Priority, Due date, Owner, Link type and Collaborators. Type options are alphabetized and include Approval, Call, Designer matching, Document review, Email, Follow-up, General, Meeting, Proposal and Site visit. Link type supports only Designer, Project and Project Opportunity. Critically, selecting Edit on an existing row opens the same Create task modal with blank/default fields and the heading Create task instead of loading the selected Task.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Identity and outcome	Title and Description; no visible Task ID, expected outcome, completion requirement or detail route.	Verified live
Classification	Alphabetized Type list, State Open by default and Priority Medium by default.	Verified live
Assignment	One Owner plus Sarah Chen, Victoria Admin and Olivia James as Collaborators.	Verified live
Timing	One date-only Due date; no start, time, estimate, duration, recurrence or reminder.	Verified live
Task Link	Designer, Project or Project Opportunity; selected type reveals a record picker.	Verified live
Edit behavior	Existing Task Edit opens blank/default Create task state and does not identify or populate the selected Task.	Critical defect verified without saving

User journeys

Current flows

Create Task

Open New Task
Describe work
Choose Type, State and Priority
Assign Owner and Collaborators
Set due timing
Link canonical context
Save

Edit Task

Select row Edit
Load exact Task ID and current version
Change permitted fields
Review downstream impact
Save and write Activity

State model

Current and expected states

Create idle

Defaults General, Open, Medium and Brad Mitchell.

Linked record selection

Record picker appears after Link type selection.

Validation and saving

Not exercised.

Editing

Incorrectly indistinguishable from blank creation.

Conflict or stale version

Not represented.

Product rules

Non-negotiable boundaries

Create and Edit are explicit modes with distinct headings and commands.
Edit loads the selected immutable Task ID and current version before changes.
A Task has one Owner and zero or more Collaborators.
Task Link uses typed canonical relationships and supports all operational contexts defined by Spec 12.
State changes, reassignment and due-date changes write Activity and trigger configured notifications.

Dependencies

Task serviceTask Builder Types and StatesMembership-backed assigneesDynamic forms and date controlsCanonical record pickerActivity, Notifications and optimistic concurrency

Known current limitations · 4 mapped

What is missing, broken or unverified

Future Spec 12 owns closure →

Edit is unsafe and cannot be considered functional.
Link types omit Client, Provider, Application, Project Phase, Provider Job, Work Order, Item and other work contexts.
No checklist, dependency, recurrence, evidence, follower, Team, visibility, estimate or Time Entry controls.
No Task ID or Activity is visible.

Future alignment

Required evolution

01Fix Edit before enabling updates.
02Implement the complete Task editor and Task Profile from Spec 12.
03Expand typed links and permission-aware record search.
04Add dependencies, checklists, recurrence, completion evidence, reminders, Calendar and Time Entries.

Current baseline

Acceptance record

Create fields and option lists are recorded.
The Edit defect is a release blocker and not softened as incomplete evidence.
No Task was created or modified during review.
Owner identity resolves consistently between grid, form and saved record.

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