Velprium
·

CORE CONCEPTS

The Coordinate Model

Velprium organizes time, data, and perspective as a coordinate system.

Traditional calendars organize time. Velprium organizes time, data, and perspective.

A calendar already has coordinates

A normal calendar already has a simple coordinate system. The x-axis tells you when an event happens, while the event itself carries a small amount of information.

Time is managed precisely, but the data that gives that time meaning is often thin.

A simple calendar timeline showing events with only a title and description.A simple calendar timeline showing events with only a title and description.x · Time9 AM12 PM3 PMy · Event dataProduct development2:00–4:00 PMDescriptionLanding page implementation

A calendar places events on a timeline, but each event carries little data.

Enriching the y-axis

Velprium extends the event’s data with Event Properties. The event stops being a plain calendar entry and becomes a structured record that can be searched, compared, and reused.

Project · Outcome · Mood · Energy

The same calendar event expanded with structured properties such as project, outcome, mood, and energy.The same calendar event expanded with structured properties such as project, outcome, mood, and energy.x · Time9 AM12 PM3 PMy · Event PropertiesProduct development2:00–4:00 PMDescriptionLanding page implementationProjectVelpriumOutcomeDocs page completeMoodFocusedEnergyHigh

Event Properties turn a calendar entry into a structured record.

Discovering the z-axis

The same time and the same event data can mean different things depending on the perspective through which you view them.

Example

A “2–4 PM, product development” event can be:

  • Work Log — Deep work spent building the product
  • Daily Journal — A period of high focus and energy
  • Weekly Review — An activity that advanced the weekly goal
  • Velprium Project — Two hours invested in Velprium
Multiple Page layers showing the same event at the same time from Daily Journal, Work Log, and Weekly Review perspectives.Multiple Page layers showing the same event at the same time from Daily Journal, Work Log, and Weekly Review perspectives.z · Perspective (Page)x · TimeWork LogDaily JournalWeekly Review9 AM12 PM3 PMsame event, three lensesType · Deep workProduct developmentMood · FocusedProduct developmentGoal · +2hProduct development

Pages let the same time be understood through different perspectives.

Inside a Page: parallel timelines

A Page defines the perspective, but a perspective can contain more than one timeline.

Areas divide a Page into independent, parallel x-axes. They share the same dates and hours, but each Area can represent a different part of the perspective.

Page: Daily Journal

Areas: Plan · Act · Review

Plan, Act, and Review are one example. Other Pages can use entirely different Area structures.

A Daily Journal Page divided into Plan, Act, and Review Areas, each acting as an independent parallel timeline.A Daily Journal Page divided into Plan, Act, and Review Areas, each acting as an independent parallel timeline.Daily JournalParallel time axesPlanProduct planningProduct developmentActOAuth issueProduct developmentReviewPlan changedHigh focus

Areas create independent, parallel timelines inside a Page.

Mapping the model to Velprium

The coordinate model maps directly to Velprium’s interface.

CoordinateVelpriumMeaning
x-axisTimeWhen an event happens
y-axisEvent PropertiesStructured data attached to an event
z-axisPageA perspective through which time is viewed
Parallel x-axesAreasIndependent timelines inside one Page

Core definitions

  • Page = Perspective
  • Area = A parallel timeline inside a Page
  • Event Property = Structured data attached to time

Why this model matters

One event, more meaning

An event becomes a structured record instead of just a title and a time.

The same time, multiple perspectives

The same time data can be read from work, diary, project, and review perspectives.

Multiple timelines, one view

Within one Page you can see different time flows side by side — plan vs. actual, work vs. health.

The coordinate model explains the structure. A setup like Plan · Act · Review is just one way to use it. See it in Templates →

Related concepts