Archives
Our public documentation layer.
We call this space Archives because it is where our documentation, philosophy, and product reference keep becoming public as we grow.
Our internal references on philosophy, contexts, recommendations, learning, and scope inform this surface. Archives is the public-facing name for that documentation layer.
Why it matters
Documentation article
Product philosophy
The core principles behind how we think: understanding, decision, guidance, learning, explainability, and accompaniment.
Documentation article
Personality and voice
How we speak: calm, collective, reflective, and always in a way that feels like a council of intelligence.
Documentation article
Contexts model
How we use contexts to reason across work, health, finance, home, learning, and the rest of a real life.
Documentation article
Recommendation system
Why we limit recommendations, how recommendation types differ, and what explainability means in practice.
Documentation article
Learning system
How we learn with the user through signals, momentum, stability, and transparent adaptation.
Documentation article
Product scope
What belongs in our MVP, what we are intentionally deferring, and why restraint is part of our strategy.
Documentation article
What is calm productivity software?
A practical explanation of calm productivity software and why a quieter product can create better daily decisions than a crowded dashboard.
Documentation article
Context-based prioritization for real life
How context-based prioritization helps software reason across work, health, finance, and home instead of treating every item as identical.
Documentation article
A daily priority system that explains itself
Why a daily priority system should not only rank what matters, but also explain the reasoning behind the top decision.
Documentation article
Explainable recommendations in productivity software
Why explainable recommendations matter in productivity software and how they change trust, action, and product maturity.
Documentation article
How private beta access should work for a thoughtful system
A product note on why private beta access, waitlists, and invite-based signup can create a stronger early system than opening everything at once.