just-vibeML deployment · plan by default
/ml-rollout
Prepare shadow, canary or staged rollout of a model version with rollback criteria
Use for a scoped model promotion plan or transition; ml-report documents offline evidence.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select ml-rollout from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv ml-rollout, /just-vibe ml-rollout and /jv:ml-rollout in Claude. See shortcut setup and context examples.
/just-vibe:ml-rollout Prepare a canary rollout and rollback plan for the new ranking model; do not change production traffic./just-vibe:ml-rollout Plan a canary when the previous model expects an older feature schema./just-vibe:ml-rollout Assess rollout readiness without live routing access or shadow-inference budget.What the agent does
- Check feature, schema, package and artifact compatibility, and preserve a usable fallback artifact and traffic-switch mechanism.
- Define shadow or canary cohort routing, comparison metrics and predeclared stop criteria as staged gates.
- Verify authorized transitions against evidence.
Inputs
- candidate/stable models, target service, evaluation evidence, traffic constraints, and rollback thresholds.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Shadow/canary/staged rollout and recovery; execution only on explicitly authorized targets.
- Writes
- Inspect/plan: inspect or propose; save requested artifacts only. Apply: make the requested changes or execute the requested operation within its resolved target and limits. Local preparation does not authorize live, remote, destructive or paid actions; existing explicit session authorization still applies.
- Mode
- Plan rollout; apply for requested rollout configuration or an explicitly requested promotion.
- Prerequisites
- Versioned model and preprocessing artifacts, input/output schema, runtime/dependencies, operating targets, and authorized environment. Validate artifact trust before loading formats that can execute code. Packaging or writing monitoring configuration does not deploy a model or enable a hosted service.
Expected output
- Rollout plan or execution record with the cohort/gate/metric plan, candidate and fallback identities, actual traffic/version state and rollback criteria.
How the work is checked
- Canary failures halt progression; rollback accounts for incompatible feature/schema changes.
When to stop or clarify
- No automatic full rollout from good offline metrics. Shadow traffic may incur cost and privacy obligations covered by the requested scope.
Handling missing context
- Infer
- Read artifact format/trust, preprocessing schema, serving runtime, compatibility and existing rollout controls.
- Assume
- Prepare packaging/configuration and isolated checks without treating them as a live deployment.
- Ask
- Resolve the target, rollback compatibility and operating limits before rollout or load generation; missing production access does not block packaging.
Technical guidance
- Evidence
- Resolve candidate/baseline models, compatibility, routing identity, shadow side effects and rollback conditions.
- Method
- Compare shadow or canary traffic under a stable assignment policy; define operational stops and enough label maturity for quality claims.
- Pitfall
- Shadow requests must not duplicate real effects; early unlabeled traffic only establishes operational behavior.
- Check
- Exercise rollback with in-flight requests, verify model attribution and keep operational acceptance separate from delayed quality acceptance.
Situational decisions
When fallback cannot consume the new schema or features: Resolve that compatibility before describing rollback as available.
When the request is for local preparation or implementation: Prepare gates, shadow/canary configuration and recovery checks locally; require target identity and current evidence before promotion.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.