Concepts
Watch briefs
How Watch turns repo activity into return value.
Watch is the retention surface.
Watch should explain why to come back
A useful Watch brief turns repository activity into a short decision: open it, ask about it, keep watching, or ignore it.
What changed?
Releases, commits, issues, and project movement.
Why for me?
The change is interpreted against OpenStar Memory.
What next?
Open, ask a follow-up, save context, or keep monitoring.
Brief generation
Collect recent repository activity from watched repos.
Read enough repository context to avoid raw notification summaries.
Compare the update with the user's Memory and watch reason.
Produce a concise brief with actions and clear uncertainty.
What a brief should contain
| Section | Goal |
|---|---|
| Change | State the concrete repo movement. |
| Impact | Explain whether the change matters to the user's stack or interests. |
| Risk | Mention breaking changes, stale activity, license concern, or unclear evidence. |
| Action | Suggest open, ask, save, unwatch, or ignore. |
Product distinction
- Do not mirror GitHub notifications. Raw notifications are high volume and low context. OpenStar should compress them into value, relevance, and next action.
- Save is a lightweight bookmark. Watch means the repo deserves future monitoring and brief generation.