P5 roadmap: Discovery Inbox next steps

[F-e-u-e-r]

What would you like?

This issue tracks discussion for P5: Discovery Inbox & Candidate Review.

The current direction is to build a deterministic review inbox for GitHub repositories discovered from different sources, before adding more complex integrations such as Telegram commands, NotebookLM, Threads/X watchers, or AI recommendations.

Current P5 direction

P5 focuses on:

• candidate repo intake
• GitHub URL normalization
• public repo resolution
• dedupe against existing stars.json
• source provenance
• dashboard Discovery Inbox
• manual workflow-generated candidate PRs
• no auto-star
• no central key custody
• no AI auto-decision

Why this comes before Telegram / NotebookLM / Threads

Before adding more discovery sources, StarLedger needs a trusted place to put candidate repositories.

The intended flow is:

source finds repo
→ trusted resolver validates it
→ candidate artifact is generated
→ dashboard shows it for review
→ user decides whether to star / dismiss / revisit

Open questions

Feedback welcome on:

• What should a candidate card show?
• Which filters matter most?
• Should candidates have statuses like candidate, dismissed, promoted?
• Should source provenance be visible in the dashboard?
• Should dismissed repos stay in history?
• What would make this useful for your own GitHub stars workflow?

Non-goals for now

Not planned for the first P5 milestone:

• auto-starring
• AI deciding what to star
• Telegram command bot
• NotebookLM integration
• Threads/X watcher
• central backend
• shared service key