Run
Create VMConnect a wallet, choose a machine, and create a virtual machine in the console.Bench workspaceOpen the injector coding workspace after you install a machine in Console.Diesel injector codingCoding and calibration workflows across live injector families.
Documentation
Documentation
Last reviewed:
Intent
Release governance is designed to protect workshop continuity while enabling platform evolution. Every release should be auditable, reversible, and communicated with clear operator expectations.
Release Channels
| Channel | Audience | Cadence | Rollback Posture |
|---|---|---|---|
| Canary | Internal operators and test partners only. | On-demand during validation windows. | Immediate rollback allowed on first critical regression. |
| Staged | Selected production tenants with controlled blast radius. | Weekly release windows with approval gates. | Rollback within change window if KPI or stability thresholds are missed. |
| General Availability | All production tenants and workshop operators. | Regular cadence after staged sign-off. | Rollback or hotfix based on incident severity and operational risk. |
Change Window Checklist
- Confirm release note scope, user impact, and migration requirements.
- Validate deterministic behavior across representative injector families.
- Verify payment/settlement traces and machine lifecycle integrity.
- Define rollback criteria and assign decision owner before deployment begins.
- Publish communication notice with expected window and support coverage.
Rollback Rules
Trigger rollback when release behavior threatens coding reliability, session integrity, or settlement trace consistency. Rollback decisions should be logged with explicit reasons, timestamp, owner, and customer-impact summary.
Communication Cadence
- Pre-release notice: at least one business day before staged or GA deployment.
- In-window updates: post status when rollout reaches each major milestone.
- Post-release summary: include impact, known limitations, and follow-up actions.