BC
Brad CodyAdministrator
Current product→Work, communications and reporting
Reverse spec drafted

Tasks directory

Workspace task grid with metrics, selection, bulk state changes, filters, sorting, ownership and record links.

Observed route/admin/tasksFuture Spec 12 →
Current maturityFunctional seeded Workspace task grid with limited work model
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

The live Tasks directory contains two seeded Tasks and provides search, four metrics, row selection, bulk State change, State/Priority/Owner filters, a Closed toggle, sixteen sort options, export, columns and row editing. Both Tasks link to Project Opportunities and are owned by Demo Administrator in the grid. The page is useful for basic list management but has no Task detail route, saved views, calendar context, dependency visibility, completion evidence or durable per-Task activity surface.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
MetricsOpen 1, In progress 1, Blocked 0 and Overdue 1.Verified live
FiltersState, Priority, Owner and ambiguous Closed checkbox; no Project, Phase, Type, Team, due range or assigned-to-me filters.Verified live
Bulk actionsSelecting rows exposes Change State to Open, In progress, Blocked or Closed.Verified without changing state
GridTask, Type, State, Priority, Owner, Collaborators, Linked to, Due and Actions; two seeded Project Opportunity Tasks.Verified live
Task navigationTask titles are not links; Edit is the only row action.Verified live
Export and columnsActions are present; output and persistence were not exercised.Visible, not mutated

User journeys

Current flows

01

Review Workspace work

  1. Open Tasks
  2. Review attention metrics
  3. Search/filter/sort
  4. Inspect Owner, context and due timing
  5. Open Task detail
  6. Update or complete work
Observed result

Discovery works; canonical Task detail does not exist.

02

Bulk change State

  1. Select permitted Tasks
  2. Choose State
  3. Review affected records
  4. Confirm
  5. Write Task Activity
Observed result

Selector is visible; mutation and audit were not tested.

State model

Current and expected states

Open

One seeded Task.

In progress

One seeded Task.

Blocked

Metric/filter exist at zero.

Closed

Hidden by default behind a checkbox.

Overdue

Derived metric shows one; no reason or escalation is visible.

Selected

Bulk State control appears.

Product rules

Non-negotiable boundaries

  • Every actionable Task has one accountable Task Owner.
  • Metrics and overdue status derive from canonical Task dates and State.
  • Task visibility follows its linked record plus explicit Task visibility.
  • Bulk changes validate each Task independently and produce audit events.
  • Closed Tasks remain durable and searchable.
Dependencies
Spec 12 Tasks and CalendarTeammates and TeamsTask BuilderProject and Pipeline RecordsEnterprise data gridPermissions, Activity and Notifications

Known current limitations · 5 mapped

What is missing, broken or unverified

Future Spec 12 owns closure →
  1. No Task detail route or history.
  2. Only seeded Tasks are visible.
  3. No saved views, Team filter, Project/Phase filter, dependency, checklist, recurrence, evidence, time or calendar columns.
  4. The Closed checkbox label is ambiguous.
  5. Owner identity conflicts with the editor default.

Future alignment

Required evolution

  • 01Add My Work, Workspace Work, Waiting On, Exceptions and saved views.
  • 02Open a canonical Task Profile rather than only an editor modal.
  • 03Connect Tasks to Calendar, resources, dependencies, evidence and Time Entries.
  • 04Add permission-safe role-specific views for Designers, Providers and Registry operators.

Current baseline

Acceptance record

  • Two seeded Tasks and all visible controls are documented.
  • Bulk State mutation is not claimed as verified.
  • Missing Task detail and execution depth are explicit.
  • Metrics resolve to the same canonical Task set as the grid.

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