Life Atlas.
A map for work that has a longer horizon.
Roles, arcs, quests and evidence connect the work of today to larger chapters of a life.
Why it exists
Life Atlas came from a real planning system spanning family, finances, learning, creative work and practice. The task list was useful for capture, but it could not show the story that connected those tasks.
The original question was personal: what is moving, which commitments are heavy, and what would count as evidence of change? The product grew from that model rather than from a generic productivity template.
The idea
Roles name lived identities. Arcs hold sustained directions of effort. Quests contain concrete work. Evidence records what actually changed. Chapters make past, present and emerging horizons legible.
Capacity and leverage matter alongside completion. Suggestions remain proposals until a person accepts them; an AI brief is generated only after the user chooses the source text and asks for it.
Experience
The Today view offers orientation. The Atlas and Chapters views show larger patterns. Proof and reviews keep the account of progress tied to events rather than the number of boxes checked.
What I built
I built the Expo interface, shared domain model and API for roles, arcs, quests, evidence, chapters, onboarding and account isolation. The system evolved from a personal repository into separate private workspaces for testers.
How it evolved
A five year planning system suggested a narrative layer above tasks.
The Observatory model added chapters, capacity signals and evidence backed progress.
The personal atlas became a private, account based product for closed testing.
Current state
Life Atlas is in Android closed testing. I am watching whether the model clarifies real decisions without turning life into another scorekeeping system.