Reverse spec drafted

Project Calendar

Project events, milestones, appointments, delivery and installation timing.

Observed route/admin/projects/:slugFuture Spec 12 →

Current maturityRequired Project module not present in the current profile

Evidence confidenceKnown limitation

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

No Calendar tab, embedded agenda, schedule view or Project timeline was found in the reviewed Project profile. Project Builder provides default Phase durations and task due-date anchors, including Project Start, Phase Start, Phase Target and Installation Date, but the Project exposes no working calendar where those dates can be reviewed or coordinated.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Project Calendar entry	Absent from Project tabs and Overview.	Verified absent
Schedule inputs	Project Builder has durations, due anchors and offsets; Create/Edit Project has Completion Target.	Verified live
Calendar views	No agenda, month, week, timeline or resource view was found.	Verified absent
External calendar sync	Not represented in the current Project surface.	Absent

User journeys

Current flows

Coordinate Project schedule

Open Project Calendar
Review Phase targets and milestones
Schedule Client and Provider work
Resolve conflicts and dependencies
Publish permitted events
Synchronize eligible events to connected calendars

State model

Current and expected states

Module unavailable

No Project Calendar navigation is present.

Completion Target absent

Rosedale displays Not set.

Template anchors configured

Basic due anchors and offsets exist in Project Builder.

Product rules

Non-negotiable boundaries

Project Calendar is a projection of canonical events, tasks and milestones—not a separate copy.
Project Phase, Work Order, receiving, delivery and installation dates remain distinguishable.
Provider and Client visibility is explicit per event.
Google Calendar synchronization never becomes the source of truth for Project scope or completion.

Dependencies

Spec 12 Tasks, Calendar & Resource SchedulingProject and Phase datesTasks and MilestonesProvider Work OrdersResource schedulesGoogle Calendar integrationNotifications

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 12 owns closure →

No current Calendar UI exists in the Project.
No conflict, availability, recurrence, timezone, resource or external-sync behavior is visible.
Installation Date is offered as a template anchor without an observed canonical Project field.

Future alignment

Required evolution

01Add Project Calendar and agenda surfaces from Spec 12.
02Make Phase targets, milestones and Provider appointments visible in context.
03Support resource and installation-day coordination.
04Add permission-scoped external synchronization with clear source and sync health.

Current baseline

Acceptance record

The missing current module is explicit.
Existing date anchors are documented without implying a Calendar implementation.
Future behavior is owned by Spec 12.

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