Features / The product system

Built around
the work.

A VuCalendar task keeps its identity as you place it in time, give it purpose, carry its method, and return to what happened. The features form one environment around that work.

Start with one task
01 / One task

One task. More than one moment.

Dates can move. Detail can grow. The scale can change. VuCalendar keeps the task as one authored thing instead of rebuilding it at every calendar moment.

The identity holds. VuModal brings its placement, purpose, method, and context together. Those details can flex without turning the work into a disconnected copy.

Identity across momentsTask 042 / same identity
Tuesday, July 28Early Day · Top of Day · 60 minutes.
Tuesday, August 4The next date returns the same authored task.
Cycle 02The prior run remains preserved as the task continues.
HistoryVuEach period can be read without replacing the task.
Planning / Completion
Prepare weekly review
Early Day60 minutes4-step Regiment
02 / Placement and scale

Time is the foundation. The work is what comes forward.

Place work by part of day, then read the same structure at day, week, and month scale. The horizon changes. The interaction model does not.

DayVu executes.
WkVu plans.
MnthVu reveals patterns.

The same task at three scales
TuesdayJuly 28
Execution
Tue28
DayVuToday by part of day
72°
AllDayGroceriesCar shop
Early Day5:00-11:59
Top of Day
Client proposal60m · Completion
Before Mid Day
Weekly review45m · Guide
Mid Day12:00-5:59
After Mid Day
Mobility30m · Practice
Before EveningOpen space
Late Day6:00-12:00+
After Evening
Invoice batch40m · Completion
NightNo task placed
DayVu returns the structure authored for this day.Portrait in the application
03 / Tracking Mode

Choose what kind of work it is.

Some work finishes. Some builds through practice. Some calls for ongoing follow-through. Choose the kind once and VuCalendar carries that meaning forward.

Mode describes what the work is for, not how often it repeats. It remains optional.

Kind of workActionLifecycleHistory lens
CompletionSubmit permit application
Complete
Finishable30-day grace after the final date
OutcomeWhat reached its end
PracticePractice conversational French
Log
Open-endedIdle notice begins at 60 days
PresenceWhere practice held
GuideWeekly client follow-through
Follow through
Open-endedIdle notice begins at 60 days
StewardshipHow follow-through held
No mode remains a complete, intentional choice.Action: Done · Completion lifecycle
The method stays inside the task
Planning / Completion
Prepare weekly review
Early Day60 minutesRegiment attached
Review procedure4 ordered steps
  1. Review the latest notesPrepare
  2. Identify decisions still openPrepare
  3. Arrange the discussion orderShape
  4. Record the next actionsFollow through
04 / Method

Not just what. How.

Regiment is an ordered operating guide attached to a task. The procedure returns with the work, so the user does not have to rebuild the method from memory.

A Regiment is not a second task hierarchy. It describes how this task is carried out while the task remains the organizing unit.

05 / Continuity

The date passes. The task keeps its context.

Per-date activity forms a record around the task. Lifecycle rules respond to its intent, HistoryVu reads what happened, and Cycle can continue the same identity into a new period by choice.

Active period
Prepare weekly reviewTask 042 · Completion
July 21Complete
July 28Complete
August 4Complete
Reflective record

Early Day held this work consistently across the period.

  • 3 completed dates
  • 180 planned minutes
  • Completion intent preserved
Continue by choice
Prepare weekly reviewTask 042 · Cycle 02
The closed period becomes an immutable snapshot. New dates begin without cloning or replacing the task.
Completion can archive after its grace period.Practice and Guide follow an idle-time lifecycle.Cycle is manual. VuCalendar never cycles work automatically.
Around the core

Systems that support the work.

These capabilities matter because of the role they play around the task. They extend capacity, context, organization, or atmosphere while the task remains the organizing unit.

01 / Capacity

Overtime Awareness

Reads the fit between authored work and available lane time. Exact minute feedback informs without blocking the user.

02 / Organization

TaskHub and Groups

Give tasks belonging and scale outside the calendar. Unscheduled work can develop before it receives dates.

03 / Context

Import Tray and Artifacts

Keep references with the work that uses them. Links, documents, images, and videos move from staging into the task.

04 / Atmosphere

Weather Adaptive Backgrounds

Change the environment, not the task logic. Live-rendered conditions make the application feel connected to where it is being used.

05 / Ownership

Local by design

The system stays on your device. Task data lives locally in SQLite; VuCalendar has no access to its contents.

The full view

One system, built around work that can continue.

The features work as one system. Experience shows how that structure feels in use.