Workflow State Management

Batuta tracks progress through its 5-phase pipeline in a JSON state file. This allows you to resume from the last successful phase after an interruption or failure.

State File

Pipeline state is persisted to .batuta-state.json in the current working directory. The file is created automatically when the first pipeline command runs.

{
  "current_phase": "Transpilation",
  "phases": {
    "Analysis": { "status": "Completed", "started_at": "...", "completed_at": "..." },
    "Transpilation": { "status": "InProgress", "started_at": "..." },
    "Optimization": { "status": "NotStarted" },
    "Validation": { "status": "NotStarted" },
    "Deployment": { "status": "NotStarted" }
  }
}

Phase Tracking

Each phase has one of four statuses:

Batuta records started_at and completed_at timestamps for every transition.

Viewing Status

Use batuta status to display phase statuses, timestamps, durations, and the recommended next step.

batuta status

Resuming from a Failed Phase

If a phase fails, Batuta records the error and stops (Jidoka principle). Fix the issue, then re-run the same command. Completed phases are not repeated.

# Phase 2 failed -- fix the source, then re-run
batuta transpile

Reset and Clean

To discard all progress and start from scratch:

batuta reset         # Interactive confirmation
batuta reset --yes   # Skip confirmation

The reset command deletes .batuta-state.json but does not remove generated source code. To remove both:

batuta reset --yes
rm -rf ./rust-output

Progress Percentage

Progress is the fraction of phases with Completed status, displayed by batuta status.

Navigate: Table of Contents