Rename batch/continuous mode to better reflect interactive nature

[jguice]

Description

The current terminology of "batch" and "continuous" mode is misleading. "Continuous" implies a non-interactive mode, but it is actually an interactive mode.

Problem

• "Continuous mode" suggests automated, hands-off operation
• In reality, continuous mode is interactive and requires user engagement
• This causes confusion about what each mode actually does

Proposed Solution

Find better terminology that accurately reflects:

• Batch mode: processes multiple items in one go
• The interactive mode: requires user interaction/feedback during execution

Suggestions welcome for alternative naming conventions.

[jguice]

@claude can you suggest some wording options.

[claude]

Claude finished @jguice's task —— View job

---

Suggested Wording Options

After analyzing the codebase (see prompts/SDD-3-manage-tasks.md:62-77), I understand the current modes control checkpoint frequency during task implementation. Here are my suggestions:

---

Option 1: Checkpoint-Based Naming (Recommended)

Clear, descriptive, and focuses on the actual behavior

• Sub-task Checkpoint Mode (currently "Continuous")

  • Pauses after each sub-task (1.1, 1.2, 1.3)
  • Interactive: requires user confirmation to continue

• Task Checkpoint Mode (currently "Task Mode")

  • Pauses after each parent task (1.0, 2.0, 3.0)
  • Interactive: requires user confirmation to continue

• Completion Checkpoint Mode (currently "Batch")

  • Pauses only after all tasks complete
  • Less interactive: maximum automation

Rationale: "Checkpoint" clearly indicates pausing for user input. The modifier (sub-task/task/completion) explains exactly when that happens.

---

Option 2: Granularity-Based Naming

Emphasizes the level of control

• Fine-Grained Mode (currently "Continuous")
• Standard Mode (currently "Task Mode")
• Coarse-Grained Mode (currently "Batch")

Rationale: Describes the granularity of interaction without implying continuous/automated operation.

---

Option 3: Interaction Frequency Naming

Focuses on how often the user engages

• Frequent Interaction Mode (currently "Continuous")
• Balanced Interaction Mode (currently "Task Mode")
• Minimal Interaction Mode (currently "Batch")

Rationale: Makes it explicit that all modes involve interaction, just at different frequencies.

---

Option 4: Pause Point Naming

Most literal description of behavior

• Pause per Sub-task (currently "Continuous")
• Pause per Task (currently "Task Mode")
• Pause at End (currently "Batch")

Rationale: Direct, unambiguous description of when execution pauses for user input.

---

Option 5: Control Level Naming

Emphasizes user oversight

• High-Control Mode (currently "Continuous")
• Standard-Control Mode (currently "Task Mode")
• Low-Control Mode (currently "Batch")

Rationale: Focuses on how much control/oversight the user maintains during execution.

---

My Recommendation

Option 1 (Checkpoint-Based) is the clearest because:

1. "Checkpoint" immediately communicates "pause for user input"
2. The modifiers (sub-task/task/completion) precisely describe when
3. Avoids confusion with automation terms like "continuous" or "batch"
4. Self-documenting: users can infer behavior from the name alone

Alternative: If you want shorter names, Option 4 (Pause Point) is the most straightforward and literal.

Would you like me to implement one of these naming changes across the codebase?

---

Job Run | Branch