#7 · Corpus · 2026-05-10
Upstream repository pointer and settings
Status: Backlog
CorpusImplementation
- Persist the designated upstream GitHub coordinates on the account (spec—one repo, JSON graph ingest; URL/path conventions TBD).
- Minimal UI or settings path to view or update the pointer once authenticated; align with “saved pointers” in the product spec.
- No hosting of third-party catalog on our backend—configuration only.
Questions
- Default repo slug—hard-coded for v1 vs user-editable field?
- Private repo access—GitHub token flow vs public-only for first release?