Platform

Master validator, registry, proxy, runtime, and weights.

PlatformPlatform

Data, security, and observability

Schemas, persistence boundaries, security controls, logs, telemetry, and troubleshooting.

#platform/data-security-observability
platformsecuritydataobservability

Data model

Challenge records, registry responses, broker jobs, GPU servers, and fallback weights are represented as typed schemas.

ModelPurpose
ChallengeRecordStored challenge metadata plus token hash and hint.
RegistryChallengeValidator-facing active challenge metadata.
BrokerRunRequestBounded Docker evaluation job requested by a challenge.
GpuServerRecordRemote GPU capacity and health metadata.
FallbackWeightsSigned latest weights for resilience.

Security controls

Platform separates public challenge traffic from private control-plane traffic.

  • Admin endpoints require admin tokens.
  • Internal challenge weights require per-challenge bearer tokens.
  • Proxy strips sensitive headers and blocks internal paths.
  • Clear challenge tokens are returned only once at creation.
  • Broker and GPU endpoints are token-protected.

Troubleshooting

Common failures are usually auth, runtime readiness, proxy routing, or weight normalization issues.

SymptomLikely cause
401 adminMissing or wrong admin token.
403 proxyPublic request targeted blocked internal path.
404 proxyChallenge is unknown or inactive.
502 proxyChallenge container is unavailable.
Empty weightsNo positive known-hotkey weights returned by active challenges.