You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The autonomous-miner system (AMS) currently runs a read-only discovery loop against gittensory's own cross-repo backlog — it can list and search claimable work, but by design has no autonomous claiming or PR-submission path yet (that mechanical loop — discover → claim → code → submit → repeat, with a safety governor — is the scope of the existing Miner Wave 3 milestone, tracked separately and already in progress).
Separately, gittensory already exercises real review/merge authority on any repository that installs its GitHub App, through a graduated, per-repo, config-driven autonomy setting.
This milestone is the natural next step once Wave 3's loop mechanics land: instead of that loop only ever working gittensory's own backlog, let any developer describe an idea for their own repository and rent autonomous development-loop time to build it, funded through the gittensor network's compute market. That's a genuinely new product, not an extension of an internal tool — it has to work with any repository, not just gittensory's own, and it has to be offered as a hosted, multi-tenant service rather than something a self-hoster runs for themselves. The core review-gate product remains self-host-only; this is a new, separate hosted surface layered on top of it.
Reusable today: the maintainer-agent's review/merge authority model (already works on any installed repo) and the append-only ledger pattern used by the miner package. Everything else — a coding agent generalized off gittensory's own conventions, gittensor-native compute economics, multi-tenant isolation and sandboxing, and the billing/legal/support layer a hosted product needs — is mostly net-new. That is why this milestone is deliberately broken into small, single-slice issues across seven groups rather than a handful of large ones.
Foundations (F) can start immediately and in parallel — F3 specifically needs sign-off from the gittensor subnet side, not just engineering. Generalized-agent (G), economics (E), and platform (P) work can proceed in parallel once their relevant foundation spec is approved, but G3 also depends on Miner Wave 3's loop mechanics existing. Idea-intake (I) wires G to F1. Billing (B) layers on top of E and P. Observability/launch (O) is the closing gate — O4 doesn't close until every other group in this milestone has shipped and been proven against one real external pilot repository.
Context
The autonomous-miner system (AMS) currently runs a read-only discovery loop against gittensory's own cross-repo backlog — it can list and search claimable work, but by design has no autonomous claiming or PR-submission path yet (that mechanical loop — discover → claim → code → submit → repeat, with a safety governor — is the scope of the existing Miner Wave 3 milestone, tracked separately and already in progress).
Separately, gittensory already exercises real review/merge authority on any repository that installs its GitHub App, through a graduated, per-repo, config-driven autonomy setting.
This milestone is the natural next step once Wave 3's loop mechanics land: instead of that loop only ever working gittensory's own backlog, let any developer describe an idea for their own repository and rent autonomous development-loop time to build it, funded through the gittensor network's compute market. That's a genuinely new product, not an extension of an internal tool — it has to work with any repository, not just gittensory's own, and it has to be offered as a hosted, multi-tenant service rather than something a self-hoster runs for themselves. The core review-gate product remains self-host-only; this is a new, separate hosted surface layered on top of it.
Reusable today: the maintainer-agent's review/merge authority model (already works on any installed repo) and the append-only ledger pattern used by the miner package. Everything else — a coding agent generalized off gittensory's own conventions, gittensor-native compute economics, multi-tenant isolation and sandboxing, and the billing/legal/support layer a hosted product needs — is mostly net-new. That is why this milestone is deliberately broken into small, single-slice issues across seven groups rather than a handful of large ones.
Scope summary
How to use this issue
Foundations (F) can start immediately and in parallel — F3 specifically needs sign-off from the gittensor subnet side, not just engineering. Generalized-agent (G), economics (E), and platform (P) work can proceed in parallel once their relevant foundation spec is approved, but G3 also depends on Miner Wave 3's loop mechanics existing. Idea-intake (I) wires G to F1. Billing (B) layers on top of E and P. Observability/launch (O) is the closing gate — O4 doesn't close until every other group in this milestone has shipped and been proven against one real external pilot repository.