In one line

Bittensor's own on-chain identity for subnet 64 names exactly one repository: chutesai/chutes. That repository is a developer client — how you register, build an image, and deploy an application on rented GPUs. Its own README then names two other repositories, owned by a different account, as where the miner and validator code actually live. Neither is the chain's own pointer.

What this map shows — everything a developer touches inside the repo the chain actually names (register, build, deploy, pay), and the one verification mechanism that repo documents (GraVal, a GPU-authenticity check). Both external repositories are drawn as boxes at the edge, reachable only by a dashed line, because that is exactly how reachable they are from here: named, not present.

Why it stops there — this course's pinned corpus is chutesai/chutes only. Drawing the scoring logic inside chutes-api would mean inventing it; the instruction for this map was explicit that a smaller, honest map beats a larger invented one.