Background
Gittensory is moving from a useful MCP/GitHub App foundation into the deterministic base-agent layer for Gittensor OSS contribution mining. The next phase should make the system more useful for miners, maintainers, repo owners, and operators without turning it into a competing Gittensor frontend or noisy autonomous PR bot.
Miners need actionable next work, scoreability blockers, cleanup-first guidance, pending-merge projections, local branch preflight, and public-safe PR packet generation. Maintainers need confirmed-miner context, quiet-by-default GitHub App behavior, repo settings previews, reviewability intelligence, and less noisy PR flow. Repo owners need registration readiness, config guidance, maintainer-cut readiness, label policy checks, and intake-health signals.
Website/docs-only work is not the current contributor priority unless it directly supports install, safety, release, or registration readiness. The focus is backend signals, MCP agent utility, GitHub App maintainer safety, upstream drift, release readiness, and Raycast as a lightweight operator surface.
Public/Private Output Boundaries
Public GitHub output must stay sanitized. It must not include wallets, hotkeys, payout or reward estimates, raw trust scores, private reviewability, public shaming, private scoreability context, or farming language. Private MCP/API surfaces may include scoreability and risk context when authenticated, but they still must not claim guaranteed payout outcomes.
Quality Bar
The repo quality target is now 97% global coverage for lines, statements, functions, and branches. Contributors should aim for 98%+ branch coverage locally so CI does not fail from small coverage variance. Every child issue should include targeted tests, invariant/regression tests, and public/private safety tests where relevant.
Child Issues
Background
Gittensory is moving from a useful MCP/GitHub App foundation into the deterministic base-agent layer for Gittensor OSS contribution mining. The next phase should make the system more useful for miners, maintainers, repo owners, and operators without turning it into a competing Gittensor frontend or noisy autonomous PR bot.
Miners need actionable next work, scoreability blockers, cleanup-first guidance, pending-merge projections, local branch preflight, and public-safe PR packet generation. Maintainers need confirmed-miner context, quiet-by-default GitHub App behavior, repo settings previews, reviewability intelligence, and less noisy PR flow. Repo owners need registration readiness, config guidance, maintainer-cut readiness, label policy checks, and intake-health signals.
Website/docs-only work is not the current contributor priority unless it directly supports install, safety, release, or registration readiness. The focus is backend signals, MCP agent utility, GitHub App maintainer safety, upstream drift, release readiness, and Raycast as a lightweight operator surface.
Public/Private Output Boundaries
Public GitHub output must stay sanitized. It must not include wallets, hotkeys, payout or reward estimates, raw trust scores, private reviewability, public shaming, private scoreability context, or farming language. Private MCP/API surfaces may include scoreability and risk context when authenticated, but they still must not claim guaranteed payout outcomes.
Quality Bar
The repo quality target is now 97% global coverage for lines, statements, functions, and branches. Contributors should aim for 98%+ branch coverage locally so CI does not fail from small coverage variance. Every child issue should include targeted tests, invariant/regression tests, and public/private safety tests where relevant.
Child Issues