Current product gaps
- Manual retry of one failed rollout is available through the Runtime CLI, not a Registry retry button.
- There is no general command that turns an arbitrary local file or directory directly into a canonical Artifact.
- Experiment preflight mode is reserved and currently unavailable.
- Registry Run Detail renders a final-score card only when the Run snapshots a Registry score policy. A defined policy remains visible as partial or unavailable until its selected immutable Runtime statistics are complete; a Run with no score policy shows no card. Raw custom statistics remain a Runtime CLI workflow through
fleet-runtime runs report. - External trace views do not yet cover every multi-producer and human-QA workflow.
- Post-close re-verification cannot reconstruct a verifier that explicitly required retained live rollout state.
- Experiment Analysis produces Task-scoped child Review reports and does not run a cross-Task synthesis model.
When to escalate
Escalate when the required operation would change immutable bytes in place, discard sealed evidence, guess a secret source, silently move a release identity, or infer a verdict from unavailable Runtime state. Those are contract or product questions, not missing commands.