PRISMPRISM
PRISM system architecture
How PRISM fits into Platform registry, proxy, challenge runtime, validator workers, and weight aggregation.
prismarchitectureplatformweights
Runtime boundaries
PRISM runs as a registered Platform challenge container. Platform owns registry state, lifecycle status, internal tokens, runtime operations, and final Bittensor submission.
Public review routes live under `/challenges/prism/...`; internal weight routes remain private.
| Layer | Responsibility |
|---|---|
| Platform master | Registry, runtime, token handling, weight collection. |
| Challenge proxy | Safe public PRISM routes. |
| PRISM service | Submissions, evaluation state, leaderboards, internal weights. |
| Validator workers | Sandboxed build, benchmark, and scoring jobs. |
End-to-end flow
A miner submission becomes a reward weight after validation, evaluation, attribution, and aggregation.
- Miner uploads a manifest and artifacts.
- PRISM validates schema, checksums, and ownership claims.
- Workers build and evaluate the submission.
- Scores update architecture and training leaderboards.
- PRISM returns hotkey weights to Platform.