List view

• Test Suite Health (maintainer)

  Consolidate the bolt-on '-coverage'/'-branch-coverage' test-file family into their sibling main suites and guard against the pattern recurring. Runtime + maintainability work; no coverage regression allowed.

  No due date

  •8/12 issues closed
  66% complete4 open8 closed

• Hosted Bare-Metal Execution Plane (maintainer)

  Build-out of the dedicated bare-metal execution plane for hosted ORB + AMS — the end-state infrastructure replacing the interim Cloudflare Workers/Containers deployment for hosted tenants. Scope: the k3s + Kata Containers stack decided in #7180's isolation-tier research, hardware procurement/enablement (SEV-SNP a hard criterion, per #8137), confidential-compute (CoCo) runtime classes for attested evaluation, tenant egress controls on the new plane, and the migration seams from the interim Cloudflare deployment. Self-host today already runs on bare metal; this milestone is the HOSTED product's plane. Created 2026-07-24: no existing milestone housed this work (ORB/AMS Cloud Readiness track the interim control-plane, not the metal).

  No due date

  •0/8 issues closed
  0% complete8 open0 closed

• PostHog Consolidation

  Consolidate observability onto PostHog: error tracking across all six Sentry surfaces (ORB self-host server, ORB hosted Worker, miner CLI, discovery-index, review-enrichment, UI), web analytics off Umami, session replay + AI observability depth, then gated Sentry/Umami sunset. Mirrors metagraphed's PostHog Consolidation milestone. Created new (rather than reusing an existing milestone) because this is a cross-cutting observability-platform migration spanning ORB, miner, Workers, and UI — no existing open milestone covers platform-observability work.

  No due date

  •9/21 issues closed
  42% complete12 open9 closed

• ORB - Long Term Features & Improvements II

  Successor to milestone #18 (closed 2026-07-17 but still actively receiving closed issues through 2026-07-20 — the grab-bag of general self-host correctness bugs, test-coverage gaps, and feature work across apps/**, packages/**, src/**, .github/**, scripts/** never stopped being a real need, it just lost its open home). Created 2026-07-21 after an adversarial re-check found the contributor-available floor had collapsed because this was the only milestone catching ordinary (non-Cloud-Readiness) engineering work and it had no open successor.

  Due by July 26, 2026

  •238/264 issues closed
  90% complete26 open238 closed

• Miner Wave 4.6 — AMS Hardening Round 3

  Recurring home for post-Wave-4/4.5 gap-audit findings in packages/loopover-engine and packages/loopover-miner — correctness bugs, unenforced documented contracts, thin coverage on branchy logic. Same shape/contributor-openness as Wave 4 and 4.5 (both fully closed). Created 2026-07-21 per reference.md's recurring-category milestone-discipline note.

  No due date

  •52/55 issues closed
  94% complete3 open52 closed

• Miner Wave 5.1 — Bittensor-Native Funding Track (maintainer)

  Subnet-funded reward-pool model: a Bittensor subnet funds its own reward pool for its own GitHub repo, AMS discovers/does the work, ORB reviews/merges, settlement flows through a layer that keeps gittensor in the path. A candidate resolution path for #4781's open economics-mechanism question — not a replacement for Wave 5's existing tradfi-rental scope, a parallel Bittensor-native track. Maintainer-only planning for now.

  Due by July 31, 2026

  •5/7 issues closed
  71% complete2 open5 closed

• Miner Wave 5 — Rent-a-Loop (maintainer)

  A hosted, multi-tenant product: rent gittensor-powered autonomous development-loop time against any repository. See the epic issue for full scope across 7 groups.

  Overdue by 2 day(s)

  •

  Due by July 24, 2026

  •64/84 issues closed
  76% complete20 open64 closed