Parent: #39
Context
Public pull-request reviews are Juror's strongest potential distribution surface, but OSS maintainers may not have budget or credentials for multiple model providers. Similar review products gained adoption by making their best experience available to public repositories.
Acceptance criteria
- Define selection criteria for ten consenting public repositories with meaningful PR volume and maintainer review load.
- Contact maintainers individually; do not open unsolicited installation PRs or enable reviews without permission.
- Provide concierge installation and a documented rollback/removal path.
- Secure or allocate a limited provider-credit budget so each participant can experience at least two model families.
- Establish a 30-day shadow-review period before any merge-blocking use.
- Collect weekly activation, failure, acted-on finding, dismissed finding, cost, and maintainer-feedback data.
- Obtain explicit permission before publishing a repository name, quote, review, or case study.
- Produce a retrospective covering adoption, retention, quality, and onboarding friction.
Parent: #39
Context
Public pull-request reviews are Juror's strongest potential distribution surface, but OSS maintainers may not have budget or credentials for multiple model providers. Similar review products gained adoption by making their best experience available to public repositories.
Acceptance criteria