Compass

Tasks should not live at the front forever.

Most systems accumulate stale commitments until everything competes for attention. Compass is built around receding visibility: old work stays accessible, but it stops demanding attention by default.

Core philosophy

Compass is built by subtraction. Every feature that remains is there because removing it made the system worse. The goal is not infinite flexibility. The goal is a system that makes the right choice clearer.

Page model

• Tasks live on the page where they were created.
• The current page stays at the front.
• Old pages recede naturally instead of crowding the present.
• A new page is created each day, resetting the active workspace.

Auto Death

Compass borrows the useful property of a notebook: older entries stop demanding attention without being deleted. You can always go backward, and you can pull any task forward to the current page when it deserves renewed attention.

ACTIVE

Working now or intending to work on it now.

WAITING

Hidden from the main view until the follow-up date arrives.

PARKED

Still present, but visually deprioritized.

SCHEDULED

Quiet until its scheduled day arrives.

COMPLETE

Archived and accessible, but no longer in working views.

IDEA

Preserved without competing with current commitments.

Today section

Today is a unified attention surface. It brings together due or overdue tasks, items planned for today, waiting tasks whose follow-up date has arrived, and scheduled tasks whose day has arrived.

The point is simple: when something becomes relevant, it should appear without the user having to remember which view to check.

Planning Module

When the next step is unclear, Compass guides the task through the Natural Planning Model: purpose, vision of success, brainstorm, organize, and next action.

That reasoning stays attached to the task, so returning later does not require reconstructing the thought process from scratch.

Compass page

The Compass page separates strategic clarity from operational flow. It holds two things that should not get buried in the task list: a single Why statement and a set of Goals that orient the work beneath them.

Priority Matrix

When several tasks all look important, the Priority Matrix helps make trade-offs explicit. Compass supports a personal model and a business model so the user can score work more objectively instead of relying on vague intuition alone.

A real interface, not a wrapper

A connected agent can create and update tasks, pull the Today view, walk the Planning Module, log a CRM activity, or check its own access — through conversation instead of clicking through screens. It is reading and writing the same data the app shows.

Scoped by design

Access is section-scoped, not all-or-nothing: a connection can be limited to just tasks, or extended to CRM, frameworks, and more. Pairing an agent for the first time grants a narrow, task-only key by default — broader access is something you opt into, not something you start with.

One next-touch date

Each person has a single next-touch date instead of a growing backlog of follow-up tasks. A 1:1 conversation re-arms it automatically; a group touch never falsely marks someone as caught up.

Items to raise

Things worth bringing up next time live in their own undated feed, separate from the follow-up date itself — so remembering what to say doesn't require inventing a fake deadline just to keep it visible.

Projects and subtasks

Tasks can be flagged as projects and organized with subtasks so larger bodies of work remain structured without losing connection to execution.

Contexts and recurring work

Contexts support filtering and grouping, while recurring tasks automatically create the next occurrence without carrying stale operational state forward.

Week Design, Finance & AI Use Cases

Optional modules for templating a recurring week, tracking net worth over time, and logging real-world AI use cases — each toggled on independently, never assumed.