metagraphed

Use when writing, validating, or preparing ANY contribution or pull request to the JSONbored/metagraphed repo — adding/enriching a subnet's public surfaces (the most common contribution), a code/schema change to the Worker API or build scripts, picking an issue, running the local gates, and formatting the commit + PR. metagraphed reviews PRs ONE-SHOT via the Gittensory Gate (the GitHub App that auto-merges/auto-closes) plus a strict CI suite; there is no review back-and-forth, so a PR must be correct, in-scope, and green before it is pushed. Surfaces live in ONE file per subnet (registry/subnets/<slug>.json) — never per-surface candidate files, never split across multiple PRs. Also covers frontend PRs against apps/ui/ (the web app, folded into this repo via monorepo consolidation) — visual changes require a before/after screenshot table and are always held for manual review. Invoke for any "contribute to / open a PR against / enrich a subnet in / add a surface to / fix a bug in / add a frontend feature to met

Use when a developer asks what a Bittensor subnet does, whether it's up right now, or how to call/integrate its API — e.g. "which subnet does image generation", "is subnet 7 healthy", "how do I call the Chutes API", "build on a Bittensor subnet". Backed by metagraphed (api.metagraph.sh), the live operational + integration registry for ~129 subnets.