Rig Lifecycle

The family of operations that create, start, stop, resume, restore, snapshot, release, unclaim, and destroy OpenRig-managed topologies. Includes the user story after reboot: "bring my work back without turning a clean recovery into a cleanup project."

If lifecycle is brittle, every higher-level primitive inherits that brittleness. Queue, workflow, seat continuity, cross-host operation, and RSI all assume that rigs and seats can be restored into known states.

Use this when

• Operating rig up / down / restore / resume / snapshot / release / unclaim / destroy
• Reading rig ps after a reboot or recovery and deciding what to trust
• Designing proof for a lifecycle scenario (clean start / warm resume / host reboot / provider auth loss / partial boot / operator recovery)
• Reasoning about restore-outcome semantics (resumed / rebuilt / fresh / failed / attention_required)
• Auditing whether a lifecycle proof is in-process bedrock vs requires real reboot evidence

Don't use this when

• The operation is single-command and deterministic, use openrig-user skill for CLI surface
• The work is operator-level configuration or troubleshooting of OpenRig itself, run rig context get help
• The work is rig spec authoring, use openrig-architect

Failure modes (4)