Skip to content

roadmap: productionize Gittensory as the Gittensor base agent #32

Description

@JSONbored

Goal

Make Gittensory the deterministic base-agent layer for Gittensor OSS contribution mining.

Miners should get actionable next work, scoreability blockers, cleanup-first guidance, pending-merge scenarios, local branch preflight, and PR packet generation.

Maintainers should get confirmed-miner context, quiet-by-default GitHub App behavior, repo settings previews, reviewability intelligence, and reduced noisy PR flow.

Repo owners should get registration readiness, lane/config recommendations, label policy guidance, maintainer-cut readiness, and intake health signals.

Public/Private Boundary

Public GitHub output must stay sanitized: no wallets, hotkeys, payout/reward estimates, raw trust scores, private reviewability, or public shaming.

Private scoreability and reward/risk context belongs in authenticated MCP/API surfaces only.

Quality Gate

All child issues must preserve npm run test:ci, keep global coverage at or above 95%, and add invariant/regression tests for touched behavior.

Child Issues

Notes

Use this roadmap to steer Gittensor contributor work toward backend signals, MCP agent utility, GitHub App maintainer safety, and production readiness. This is intentionally not a website/docs polish roadmap.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions