Reference
RunPod execution and support status
Distinguish the available offline and read-only RunPod contracts from unavailable live execution.
Current boundary
The finetuning runpod command surface exists. It supports offline planning, dry-run lifecycle output, read-only diagnostics and credentialed volume listing, plus fake lifecycle and hardening contracts. volume list reports pinned provider fields and marks ownership as unverified because the pinned NetworkVolume DTO has no ownership metadata.
Live Pod creation, stop, termination, cleanup, and network-volume ensure or deletion fail closed before a mutation transport call. No authorized live qualification evidence or provider spend was produced. Production recipes, spot semantics, generic exec/log REST, direct Secrets representation, Serverless, and fleet execution remain unavailable.
Retained phase reports
- Pinned REST and capability evidence
- Lifecycle and safety evidence
- Training hardening evidence
- Serverless and fleet evidence
Use finetuning runpod --help for the tested command inventory and finetuning runpod doctor --json for machine-readable capability status.