Section 2: Presence + Distribution
Why this section matters competitively
Seraph cannot become a real daily guardian if it only exists in a browser tab on localhost. This section translates the product from an impressive local app into something that is reachable, ambient, and present across the day.
Current state in Seraph
- strong browser-based product experience
- local Docker-centered setup
- no real channel reach yet
- no desktop shell or system tray
- limited notification presence outside the active web UI
Target end state
Seraph is available as a native-feeling local companion with at least one external channel and reliable delivery surfaces that make proactive behavior useful in ordinary life.
Key capabilities
- native desktop packaging
- tray presence and notifications
- startup/background availability
- external messaging channel integration
- cross-surface session continuity
- better delivery routing for briefings, alerts, and nudges
Dependencies and risks
- depends on Season 1 establishing runtime credibility first
- can create support and platform burden quickly
- risks diluting the main UX if distribution precedes product discipline