BC
Brad CodyAdministrator
Current productProjects and project operations
Reverse spec drafted

Project profile

Operational Project Record connecting phases, participants, tasks, files, decisions, items, budgets and commercial work.

Observed route/admin/projects/:slugFuture Spec 07
Current maturityPolished Project shell with major operational modules still absent
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

The live Project profile provides a strong shell around a canonical-looking Project ID, title, Client/location summary, health, Overview, Process, Participants, Files, Communication and Activity tabs. Overview includes the seven phases, Project Pulse, planning budget, blockers, approvals, Spaces & Rooms, Vision & Inspiration and decisions. Many controls describe future capability without a destination or working module; Calendar, Items & Budgets, Tasks, Approvals, Spaces, commercial records, Provider work and presentations are not first-class profile tabs.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Identity headerRR avatar, PR-00001, Rosedale Residence, Emma Hughes, Toronto Ontario and on track health.Verified live
Primary tabsOverview, Process, Participants, Files, Communication and Activity.Verified live
Phase railSeven numbered phases with Concept 100%, Design 28% and all later phases 0%.Verified live
Project PulseCurrent Phase, Overall Progress, Health and Completion Target plus Complete phase and advance.Verified live
Financial summaryPlanning budget $540,000 and placeholder copy for future Budgeting.Verified live
Attention modulesNo urgent blockers and no approvals; View tasks and View approvals controls are present.Verified live; destinations not evidenced
Spaces & RoomsExplains floor/space/room organization and exposes Manage spaces.Verified live; management destination not evidenced
Recent decisionsEmpty state only.Verified live
Edit ProjectEdits name, Client/household text, location text, planning budget and completion target.Verified without saving

User journeys

Current flows

01

Review Project status

  1. Open Project
  2. Review identity and health
  3. Review phases and pulse
  4. Review financial summary
  5. Check blockers, approvals and recent decisions
Observed result

Working as a summary experience, with several placeholder modules.

02

Edit core details

  1. Select Edit Project
  2. Change permitted core fields
  3. Save
  4. Write attributed history
Observed result

Form and audit promise verified; save intentionally not executed.

03

Operate Project

  1. Open Tasks, Calendar, Items, Budgets, Provider work or Presentation
  2. Perform contextual work
  3. Return to Project
Observed result

Not currently possible from dedicated Project modules.

State model

Current and expected states

On Track

Rosedale shows on track without visible calculation detail.

Phase active

Design is current at 28%; Concept is complete.

No target

Completion Target shows Not set.

No blockers, approvals or decisions

Dedicated empty summaries appear.

No participants, files, communications or activity

Each dedicated tab shows an empty or readiness state.

Permission-redacted financials

Copy says shown only to permitted viewers; redacted rendering was not tested.

Product rules

Non-negotiable boundaries

  • All tabs project one canonical Project Record.
  • Client, Designer, Provider and Admin profiles use shared modules with field- and record-level visibility.
  • A Project Phase may be primary while tasks in other phases remain active.
  • Advancing a phase validates template completion rules and records an attributed transition.
  • Client identity must reference a Client Entity rather than remain editable free text.
  • Financial values are derived from Budget Categories, Items and commercial records once those modules exist.
Dependencies
Project RecordProject Template snapshotClient EntityProject Participants and access grantsTasksApprovals and DecisionsFiles and revisionsCommunicationsItems and BudgetsCalendarActivity and audit

Known current limitations · 6 mapped

What is missing, broken or unverified

Future Spec 07 owns closure →
  1. The profile lacks first-class Tasks, Calendar, Items & Budgets, Provider Operations, Proposals/Work Orders/Invoices and Presentation tabs.
  2. View tasks, View approvals and Manage spaces read like destinations but no working destination was verified.
  3. Client/household and location are editable plain text in the core edit form.
  4. Progress, health and phase-advance calculation are not explained.
  5. Project Communication is only readiness copy, not a working inbox.
  6. The phrase Premium project book is decorative and not glossary-governed.

Future alignment

Required evolution

  • 01Build the Project workspace defined in Spec 07 around permission-aware modules.
  • 02Link Client and participant Entities instead of copying names.
  • 03Add phase validation, transition blockers, explanation and rollback governance.
  • 04Connect Tasks, Calendar, Items, Budgets, commercial work and Provider Work Packages.
  • 05Use Project Presentation for the client-facing authored output; do not overload Project Book as a data type.

Current baseline

Acceptance record

  • All live tabs and Overview modules are documented.
  • Placeholder controls are not represented as working modules.
  • Core edit fields and audit promise are recorded.
  • Canonical terms are defined in the company glossary.

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