PlatformPlatform
Challenge lifecycle
Register, activate, run, restart, and retire Dockerized challenge services.
platformchallengelifecycleregistry
Sources
States
Challenge records support registry lifecycle states. Only active challenges should be exposed through public routing and weight collection.
| State | Meaning |
|---|---|
| draft | Created but not yet active. |
| active | Eligible for runtime orchestration, proxy traffic, and weight collection. |
| inactive | Registered but removed from active challenge flows. |
| disabled | Retained in metadata but operationally disabled. |
Workflow
A typical challenge moves from registration to runtime readiness before activation.
bash
uv run platform challenge register demo ghcr.io/org/demo:latest 10 uv run platform challenge pull demo uv run platform challenge activate demo uv run platform challenge restart demo uv run platform challenge deactivate demo