Home And Notification
Desktop's Home surface is the social feed and shortcuts entry; the Notification surface is the unread-count and recent notifications view. Together they form Desktop's "what's new" surface.
Home
| Feature | Behavior |
|---|---|
| Social feed | Posts and updates from your social graph |
| Shortcuts | Frequent destinations (worlds, agents, conversations) |
| Recommended content | Surface curated content |
| Cross-domain post cards | Surface post cards from other domains (chat, gift, profile, etc.) |
Home is a destination, not an authority. It reads from Realm social, Realm posts, Realm world / agent surfaces, and projects.
Cross-Domain Entry Points
Home post cards may surface entry points to other domains — "Open chat with X", "Send a gift to Y", "View Z's profile". A key design choice: Home does not directly own those mutations.
Cross-domain actions are injected via explicit owner callbacks. Home presents the entry point; the owner domain (chat, economy, profile) handles the actual flow.
This is what keeps Home from becoming an accidental shadow authority for every surface in Desktop.
Notification
| Feature | Behavior |
|---|---|
| Notification list | Recent notifications |
| Unread count badge | Visible in nav |
| Mark as read | Per-notification or all |
| Polling | Polling-based for unread count |
The unread count is polling-based — small operational detail, but it matters for what apps can rely on. Realtime push for unread is not admitted; the polling model is.
Reader Scenario: Acting On A Home Card
You see a home card — "X sent you a gift."
- Card surfaces. Home reads the relevant social / economy event; renders a card.
- You click "open." Home does not directly mutate state; instead, it calls into the owner domain (economy) through an admitted callback.
- Economy handles. The Wallet flow opens with the gift in focus.
- Audit lineage. The user click is recorded; the navigation is audited.
Home is the discovery surface. Wallet is the action surface. The two cooperate but neither owns the other's truth.
Reader Scenario: Checking Notifications
You open Notifications.
- List loads. Recent notifications display.
- Unread count. Badge shows N unread.
- Mark as read. You read items; mark as read; the badge decrements.
- Polling. The unread count polls under admitted polling policy.
Notifications are bounded; new notification kinds require admitted notification contracts.