Saa: Make time visible

Saa exists to make time visible. It is deliberately narrower than a platform and more useful than a dashboard full of possibilities.

Begin with the useful act

Open Saa and place an event once and understand the time around it without rebuilding your calendar. The first screen should explain itself through the records already there, sensible defaults, and one obvious create action. You should not need a setup ceremony before discovering whether the tool helps.

Speed is part of the product. Warm pages are server-rendered, ordinary changes stay local first, and small HTMX responses update only the part that changed. Shared identity comes from Muhaka, so moving from Yote into Saa should preserve the session instead of presenting another login wall.

What Saa owns

Saa owns events and time records. It can reference a file from Hifadhi, a page from Sura, or a record from another app, but the source remains labelled and opens at its owner. This keeps edits, archives, restores, and audits understandable.

That boundary also protects performance. Saa does not carry a copy of every account, file, notification, and workflow in the constellation. It loads the small contract it needs and gets out of the way.

A calm daily rhythm

Use the product in the smallest rhythm that produces relief:

1. Capture the thing while it is present.
2. Add context only when the context changes a decision.
3. Finish, archive, or return through one direct action.
4. Let Yote surface a useful notification only when another app genuinely needs attention.

What good feels like

A good session in Saa ends quickly. The record is trustworthy, the source is clear, and the next action is obvious. Mobile keeps the same mental model with fewer columns: choose the thing, then act on it. Desktop uses space for readability, not more control panels.

The product will continue to improve, but this promise should remain stable: make time visible, without asking you to manage the machinery behind it.