Skip to content

Epic: Miner Wave 3.5 — Wire the autonomous loop end-to-end #5130

Description

@JSONbored

Context

Miner Wave 1 (#11), Wave 2 (#12), and Wave 3 (#13) milestones are all closed — every individual issue's PR genuinely merged (spot-checked and cross-referenced with closedByPullRequestsReferences, no false closures found). But a code-level audit (import-graph traced from bin/gittensory-miner.js outward, plus targeted git grep for real call sites vs. definitions/tests) found that the actual discover → analyze → plan → prepare → create → manage → repeat loop this whole system exists to run has zero live entrypoint end-to-end today. The individual pieces are real and wired in isolation:

  • discover → rank → enqueue: fully wired (opportunity-fanout.jsopportunity-ranker.jsportfolio-discovery.jsportfolio-queue.js, reachable from the discover CLI command).
  • manage poll: fully wired (ci-poller.jsevent-ledger.jsmanage-status.js).
  • Governor decision auditing: a real, working SQLite append-only log (governor-ledger.js), reachable via governor list.
  • .gittensory-miner.yml parsing: real and live (opportunity-ranker.js calls parseMinerGoalSpecContent).

But the create and repeat steps — the actual point of the system — are not reachable from anywhere:

  • attempt-runner.js's runMinerAttempt (the create→review→gate→submit orchestrator from maintainer: wire the submission-gate trigger into the harness driving loop #2337) is never dispatched by the CLI.
  • The coding-agent driver seam (createCodingAgentDriver/runCodingAgentAttempt in packages/gittensory-engine) has zero production caller anywhere — only test and doc references.
  • attempt-runner.js's injectable runSlopAssessment self-review dependency has no production implementation.
  • Governor counters (rate-limit buckets, backoff attempts, budget/turn/termination totals, convergence history, reputation/self-plagiarism throttle state) are pure in/out transforms with nothing persisting them between separate CLI invocations — contrast with the ledger above, which does persist.
  • loop-reentry.js/loop-closure.js (the "automatically re-invoke discovery on a resolved outcome" pieces) are CLI-unreachable; the Dockerfile's own CMD is ["doctor"], a one-shot batch command — nothing autonomously repeats the cycle today.

This milestone closes that gap: wire the 5 pieces below, in dependency order, so the loop this whole system was built for actually runs unattended, end to end.

Sub-issues

All maintainer-only: this is the core autonomous-write control-flow, same tier as the rest of Wave 3.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.

Projects

Status
Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions