Overview

Intro

Jupiter is a tool for life planning. It is opinionated in how it approaches this problem. The goal of this page is to document Jupiter's conceptual model and how life planning is mapped to it.

There will be references made to the current implementation. But the concepts are separate from it, and could just as easily be implemented via pen & paper.

The Concepts

As a quick reference, here is the list of the more important concepts:

The rest of the document will cover each of these in greater detail.

Note: When referencing Jupiter commands, we’ll use jupiter foo instead of the current Docker based docker run -it --rm --name jupiter-app -v $(pwd):/data jupiter foo. We’ll get there sometime too, but for the sake of brevity it’s easier this way.

As a general consideration, every action in Jupiter is done via a command in the jupiter CLI app. It will affect both the local storage and Notion at the same time. You can edit things in Notion, and for most things it will be easier to go this route though. So you'll need to run special sync commands to keep the local store and Notion in sync.