Recover an interrupted revision

Recovery resolves an interrupted revision. It uses the recorded transaction and its original approval.

Keep your project out of iCloud Drive folders. Project commands such as bowerloom up, ls, status, apply, and skills sync refuse a project under ~/Documents or ~/Desktop when Desktop and Documents sync is on, and under the ~/Library cloud folders, with PROJECT_IN_CLOUD_FOLDER. The older forms that take an explicit path do not run this check. This beta reads skills only from public sources. See the beta limits.

Ask your agent

Help me understand this interrupted Bowerloom revision. Preserve the transaction records and show the supported resume or rollback choice before acting.

Agent procedure

Prerequisites

Install the matching CLI version through Install Bowerloom.

Use the exact original project and retained transaction records. Obtain the original recorded revision-plan approval.

If the original approval or transaction cannot be established, stop. Preserve the marker, stage, backup, receipt, and history.

Inspect the pending state

Replace the target with the interrupted project's absolute path.

bowerloom init status --target /absolute/projects/clean-install-trial

revision-pending is not a ready setup. Inspect the recorded transaction before choosing an action.

Choose one action

Explain the supported choice to the human. Use the original approved transaction revision for EXACT_REVISION_PLAN.

If the selected action is resume, use:

bowerloom revise recover --target /absolute/projects/clean-install-trial --approve EXACT_REVISION_PLAN --action resume

If the selected action is rollback, use:

bowerloom revise recover --target /absolute/projects/clean-install-trial --approve EXACT_REVISION_PLAN --action rollback

Resume continues the recorded approved transaction. Rollback restores its recorded prior installation.

Inspect the resolved state

bowerloom init status --target /absolute/projects/clean-install-trial

Report the actual transaction outcome and readiness fields. Recovery starts no workers and grants no cleanup authority.

If recovery refuses

Preserve journals and identity fields. Do not adopt a replacement directory or repeatedly call fresh installation.

There is no generic init recover command. If an I/O outcome stays uncertain, inspect retained state before further action.

Revision guide · Troubleshooting · Status reference