PlatformPlatform
Platform architecture
How the master, proxy, registry, Docker runtime, challenges, and Bittensor weight loop fit together.
platformarchitecturedockerproxyweights
Main components
The single Platform API serves token-gated admin/registry routes and public proxy traffic alongside runtime orchestration and Bittensor integration.
| Component | Purpose |
|---|---|
| Admin API | Private challenge registry and lifecycle operations. |
| Public proxy | Forwards safe public traffic to active challenge containers. |
| Docker orchestrator | Pulls images, starts containers, mounts volumes and secrets, verifies readiness. |
| Docker broker | Runs bounded challenge-side Docker jobs without exposing the host socket to challenges. |
| Weight service | Collects per-challenge weights and submits normalized UID weights. |
Runtime flow
A challenge becomes public only after it is registered, activated, pulled, started, and validated through health/version checks.
The proxy accepts `/challenges/{slug}/...` only for active challenges and blocks internal paths from public access.