Build blueprint
Local Activity Auto-Timeline
A private desktop timeline deciding whether each app/window event starts, continues, or ends an activity.
- Problem
- People cannot reconstruct what they worked on across apps without manual time tracking.
- Why Jev
- Continuous desktop events demand cheap classification rather than narrative generation.
- Architecture
- Accessibility events → activity Choice and boundary Boolean → local timeline → editable UI.
- Current alternative
- App-name timers and periodic screenshots.
- Jev advantage
- Semantic events can produce a useful timeline without recording every frame.
- Unknowns
- Privacy, app permissions, and ambiguous multitasking.
Why this confidence: Strong indie fit and event-level economics; personalization remains untested.
This is an authored hypothesis derived from the research corpus. Nothing here demonstrates product demand, or that Jev performs well on this particular workload. Run the validation experiment before building past the MVP.
Sources
Limitations
- Privacy, app permissions, and ambiguous multitasking.
- This is a research hypothesis, not evidence of product demand or Jev performance in this workflow.
Supporting research
- Decision sidecar PlausibleA typed judgment service sits beside ordinary code; code owns effects and safety boundaries.
- HA-Jev ObservedA Home Assistant custom integration exposing Jev evaluations as sensors and automation actions.
- Routing, classification, verification, and workflow control are the dominant early mental models. PlausibleThose categories recur in the collected launch discussion and align with the documented output primitives.
- Decision quorum PlausibleMultiple typed judgments are aggregated through voting or confidence-aware stopping.