PRISM

Architecture mining, training variants, scoring, and operators.

PRISMPRISM

PRISM system architecture

How PRISM fits into Platform registry, proxy, challenge runtime, validator workers, and weight aggregation.

#prism/system-architecture
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.

LayerResponsibility
Platform masterRegistry, runtime, token handling, weight collection.
Challenge proxySafe public PRISM routes.
PRISM serviceSubmissions, evaluation state, leaderboards, internal weights.
Validator workersSandboxed 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.