Overview
Ritual’s context model is built around structured signals.
This gives Ritual enough context to explain where time went without treating your screen as a permanent raw memory surface.
What Ritual Uses
The watcher collects compact activity signals from your Mac.
These signals feed Computer Time, app/website breakdowns, and workstream summaries.
What Ritual Avoids
The current context path is intentionally narrower than the older recorder/search design.
Ritual can still use richer context in targeted places later, but the core product now relies on structured activity and rollups.
Watcher
Ritual Watcher tracks app and website activity locally, then groups computer time into project/task workstreams and daily rollups.What it captures
Workstreams
Workstreams are compact labels for what your computer time was about. They are built from app usage, domains, titles, and safe project/file hints when available. Examples:
The goal is not to preserve every piece of screen text. The goal is to make the day understandable at the level of useful tasks, projects, and time blocks.
Daily Rollups
Ritual turns raw activity segments into compact daily facts.
These rollups are what power Overview, Metrics, Logs, Calendar, and Chat summaries.
Context Sources
Computer activity is only one part of Ritual’s context model.
Together, these sources make it easier to explain the relationship between habits, health, work, phone usage, and environment.
What This Enables
The current model is designed for practical questions.Privacy And Control
The context system is meant to stay understandable and controllable.
This keeps Ritual useful for self-observation without making the default system heavier than it needs to be.
Health Signals
Ritual surfaces diagnostics so context quality is visible.
If a source is missing, Ritual should degrade gracefully instead of overwriting known-good habit totals with empty data.