roadmap: Gittensory ecosystem adoption v1

[JSONbored]

Product thesis

Gittensory should become the Gittensor contribution operating layer: the place where miners plan and validate useful work, maintainers control and trust GitHub output, repo owners assess intake readiness, and operators measure ecosystem adoption/value.

This is the adoption roadmap for the surfaces around the deterministic base-agent foundation. Keep #82 as the beta-grade base-agent v2 foundation roadmap; use this issue as the ecosystem adoption v1 parent. Do not create another top-level roadmap unless this issue is explicitly closed as superseded.

Non-goals

Gittensory should not become:

• A generic Gittensor dashboard or explorer.
• A public reward leaderboard.
• A wallet/hotkey dashboard.
• An autonomous PR bot.
• A public score predictor.

V1 success criteria

• Miners can install, plan, preflight, and generate a useful PR packet.
• Maintainers can trust, preview, and control GitHub output before it reaches public surfaces.
• Repo owners can assess intake readiness before inviting more contributor traffic.
• Operators can measure adoption/value without exposing private scoreability or implying payout outcomes.
• The browser extension is usable in the GitHub PR review flow and has screenshot-backed review states.

Tracking model

Use this issue as the narrative source of truth. Use native sub-issues for the execution tree where GitHub supports it. Keep nesting shallow: parent roadmap -> phase epic -> implementation issues.

Use one GitHub Project named Gittensory Ecosystem Adoption v1 as the operating board for status, phase, audience, surface, priority, gate, target, source, and PR linkage. Project creation/configuration requires a GitHub token with project scope.

Project board fields

• Status: Backlog, Ready, In Progress, Blocked, Review, Done, Closed/Superseded.
• Phase: 0 Stabilize, 1 Miner, 2 Maintainer, 3 Repo Owner, 4 Analytics, 5 Distribution, 6 Advanced.
• Audience: Miner, Maintainer, Repo Owner, Operator, Contributor, All.
• Surface: MCP, Web App, GitHub App, Extension, API, Data, Docs, Raycast/PWA.
• Priority: P0, P1, P2, P3.
• Confidence: High, Medium, Low.
• Gate: Needs PR, Needs screenshots, Needs CI, Needs design, Needs auth/privacy review, Ready.
• Target: Now, Next, Later, Research.
• Source: Existing issue, New issue, Existing PR, Replacement PR.

Project board views

• Roadmap: grouped by Phase, sorted by Priority.
• Current Push: filtered to Phase 0/1/2, Status not Done.
• Maintainer Trust: Audience = Maintainer or Surface = Extension/GitHub App.
• Miner Utility: Audience = Miner or Surface = MCP.
• Blocked: Status = Blocked or Gate contains CI/screenshots/auth.
• PR Queue: items linked to open PRs.
• Advanced: Phase = 6 Advanced.

Phase epics

• roadmap(phase 0): stabilize while shipping #233 - Phase 0: Stabilize While Shipping
• roadmap(phase 1): miner command center #234 - Phase 1: Miner Command Center
• roadmap(phase 2): maintainer trust and browser extension #235 - Phase 2: Maintainer Trust + Browser Extension
• roadmap(phase 3): repo owner intake console #236 - Phase 3: Repo Owner Intake Console
• roadmap(phase 4): adoption analytics and launch system #237 - Phase 4: Adoption Analytics + Launch System
• roadmap(phase 5): ecosystem distribution #238 - Phase 5: Ecosystem Distribution
• roadmap(phase 6): advanced contribution operating layer #269 - Phase 6: Advanced Contribution Operating Layer

Phase 0: Stabilize While Shipping

Live PR cleanup and deterministic blockers:

• PR feat: add a private GitHub PR sidebar context panel for extension maintainers #224, PR fix(auth): trim bearer tokens in rate-limit keys #65, PR fix(docs): clarify MCP metadata upload boundary #231, PR feat: add agent action explanation cards #232, PR feat(agent): add recommendation outcome feedback #229, PR feat(agent): add risk-adjusted action portfolio #219
• [Bug]: ensurePullRequestLabel misses labels beyond first page #160 / PR [Bug]: ensurePullRequestLabel misses labels beyond first page #161 label pagination/accounting
• [Bug]: openIssuesTotal under-counts when open PRs are subtracted from GraphQL issues #159 / PR [Bug]: openIssuesTotal under-counts when open PRs are subtracted from GraphQL issues #162 open issue under-count
• [Bug]: Monolithic backfill stores PR-inclusive count as openIssuesCount #176 / PR [Bug]: Monolithic backfill stores PR-inclusive count as openIssuesCount #177 PR-inclusive open issue count
• [Bug]: Maintainer-authored issues can be scored ready for outside contributors #186 / PR [Bug]: Maintainer-authored issues can be scored ready for outside contributors #187 maintainer-authored issue scoring
• [Bug]: installation_repositories webhooks are never handled — repos added to an existing installation are silently dropped (and the installation "added" branch is dead code) #257 installation_repositories webhook handling
• PR feat(bounties): classify lifecycle advisory states #157 stale bounty lifecycle branch
• chore(roadmap): triage stale v1 PR queue into land/replace/close buckets #239 triage stale v1 PR queue

Phase 1: Miner Command Center

• feat(control-panel): add miner command center #129 miner command center
• feat(mcp): add public-safe PR body drafting command #98 public-safe PR body drafting
• feat(mcp): add multi-account profile support #99 multi-account profile support
• feat(mcp): cache last-good decision packs for offline fallback #100 last-good decision packs for offline fallback
• feat(mcp): make doctor output a miner onboarding checklist #240 doctor as miner onboarding checklist
• feat(app): show MCP command copy actions from miner dashboard #241 MCP command copy actions from dashboard
• feat(agent): expose recommendation changes and rerun reasons in miner dashboard #242 recommendation changes and rerun reasons
• feat(mcp): add roots-aware workspace detection #274 roots-aware workspace detection
• feat(mcp): add non-sensitive elicitation for planning choices #275 non-sensitive MCP elicitation for planning choices

Phase 2: Maintainer Trust + Browser Extension

• feat(control-panel): add maintainer control panel #130 maintainer control panel
• feat(extension): scaffold GitHub overlay browser extension #145 extension scaffold
• feat(extension): add PR sidebar Gittensory context panel #146 PR sidebar context panel
• feat(github-agent): add repo and docs context Q&A from connected sources #142 repo/docs context Q&A
• feat(extension): add screenshot-backed v1 review states #243 screenshot-backed extension review states
• feat(extension): harden role-based private/public panel rendering #244 role-based private/public extension rendering
• feat(github-app): add maintainer trust checklist and install preview flow #245 maintainer trust checklist and install preview
• feat(github-app): publish public-safe check-run annotations #272 public-safe check-run annotations

Completed foundation to link, not reopen: #135, #140, #141, #143, #144, #147, #148.

Phase 3: Repo Owner Intake Console

• feat(registration): create Gittensory self-dogfood registration pack #117 self-dogfood registration pack
• feat(config): add Gittensory repo focus manifest #118 repo focus manifest
• feat(issues): generate recommended contributor issue drafts from repo policy #119 contributor issue drafts
• feat(control-panel): add repo owner registration workspace #131 repo owner registration workspace
• feat(app): turn registration readiness into a guided owner workflow #246 guided owner workflow
• feat(signals): show direct-PR vs issue-discovery tradeoff summary #247 direct-PR vs issue-discovery tradeoff summary
• feat(settings): generate repo onboarding pack for accepted Gittensory repos #248 onboarding pack for accepted repos
• feat(settings): add repo policy compiler for focus manifests #277 repo policy compiler for focus manifests

Phase 4: Adoption Analytics + Launch System

• feat(control-panel): add usage and value analytics dashboard #134 usage and value analytics dashboard
• feat(analytics): add privacy-safe product usage event table #249 privacy-safe product usage event table
• feat(analytics): add role activation and retention rollups #250 role activation and retention rollups
• feat(app): add weekly value report export for operators and maintainers #251 weekly value report export
• feat(analytics): add outcome learning loop for recommendation quality #278 outcome learning loop for recommendation quality

Completed foundation to verify before claiming complete: #136, #137, #138, #139, #149, #153.

Phase 5: Ecosystem Distribution

• feat(raycast): scaffold Gittensory Raycast extension #113 Raycast scaffold
• feat(raycast): add miner command center #114 Raycast miner command center
• feat(raycast): add maintainer queue commands #115 Raycast maintainer queue commands
• research(mobile): validate native mobile vs PWA for maintainer digests #150 mobile/PWA research
• docs(launch): create miner quickstart by contribution lane #252 miner quickstart by contribution lane
• docs(launch): create maintainer install and trust guide #253 maintainer install and trust guide
• docs(launch): create repo-owner onboarding checklist #254 repo-owner onboarding checklist
• feat(pwa): add digest-ready maintainer queue notifications after research decision #255 digest-ready maintainer queue notifications
• feat(distribution): add Gittensory custom agent profiles #276 Gittensory custom agent profiles

Phase 6: Advanced Contribution Operating Layer

Post-v1 advanced systems after phases 0-5 are stable:

• roadmap(phase 6): advanced contribution operating layer #269 phase epic
• feat(agent): add replayable decision snapshots #270 replayable decision snapshots
• feat(agent): add repo-specific scenario simulator #271 repo-specific scenario simulator
• feat(mcp): ship native resources prompts and output schemas #273 MCP-native resources, prompts, and output schemas

Related cross-phase dependencies:

• feat(distribution): add Gittensory custom agent profiles #276 Gittensory custom agent profiles. Native parent phase: roadmap(phase 5): ecosystem distribution #238.
• feat(settings): add repo policy compiler for focus manifests #277 repo policy compiler for focus manifests. Native parent phase: roadmap(phase 3): repo owner intake console #236.
• feat(analytics): add outcome learning loop for recommendation quality #278 outcome learning loop for recommendation quality. Native parent phase: roadmap(phase 4): adoption analytics and launch system #237.

This phase must stay advisory and human-approved. It must not become public reward prediction, wallet tooling, public leaderboards, or autonomous PR automation.

Existing adoption/control-panel issues still related

• feat(control-panel): add agent run history and evidence viewer #132 agent run history and evidence viewer
• feat(control-panel): add interactive API docs and agent playground #133 interactive API docs and agent playground

Cross-cutting gates

• UI/frontend/browser-extension PRs must include actual screenshots or recordings for changed states. Missing evidence is a rejection reason.
• Public-output work must include sanitizer criteria for forbidden wallet/hotkey, reward-estimate, trust-score, public-score-prediction, private-reviewability, private-scoreability, and farming-language leakage.
• MCP/CLI work must include JSON-output, token-redaction, local path-redaction, and source-upload behavior criteria.
• Keep CI/check state separate from reviewer/mergeability state. Green checks alone do not make a PR merge-ready.