roadmap: Wave 2 — Agent Layer (auto-maintain + auto-development)

[JSONbored]

Continues: #525 (Wave 1 — contribution quality & adoption).

Vision

Gittensory becomes the agent layer / control plane for automated development on gittensor repos — both miners and maintainers — keeping its anti-slop, deterministic, privacy-preserving DNA. Local planning docs: docs/roadmap/{agent-layer-auto-maintain,current-state-and-readiness,discovery-sweep-findings}.md.

Architectural rule (hybrid)

Cloud acts on GitHub state (merge/close/review/label); the user's local harness generates code. The trust boundary never moves; anti-slop is the throttle. A conscious evolution past Wave 1's 'advisory-only, never auto-merge' → graduated, opt-in, deny-by-default autonomy, human-in-the-loop preserved via the approval dial.

Phases

• Phase 0 — foundations & autonomy framework → roadmap(agent phase 0): foundations & autonomy framework #768
• Phase 1 — maintainer auto-maintain → roadmap(agent phase 1): maintainer auto-maintain (cloud action layer) #769
• Phase 2 — miner auto-development → roadmap(agent phase 2): miner auto-development (local orchestration) #770
• Phase 3 — automation controls → roadmap(agent phase 3): automation controls (dashboard/CLI/MCP) #771

Anti-slop strategy (moat)

Meta-loop: the same gate that enables auto-dev gates the agents it enables. Plus agent-authored attribution, per-agent slop budget/rate-limit, golden-fixture guard (#565), gittensor-team alignment.

Unlocks after Wave 1 (M1)

Depends on Wave-1 prerequisite cluster (#551/#538/#555/#552/#540/#554) + write-safety fixes (B-series).

Milestones: M2–M5 (06-24 → 06-30).