{"version":1,"pages":[{"slug":"overview","href":"/docs","title":"Documentation overview","description":"A complete documentation hub for Platform, PRISM, Agent Challenge, and the public website experience.","repo":"Website","tags":["overview","docs","start"],"headings":[{"id":"what-is-documented","title":"What is documented"},{"id":"how-to-read","title":"How to read the docs"}]},{"slug":"website/navigation","href":"/docs/website/navigation","title":"Website navigation","description":"How the public website routes map to product areas and active account surfaces.","repo":"Website","tags":["website","navigation","routes"],"headings":[{"id":"top-level-routes","title":"Top-level routes"},{"id":"account-surfaces","title":"Account surfaces"}]},{"slug":"website/challenge-pages","href":"/docs/website/challenge-pages","title":"Challenge pages","description":"How the challenge index, static challenge detail pages, and nested review pages behave.","repo":"Website","tags":["website","challenges","prism","agent"],"headings":[{"id":"index","title":"Challenge index"},{"id":"detail-pages","title":"Detail pages"}]},{"slug":"website/metrics-and-access","href":"/docs/website/metrics-and-access","title":"Metrics and access","description":"Metrics, benchmark language, and current Miner account access in the public UI.","repo":"Website","tags":["website","metrics","access","auth","dashboard"],"headings":[{"id":"metrics","title":"Metrics"},{"id":"access","title":"Account access"},{"id":"dashboard-overview","title":"Dashboard overview"}]},{"slug":"website/vercel-deployment","href":"/docs/website/vercel-deployment","title":"Vercel deployment checklist","description":"Environment, callback, migration, and verification checklist for deploying the active Miner auth and dashboard backend on Vercel.","repo":"Website","tags":["website","deployment","vercel","auth","environment"],"headings":[{"id":"runtime","title":"Runtime and project settings"},{"id":"environment","title":"Required environment variables"},{"id":"auth-signup","title":"Better Auth username signup"},{"id":"database-migrations","title":"Neon database and Drizzle migrations"},{"id":"signup-rate-limit","title":"Signup rate limit"},{"id":"secrets-verification","title":"Secret handling and deployment verification"}]},{"slug":"platform/overview","href":"/docs/platform/overview","title":"Platform overview","description":"The multi-challenge Bittensor validator platform that powers registry-backed challenge services.","repo":"Platform","tags":["platform","overview","bittensor","validator"],"headings":[{"id":"purpose","title":"Purpose"},{"id":"roles","title":"Core roles"}]},{"slug":"platform/architecture","href":"/docs/platform/architecture","title":"Platform architecture","description":"How the master, proxy, registry, Docker runtime, challenges, and Bittensor weight loop fit together.","repo":"Platform","tags":["platform","architecture","docker","proxy","weights"],"headings":[{"id":"components","title":"Main components"},{"id":"runtime-flow","title":"Runtime flow"}]},{"slug":"platform/quickstart","href":"/docs/platform/quickstart","title":"Platform quickstart","description":"Install the Platform repo, run validators, and start local master services.","repo":"Platform","tags":["platform","quickstart","install","local"],"headings":[{"id":"install","title":"Install"},{"id":"run","title":"Run local services"}]},{"slug":"platform/configuration","href":"/docs/platform/configuration","title":"Configuration","description":"YAML and environment settings for master, validator, database, Docker, GPU, weights, security, and observability.","repo":"Platform","tags":["platform","config","yaml","environment"],"headings":[{"id":"settings","title":"Settings groups"},{"id":"secrets","title":"Secrets"}]},{"slug":"platform/cli-reference","href":"/docs/platform/cli-reference","title":"CLI reference","description":"Command groups for master services, validators, challenges, GPU servers, weights, registry, and database migrations.","repo":"Platform","tags":["platform","cli","reference","operations"],"headings":[{"id":"commands","title":"Command groups"}]},{"slug":"platform/challenge-lifecycle","href":"/docs/platform/challenge-lifecycle","title":"Challenge lifecycle","description":"Register, activate, run, restart, and retire Dockerized challenge services.","repo":"Platform","tags":["platform","challenge","lifecycle","registry"],"headings":[{"id":"states","title":"States"},{"id":"workflow","title":"Workflow"}]},{"slug":"platform/api-reference","href":"/docs/platform/api-reference","title":"Platform API reference","description":"Admin, registry, public proxy, Docker broker, GPU agent, and fallback weight endpoints.","repo":"Platform","tags":["platform","api","admin","proxy","broker"],"headings":[{"id":"admin","title":"Admin and registry"},{"id":"proxy","title":"Public proxy"}]},{"slug":"platform/weight-aggregation","href":"/docs/platform/weight-aggregation","title":"Weight aggregation","description":"How challenge scores become final Bittensor UID weights.","repo":"Platform","tags":["platform","weights","bittensor","emissions"],"headings":[{"id":"epoch","title":"Epoch flow"},{"id":"rules","title":"Normalization rules"}]},{"slug":"platform/docker-gpu-orchestration","href":"/docs/platform/docker-gpu-orchestration","title":"Docker and GPU orchestration","description":"Local challenge containers, brokered Docker jobs, and remote GPU routing.","repo":"Platform","tags":["platform","docker","gpu","broker"],"headings":[{"id":"challenge-runtime","title":"Challenge runtime"},{"id":"broker-and-gpu","title":"Broker and GPU routing"}]},{"slug":"platform/data-security-observability","href":"/docs/platform/data-security-observability","title":"Data, security, and observability","description":"Schemas, persistence boundaries, security controls, logs, telemetry, and troubleshooting.","repo":"Platform","tags":["platform","security","data","observability"],"headings":[{"id":"data-model","title":"Data model"},{"id":"security","title":"Security controls"},{"id":"troubleshooting","title":"Troubleshooting"}]},{"slug":"agent-challenge/overview","href":"/docs/agent-challenge/overview","title":"Agent Challenge overview","description":"The term-challenge repository redirects to Agent Challenge: a SWE-Forge evaluator for miner-submitted software engineering agents.","repo":"Agent","tags":["agent","term-challenge","swe-forge","overview"],"headings":[{"id":"purpose","title":"Purpose"},{"id":"flow","title":"Evaluation flow"}]},{"slug":"agent-challenge/quickstart","href":"/docs/agent-challenge/quickstart","title":"Agent Challenge quickstart","description":"Install, run, submit an agent, and read results locally.","repo":"Agent","tags":["agent","quickstart","setup"],"headings":[{"id":"run","title":"Run service"},{"id":"submit","title":"Submit an agent"}]},{"slug":"agent-challenge/submissions","href":"/docs/agent-challenge/submissions","title":"Miner submissions","description":"Submission payloads, artifact staging, hashing, validation errors, and response fields.","repo":"Agent","tags":["agent","submissions","miners","artifacts"],"headings":[{"id":"payload","title":"Payload"},{"id":"safety","title":"Artifact safety"}]},{"slug":"agent-challenge/api","href":"/docs/agent-challenge/api","title":"Agent Challenge API","description":"Public submission and leaderboard endpoints plus internal Platform health/version/weights endpoints.","repo":"Agent","tags":["agent","api","weights","leaderboard"],"headings":[{"id":"public","title":"Public endpoints"},{"id":"internal","title":"Internal endpoints"}]},{"slug":"agent-challenge/evaluation-scoring","href":"/docs/agent-challenge/evaluation-scoring","title":"Evaluation and scoring","description":"How SWE-Forge tasks are selected, executed, and converted into scores.","repo":"Agent","tags":["agent","evaluation","scoring","swe-forge"],"headings":[{"id":"task-selection","title":"Task selection"},{"id":"scoring","title":"Scoring"}]},{"slug":"agent-challenge/swe-forge-contract","href":"/docs/agent-challenge/swe-forge-contract","title":"SWE-Forge task contract","description":"Contract between the challenge service, SWE-Forge Docker images, and submitted agent artifacts.","repo":"Agent","tags":["agent","swe-forge","docker","contract"],"headings":[{"id":"contract","title":"Container contract"},{"id":"metadata","title":"Task metadata"}]},{"slug":"agent-challenge/platform-weights","href":"/docs/agent-challenge/platform-weights","title":"Platform weights","description":"How completed agent scores are exported to the Platform master.","repo":"Agent","tags":["agent","weights","platform","bittensor"],"headings":[{"id":"export","title":"Challenge export"},{"id":"normalization","title":"Platform normalization"}]},{"slug":"agent-challenge/configuration-security","href":"/docs/agent-challenge/configuration-security","title":"Configuration and security","description":"Environment settings, Docker execution defaults, data model, and security boundaries.","repo":"Agent","tags":["agent","config","security","deployment"],"headings":[{"id":"settings","title":"Settings"},{"id":"security","title":"Security"}]},{"slug":"agent-challenge/data-model","href":"/docs/agent-challenge/data-model","title":"Data model and statuses","description":"Stored entities and lifecycle statuses for submissions, evaluation jobs, and task results.","repo":"Agent","tags":["agent","data-model","statuses"],"headings":[{"id":"entities","title":"Entities"},{"id":"statuses","title":"Statuses"}]},{"slug":"prism/overview","href":"/docs/prism/overview","title":"PRISM overview","description":"Architecture mining challenge for model families, training variants, evaluation, and reward attribution.","repo":"PRISM","tags":["prism","overview","architecture-mining"],"headings":[{"id":"purpose","title":"Purpose"},{"id":"entities","title":"Main entities"}]},{"slug":"prism/system-architecture","href":"/docs/prism/system-architecture","title":"PRISM system architecture","description":"How PRISM fits into Platform registry, proxy, challenge runtime, validator workers, and weight aggregation.","repo":"PRISM","tags":["prism","architecture","platform","weights"],"headings":[{"id":"boundaries","title":"Runtime boundaries"},{"id":"flow","title":"End-to-end flow"}]},{"slug":"prism/miner-quickstart","href":"/docs/prism/miner-quickstart","title":"PRISM miner quickstart","description":"Prepare a reproducible architecture submission and understand validator checks.","repo":"PRISM","tags":["prism","quickstart","miner","submission"],"headings":[{"id":"prepare","title":"Prepare a submission"},{"id":"checklist","title":"Local checklist"}]},{"slug":"prism/submission-manifest","href":"/docs/prism/submission-manifest","title":"Submission manifest","description":"Manifest fields for architecture identity, training variants, artifacts, reproducibility, and review metadata.","repo":"PRISM","tags":["prism","manifest","schema"],"headings":[{"id":"fields","title":"Required fields"},{"id":"shape","title":"Docs-level shape"}]},{"slug":"prism/model-contract-hooks","href":"/docs/prism/model-contract-hooks","title":"Model contract and hooks","description":"Interfaces validators use to build, inspect, train, and evaluate submitted architectures.","repo":"PRISM","tags":["prism","model","hooks","evaluation"],"headings":[{"id":"contract","title":"Contract"},{"id":"hooks","title":"Hooks"}]},{"slug":"prism/architecture-ownership","href":"/docs/prism/architecture-ownership","title":"Architecture ownership","description":"How canonical architecture families are created, deduplicated, disputed, and credited.","repo":"PRISM","tags":["prism","ownership","deduplication","q_arch"],"headings":[{"id":"rules","title":"Ownership rules"},{"id":"evidence","title":"Review evidence"}]},{"slug":"prism/training-variants","href":"/docs/prism/training-variants","title":"Training variants","description":"How recipes, schedules, data mixes, checkpoints, and loss improvements are credited inside an architecture family.","repo":"PRISM","tags":["prism","training","q_recipe","loss"],"headings":[{"id":"identity","title":"Variant identity"},{"id":"leaderboard","title":"Variant leaderboard"}]},{"slug":"prism/scoring","href":"/docs/prism/scoring","title":"Scoring, rewards, and weights","description":"How PRISM converts architecture and training evaluation into miner rewards and Platform weights.","repo":"PRISM","tags":["prism","scoring","rewards","weights"],"headings":[{"id":"components","title":"Scoring components"},{"id":"weights","title":"Weights contract"}]},{"slug":"prism/evaluation-pipeline","href":"/docs/prism/evaluation-pipeline","title":"Evaluation pipeline","description":"Validator pipeline from intake through schema checks, sandbox execution, benchmark scoring, consensus, and publication.","repo":"PRISM","tags":["prism","evaluation","validators","pipeline"],"headings":[{"id":"stages","title":"Stages"},{"id":"assignments","title":"Validator assignments"}]},{"slug":"prism/benchmarks-scaling","href":"/docs/prism/benchmarks-scaling","title":"Benchmarks and scaling","description":"Benchmark families, resource strategy, sharding, caching, and scaling behavior for validator workers.","repo":"PRISM","tags":["prism","benchmarks","scaling","gpu"],"headings":[{"id":"benchmarks","title":"Benchmark types"},{"id":"scaling","title":"Scaling controls"}]},{"slug":"prism/evaluation-data","href":"/docs/prism/evaluation-data","title":"Evaluation data","description":"Data boundaries, leakage prevention, shard handling, and reproducibility expectations.","repo":"PRISM","tags":["prism","data","leakage","benchmarks"],"headings":[{"id":"classes","title":"Dataset classes"},{"id":"policy","title":"Data policy"}]},{"slug":"prism/security","href":"/docs/prism/security","title":"PRISM security","description":"Security model for untrusted miner code, public proxy traffic, internal tokens, sandboxing, and hidden benchmark data.","repo":"PRISM","tags":["prism","security","sandbox","tokens"],"headings":[{"id":"threat-model","title":"Threat model"},{"id":"secrets","title":"Secret handling"}]},{"slug":"prism/api-reference","href":"/docs/prism/api-reference","title":"PRISM API reference","description":"Public and internal PRISM API surfaces for miners, reviewers, validators, and Platform operators.","repo":"PRISM","tags":["prism","api","reference"],"headings":[{"id":"endpoints","title":"Endpoint summary"},{"id":"shapes","title":"Response shapes"}]},{"slug":"prism/operator-guide","href":"/docs/prism/operator-guide","title":"PRISM operator guide","description":"Register PRISM, run workers, assign validators, collect weights, and diagnose failures.","repo":"PRISM","tags":["prism","operator","validator","troubleshooting"],"headings":[{"id":"checklist","title":"Operator checklist"},{"id":"troubleshooting","title":"Troubleshooting"}]}]}