Found during a 2026-07-08 miner-roadmap audit: the optional hosted discovery plane has real coverage on the client side and zero coverage on the server side.
The Wave 2 tracker (#2353, Phase 6) itemizes three client-facing pieces: "define the public-data-only discovery-index API contract," "add anonymized telemetry event schema for the optional hosted plane," and "add client-side soft-claim coordination request builder." All three describe what a gittensory-miner instance sends/expects. None of them, nor anything in the maintainer-only milestone (#13), covers actually building and operating the server that answers that contract.
Per the roadmap's own deployment model, this plane is optional, metadata-only (public GitHub data, never source or actor-capable credentials), and exists to mitigate a real rate-limit problem: one shared crawler across the miner fleet instead of N independent ones hammering the same repos (the roadmap explicitly cites the prior rate-limit incident, #1936). #1970 (self-hosted ORB federation) is adjacent infrastructure but a different system — it's cross-instance ORB telemetry federation, not a public discovery index.
Flagged maintainer-only because this is a shared, owner-operated, multi-tenant service with real abuse/cost/dedup posture decisions — closer in kind to other owner-run hosted infra than a contributor scaffold task, even though it doesn't itself touch the autonomous-write/kill-switch boundary.
Deliverables
References
Cloud Readiness cross-reference (added 2026-07-12)
This is the "build as documented" path for #4943 ("Decide the fate of the unimplemented hosted discovery-plane"), now also in this milestone. Do not start this until #4943 reaches an explicit decision — if the decision is to retire or fold this into the broader hosted architecture instead, this issue should be closed or re-scoped accordingly rather than built as originally specified.
Found during a 2026-07-08 miner-roadmap audit: the optional hosted discovery plane has real coverage on the client side and zero coverage on the server side.
The Wave 2 tracker (#2353, Phase 6) itemizes three client-facing pieces: "define the public-data-only discovery-index API contract," "add anonymized telemetry event schema for the optional hosted plane," and "add client-side soft-claim coordination request builder." All three describe what a
gittensory-minerinstance sends/expects. None of them, nor anything in the maintainer-only milestone (#13), covers actually building and operating the server that answers that contract.Per the roadmap's own deployment model, this plane is optional, metadata-only (public GitHub data, never source or actor-capable credentials), and exists to mitigate a real rate-limit problem: one shared crawler across the miner fleet instead of N independent ones hammering the same repos (the roadmap explicitly cites the prior rate-limit incident, #1936). #1970 (self-hosted ORB federation) is adjacent infrastructure but a different system — it's cross-instance ORB telemetry federation, not a public discovery index.
Flagged maintainer-only because this is a shared, owner-operated, multi-tenant service with real abuse/cost/dedup posture decisions — closer in kind to other owner-run hosted infra than a contributor scaffold task, even though it doesn't itself touch the autonomous-write/kill-switch boundary.
Deliverables
References
Cloud Readiness cross-reference (added 2026-07-12)
This is the "build as documented" path for #4943 ("Decide the fate of the unimplemented hosted discovery-plane"), now also in this milestone. Do not start this until #4943 reaches an explicit decision — if the decision is to retire or fold this into the broader hosted architecture instead, this issue should be closed or re-scoped accordingly rather than built as originally specified.