clear-eval 2.0.1__tar.gz → 2.0.2__tar.gz

clear_eval-2.0.2/PKG-INFO

@@ -0,0 +1,248 @@
+Metadata-Version: 2.4
+Name: clear_eval
+Version: 2.0.2
+Summary: A python API sdk facilitating Error Analysis via LLM-as-a-Judge
+Author-email: Lilach Eden <lilache@il.ibm.com>, Asaf Yehudai <asaf.yehudai@ibm.com>
+License: Apache-2.0
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: python-dotenv
+Requires-Dist: langchain
+Requires-Dist: langgraph
+Requires-Dist: langchain_openai
+Requires-Dist: langchain_ibm
+Requires-Dist: ibm_watsonx_ai>=1.3.42
+Requires-Dist: openai
+Requires-Dist: pyyaml
+Requires-Dist: pandas
+Requires-Dist: tqdm
+Requires-Dist: pyyaml
+Requires-Dist: streamlit
+Requires-Dist: matplotlib
+Requires-Dist: seaborn
+Requires-Dist: langchain_community
+Requires-Dist: numpy
+Requires-Dist: pyarrow>=22.0.0
+Requires-Dist: nest-asyncio
+Requires-Dist: nicegui>=3.7.1
+Requires-Dist: plotly
+Requires-Dist: networkx
+Requires-Dist: litellm>=1.83.0
+Requires-Dist: nest-asyncio
+Requires-Dist: scipy
+Requires-Dist: scikit-learn
+Requires-Dist: botocore
+Provides-Extra: tool-calls
+Requires-Dist: agent-lifecycle-toolkit; extra == "tool-calls"
+Dynamic: license-file
+
+# CLEAR: Comprehensive LLM Error Analysis and Reporting
+
+**CLEAR** is an open-source toolkit for **LLM error analysis** using an LLM-as-a-Judge approach.
+
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License](https://img.shields.io/badge/license-Apache%202.0-green.svg)](LICENSE)
+[![PyPI](https://img.shields.io/pypi/v/clear-eval.svg)](https://pypi.org/project/clear-eval/)
+
+---
+
+## What is CLEAR?
+
+CLEAR provides systematic error analysis for LLM-based systems. It combines automated LLM-as-a-judge evaluation with interactive dashboards to help you:
+- Identify recurring error patterns across your dataset
+- Quantify issue frequencies and severity
+- Drill down into specific failure cases
+- Prioritize improvements based on data-driven insights
+
+CLEAR operates in two phases:
+
+1. **Analysis** — Generates per-instance textual feedback, identifies system-level error categories, and quantifies their frequencies.
+2. **Interactive Dashboard** — Explore aggregate visualizations, apply dynamic filters, and drill down into individual failure examples.
+
+---
+
+## Two Analysis Modes
+
+### LLM Analysis
+
+Evaluate standard LLM outputs — generation quality, correctness, and recurring error patterns. Provide a CSV with prompts and responses, and CLEAR will score each instance, generate textual critiques, and surface system-level issues.
+
+- **Input:** CSV with model inputs and responses
+- **Output:** Per-record scores, evaluation text, aggregated issue categories
+- **Dashboard:** Streamlit-based interactive explorer
+
+> **[LLM Analysis Guide →](docs/llm-analysis.md)**
+
+### Agentic Analysis
+
+Evaluate multi-agent system trajectories — step-by-step agent interactions and full trajectory analysis.
+Supports traces from LangGraph, CrewAI, and other frameworks via MLflow or Langfuse.
+
+- **Input:** Raw JSON traces or preprocessed trajectory CSVs (each trace captures one complete agent task execution)
+- **Output:** Per-step CLEAR analysis, trajectory-level scores, rubric evaluations
+- **Dashboard:** NiceGUI-based workflow visualization with path and temporal analysis
+
+> **[Agentic Workflows Guide →](src/clear_eval/agentic/README.md)**
+
+---
+
+## Installation
+
+**Requires Python 3.10+**
+
+#### Option 1: pip
+
+```bash
+pip install clear-eval
+```
+
+#### Option 2: From source (for development)
+
+```bash
+git clone https://github.com/IBM/CLEAR.git
+cd CLEAR
+python3 -m venv .venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+pip install -e .
+```
+
+Verify the installation:
+
+```bash
+run-clear-eval-analysis --help
+```
+
+---
+
+## Quick Start
+
+### 1. Set your provider credentials
+
+CLEAR requires a supported LLM provider. Set the appropriate environment variables for your provider (e.g., `OPENAI_API_KEY` for OpenAI). Adjust `--provider` and `--eval-model-name` in the commands below to match your setup. See [Provider Configuration](#provider-configuration) for details.
+
+### 2. LLM Analysis
+
+This evaluates GSM8K math problem responses and surfaces recurring quality issues:
+
+```bash
+run-clear-eval-analysis --provider openai --eval-model-name gpt-4o
+```
+
+Results are saved to `results/gsm8k/sample_output/`. View them:
+
+```bash
+run-clear-eval-dashboard
+```
+
+> **[Full LLM Analysis Guide →](docs/llm-analysis.md)** — input formats, CLI arguments, configuration, Python API, and external judges.
+
+### 3. Agentic Analysis
+
+These two modes are independent — this section does not require step 2.
+
+Run CLEAR on sample agent traces (3 traces, each capturing one complete agent task execution, ~2 minutes):
+
+```bash
+run-clear-agentic-eval \
+    --data-dir src/clear_eval/sample_data/agentic/research_agent_traces/mlflow \
+    --results-dir my_smoke_test_results \
+    --from-raw-traces true \
+    --agent-framework langgraph \
+    --observability-framework mlflow \
+    --run-name smoke_test \
+    --max-files 3 \
+    --eval-model-name gpt-4o \
+    --provider openai
+```
+
+View pre-computed results (all 20 traces) without re-running:
+
+```bash
+run-clear-agentic-dashboard
+# Upload: src/clear_eval/sample_data/agentic/research_agent_results/mlflow/my_experiment/unified_ui_results.zip
+```
+
+> **[Full Agentic Guide →](src/clear_eval/agentic/README.md)** — trace generation, configuration, output structure, and dashboard features.
+
+---
+
+## Provider Configuration
+
+CLEAR uses [LiteLLM](https://docs.litellm.ai/docs/providers) as its inference backend, supporting 100+ LLM providers (OpenAI, Anthropic, WatsonX, AWS Bedrock, Google Vertex AI, and more).
+
+**Parameters:**
+
+| Parameter | CLI Flag | Description |
+|-----------|----------|-------------|
+| `provider` | `--provider` | LiteLLM provider name (e.g., `openai`, `anthropic`, `bedrock`, `vertex_ai`) |
+| `eval_model_name` | `--eval-model-name` | Model identifier (e.g., `gpt-4o`, `claude-3-5-sonnet-20241022`) |
+| `eval_model_params` | `--eval-model-params` | Additional model parameters as JSON (e.g., `{"temperature": 0}`) |
+| `endpoint_url` | `--endpoint-url` | Custom endpoint URL for local/self-hosted models |
+
+**Cloud provider example:**
+
+```bash
+export OPENAI_API_KEY="..."
+run-clear-eval-analysis --provider openai --eval-model-name gpt-4o
+```
+
+**Local model example (vLLM, llama.cpp, Ollama, etc.):**
+
+```bash
+run-clear-eval-analysis \
+    --provider openai \
+    --eval-model-name my-local-model \
+    --endpoint-url http://localhost:8000/v1
+```
+
+No credentials are needed when using `--endpoint-url` with a local server.
+
+Set the required environment variables for your provider according to [LiteLLM's documentation](https://docs.litellm.ai/docs/providers).
+
+---
+
+## Documentation
+
+| Guide | Description |
+|-------|-------------|
+| [**Agentic Workflows Guide**](src/clear_eval/agentic/README.md) | Multi-agent evaluation — trace preprocessing, step-by-step and trajectory analysis, configuration reference |
+| [**Agentic Dashboard Guide**](docs/agentic/dashboard.md) | Dashboard features — workflow view, node analysis, trajectory explorer, path and temporal analysis |
+| [**LLM Analysis Guide**](docs/llm-analysis.md) | Full pipeline reference — input formats, CLI arguments, configuration, and external judges |
+
+---
+
+## Citation
+
+If you use CLEAR in your research, please cite the relevant paper(s):
+
+**LLM Analysis** ([AAAI 2026](https://ojs.aaai.org/index.php/AAAI/article/view/42398)):
+```bibtex
+@inproceedings{yehudai2026clear,
+  title={CLEAR: Error analysis via llm-as-a-judge made easy},
+  author={Yehudai, Asaf and Eden, Lilach and Perlitz, Yotam and Bar-Haim, Roy and Shmueli-Scheuer, Michal},
+  booktitle={Proceedings of the AAAI Conference on Artificial Intelligence},
+  volume={40},
+  number={48},
+  pages={41736--41738},
+  year={2026}
+}
+```
+
+**Agentic Analysis** (ACL 2026, to appear — [preprint](https://arxiv.org/abs/2605.22608)):
+```bibtex
+@article{yehudai2026agentic,
+  title={Agentic CLEAR: Automating Multi-Level Evaluation of LLM Agents},
+  author={Yehudai, Asaf and Eden, Lilach and Shmueli-Scheuer, Michal},
+  journal={arXiv preprint arXiv:2605.22608},
+  year={2026}
+}
+```
+
+---
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE) for details.

clear_eval-2.0.2/README.md

@@ -0,0 +1,207 @@
+# CLEAR: Comprehensive LLM Error Analysis and Reporting
+
+**CLEAR** is an open-source toolkit for **LLM error analysis** using an LLM-as-a-Judge approach.
+
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License](https://img.shields.io/badge/license-Apache%202.0-green.svg)](LICENSE)
+[![PyPI](https://img.shields.io/pypi/v/clear-eval.svg)](https://pypi.org/project/clear-eval/)
+
+---
+
+## What is CLEAR?
+
+CLEAR provides systematic error analysis for LLM-based systems. It combines automated LLM-as-a-judge evaluation with interactive dashboards to help you:
+- Identify recurring error patterns across your dataset
+- Quantify issue frequencies and severity
+- Drill down into specific failure cases
+- Prioritize improvements based on data-driven insights
+
+CLEAR operates in two phases:
+
+1. **Analysis** — Generates per-instance textual feedback, identifies system-level error categories, and quantifies their frequencies.
+2. **Interactive Dashboard** — Explore aggregate visualizations, apply dynamic filters, and drill down into individual failure examples.
+
+---
+
+## Two Analysis Modes
+
+### LLM Analysis
+
+Evaluate standard LLM outputs — generation quality, correctness, and recurring error patterns. Provide a CSV with prompts and responses, and CLEAR will score each instance, generate textual critiques, and surface system-level issues.
+
+- **Input:** CSV with model inputs and responses
+- **Output:** Per-record scores, evaluation text, aggregated issue categories
+- **Dashboard:** Streamlit-based interactive explorer
+
+> **[LLM Analysis Guide →](docs/llm-analysis.md)**
+
+### Agentic Analysis
+
+Evaluate multi-agent system trajectories — step-by-step agent interactions and full trajectory analysis.
+Supports traces from LangGraph, CrewAI, and other frameworks via MLflow or Langfuse.
+
+- **Input:** Raw JSON traces or preprocessed trajectory CSVs (each trace captures one complete agent task execution)
+- **Output:** Per-step CLEAR analysis, trajectory-level scores, rubric evaluations
+- **Dashboard:** NiceGUI-based workflow visualization with path and temporal analysis
+
+> **[Agentic Workflows Guide →](src/clear_eval/agentic/README.md)**
+
+---
+
+## Installation
+
+**Requires Python 3.10+**
+
+#### Option 1: pip
+
+```bash
+pip install clear-eval
+```
+
+#### Option 2: From source (for development)
+
+```bash
+git clone https://github.com/IBM/CLEAR.git
+cd CLEAR
+python3 -m venv .venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+pip install -e .
+```
+
+Verify the installation:
+
+```bash
+run-clear-eval-analysis --help
+```
+
+---
+
+## Quick Start
+
+### 1. Set your provider credentials
+
+CLEAR requires a supported LLM provider. Set the appropriate environment variables for your provider (e.g., `OPENAI_API_KEY` for OpenAI). Adjust `--provider` and `--eval-model-name` in the commands below to match your setup. See [Provider Configuration](#provider-configuration) for details.
+
+### 2. LLM Analysis
+
+This evaluates GSM8K math problem responses and surfaces recurring quality issues:
+
+```bash
+run-clear-eval-analysis --provider openai --eval-model-name gpt-4o
+```
+
+Results are saved to `results/gsm8k/sample_output/`. View them:
+
+```bash
+run-clear-eval-dashboard
+```
+
+> **[Full LLM Analysis Guide →](docs/llm-analysis.md)** — input formats, CLI arguments, configuration, Python API, and external judges.
+
+### 3. Agentic Analysis
+
+These two modes are independent — this section does not require step 2.
+
+Run CLEAR on sample agent traces (3 traces, each capturing one complete agent task execution, ~2 minutes):
+
+```bash
+run-clear-agentic-eval \
+    --data-dir src/clear_eval/sample_data/agentic/research_agent_traces/mlflow \
+    --results-dir my_smoke_test_results \
+    --from-raw-traces true \
+    --agent-framework langgraph \
+    --observability-framework mlflow \
+    --run-name smoke_test \
+    --max-files 3 \
+    --eval-model-name gpt-4o \
+    --provider openai
+```
+
+View pre-computed results (all 20 traces) without re-running:
+
+```bash
+run-clear-agentic-dashboard
+# Upload: src/clear_eval/sample_data/agentic/research_agent_results/mlflow/my_experiment/unified_ui_results.zip
+```
+
+> **[Full Agentic Guide →](src/clear_eval/agentic/README.md)** — trace generation, configuration, output structure, and dashboard features.
+
+---
+
+## Provider Configuration
+
+CLEAR uses [LiteLLM](https://docs.litellm.ai/docs/providers) as its inference backend, supporting 100+ LLM providers (OpenAI, Anthropic, WatsonX, AWS Bedrock, Google Vertex AI, and more).
+
+**Parameters:**
+
+| Parameter | CLI Flag | Description |
+|-----------|----------|-------------|
+| `provider` | `--provider` | LiteLLM provider name (e.g., `openai`, `anthropic`, `bedrock`, `vertex_ai`) |
+| `eval_model_name` | `--eval-model-name` | Model identifier (e.g., `gpt-4o`, `claude-3-5-sonnet-20241022`) |
+| `eval_model_params` | `--eval-model-params` | Additional model parameters as JSON (e.g., `{"temperature": 0}`) |
+| `endpoint_url` | `--endpoint-url` | Custom endpoint URL for local/self-hosted models |
+
+**Cloud provider example:**
+
+```bash
+export OPENAI_API_KEY="..."
+run-clear-eval-analysis --provider openai --eval-model-name gpt-4o
+```
+
+**Local model example (vLLM, llama.cpp, Ollama, etc.):**
+
+```bash
+run-clear-eval-analysis \
+    --provider openai \
+    --eval-model-name my-local-model \
+    --endpoint-url http://localhost:8000/v1
+```
+
+No credentials are needed when using `--endpoint-url` with a local server.
+
+Set the required environment variables for your provider according to [LiteLLM's documentation](https://docs.litellm.ai/docs/providers).
+
+---
+
+## Documentation
+
+| Guide | Description |
+|-------|-------------|
+| [**Agentic Workflows Guide**](src/clear_eval/agentic/README.md) | Multi-agent evaluation — trace preprocessing, step-by-step and trajectory analysis, configuration reference |
+| [**Agentic Dashboard Guide**](docs/agentic/dashboard.md) | Dashboard features — workflow view, node analysis, trajectory explorer, path and temporal analysis |
+| [**LLM Analysis Guide**](docs/llm-analysis.md) | Full pipeline reference — input formats, CLI arguments, configuration, and external judges |
+
+---
+
+## Citation
+
+If you use CLEAR in your research, please cite the relevant paper(s):
+
+**LLM Analysis** ([AAAI 2026](https://ojs.aaai.org/index.php/AAAI/article/view/42398)):
+```bibtex
+@inproceedings{yehudai2026clear,
+  title={CLEAR: Error analysis via llm-as-a-judge made easy},
+  author={Yehudai, Asaf and Eden, Lilach and Perlitz, Yotam and Bar-Haim, Roy and Shmueli-Scheuer, Michal},
+  booktitle={Proceedings of the AAAI Conference on Artificial Intelligence},
+  volume={40},
+  number={48},
+  pages={41736--41738},
+  year={2026}
+}
+```
+
+**Agentic Analysis** (ACL 2026, to appear — [preprint](https://arxiv.org/abs/2605.22608)):
+```bibtex
+@article{yehudai2026agentic,
+  title={Agentic CLEAR: Automating Multi-Level Evaluation of LLM Agents},
+  author={Yehudai, Asaf and Eden, Lilach and Shmueli-Scheuer, Michal},
+  journal={arXiv preprint arXiv:2605.22608},
+  year={2026}
+}
+```
+
+---
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE) for details.

{clear_eval-2.0.1 → clear_eval-2.0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "clear_eval"
-version = "2.0.1"
+version = "2.0.2"
 description = "A python API sdk facilitating Error Analysis via LLM-as-a-Judge"
 readme = "README.md"
 authors = [{ name = "Lilach Eden", email = "lilache@il.ibm.com"},

{clear_eval-2.0.1 → clear_eval-2.0.2}/src/clear_eval/agentic/dashboard/launch_dashboard.py

@@ -9,6 +9,18 @@ import sys
 from pathlib import Path
 
 
+def _is_port_available(host: str, port: int) -> bool:
+    """Check if a port is available for binding."""
+    import socket
+    try:
+        with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:
+            s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
+            s.bind((host, port))
+            return True
+    except OSError:
+        return False
+
+
 def main():
     parser = argparse.ArgumentParser(description="Launch the Agentic Workflow Dashboard")
     parser.add_argument("--port", type=int, default=8080, help="Port to run the dashboard on (default: 8080)")
@@ -16,6 +28,12 @@ def main():
     parser.add_argument("--no-open", action="store_true", help="Don't auto-open browser")
     args = parser.parse_args()
 
+    if not _is_port_available(args.host, args.port):
+        print(f"Error: Port {args.port} is already in use.")
+        print(f"Either stop the process using port {args.port}, or use a different port:")
+        print(f"  run-clear-agentic-dashboard --port {args.port + 1}")
+        sys.exit(1)
+
     # Ensure the server shuts down cleanly on termination signals,
     # so the port is released immediately instead of staying in TIME_WAIT.
     def _handle_signal(signum, frame):

{clear_eval-2.0.1 → clear_eval-2.0.2}/src/clear_eval/agentic/pipeline/full_traces_evaluation/run_trajectory_evaluation_pipeline.py

@@ -690,7 +690,6 @@ def main():
     validate_required_config(config, ['data_dir', 'results_dir'], parser)
 
     # Get run output directory
-    user_provided_run_name = config.get('run_name') is not None
     output_dir, run_name = get_run_output_dir(
         config['results_dir'],
         config.get('run_name')
@@ -708,14 +707,10 @@ def main():
         logger.error(f"Input directory does not exist: {traj_input_dir}")
         sys.exit(1)
 
-    # Validate run directory state
-    if output_dir.exists() and user_provided_run_name:
-        if config.get('overwrite', True):
-            logger.error(
-                f"Output directory already exists: {output_dir}\n"
-                f"Use --overwrite false to resume, or delete the existing directory."
-            )
-            sys.exit(1)
+    # Log if output dir already exists
+    if output_dir.exists():
+        if config.get('overwrite', False):
+            logger.info(f"Re-running existing run with overwrite: {run_name}")
         else:
             logger.info(f"Resuming existing run: {run_name}")
 

{clear_eval-2.0.1 → clear_eval-2.0.2}/src/clear_eval/agentic/pipeline/run_clear_agentic_eval.py

@@ -148,17 +148,20 @@ def prepare_traces_data(
     else:
         traces_data_dir = output_paths['base'] / 'traces_data'
     
+    overwrite = config.get('overwrite', False)
+
     if from_raw_traces:
-        # Process raw JSON traces
+        # Process raw JSON traces — always runs; skips individual CSVs that
+        # already exist when overwrite=false (handles interrupted runs)
         logger.info(f"Preprocessing raw traces from: {data_dir}")
-        
+
         try:
             process_traces_to_traj_data(
                 input_dir=str(data_dir),
                 output_dir=str(traces_data_dir),
                 agent_framework=config.get('agent_framework'),
                 observability_framework=config.get('observability_framework'),
-                overwrite=config.get('overwrite', True),
+                overwrite=overwrite,
             )
             logger.info(f"✓ Traces preprocessed")
             return traces_data_dir
@@ -167,8 +170,14 @@ def prepare_traces_data(
             return None
     else:
         # Copy existing CSV files
-        logger.info(f"Using trajectory CSVs from: {data_dir}")
-
+        # If not overwriting and traces_data already has CSVs, reuse as-is
+        if not overwrite and traces_data_dir.exists():
+            csv_count = len(list(traces_data_dir.glob('*.csv')))
+            if csv_count > 0:
+                logger.info(f"Reusing existing traces_data ({csv_count} CSVs)")
+                return traces_data_dir
+
+        logger.info(f"Copying trajectory CSVs from: {data_dir}")
         try:
             if traces_data_dir.exists():
                 shutil.rmtree(traces_data_dir)
@@ -325,20 +334,16 @@ def main():
     # Extract parameters
     data_dir = Path(config['data_dir'])
     from_raw_traces = config.get('from_raw_traces')
-    overwrite = config.get('overwrite', True)
-    user_provided_run_name = config.get('run_name') is not None
 
     # Validate input directory exists
     if not data_dir.exists():
         parser.error(f"Input directory does not exist: {data_dir}")
 
-    # Validate run directory state
-    if output_dir.exists() and user_provided_run_name:
+    # Log if output dir already exists
+    if output_dir.exists():
+        overwrite = config.get('overwrite', False)
         if overwrite:
-            parser.error(
-                f"Output directory already exists: {output_dir}\n"
-                f"Use --overwrite false to resume, or delete the existing directory."
-            )
+            logger.info(f"Re-running existing run with overwrite: {run_name}")
         else:
             logger.info(f"Resuming existing run: {run_name}")
     

{clear_eval-2.0.1 → clear_eval-2.0.2}/src/clear_eval/agentic/pipeline/run_clear_step_analysis.py

@@ -642,7 +642,6 @@ Argument Precedence (lowest to highest):
     validate_required_config(config_dict, ['data_dir', 'results_dir'], parser)
 
     # Get run output directory
-    user_provided_run_name = config_dict.get('run_name') is not None
     results_dir, run_name = get_run_output_dir(
         config_dict['results_dir'],
         config_dict.get('run_name')
@@ -655,16 +654,13 @@ Argument Precedence (lowest to highest):
     # Extract parameters
     from_raw_traces = config_dict.get('from_raw_traces')
     data_dir = config_dict['data_dir']
-    overwrite = config_dict.get('overwrite', True)
+    overwrite = config_dict.get('overwrite', False)
     memory_only = config_dict.get('memory_only')
 
-    # Validate run directory state
-    if results_dir.exists() and user_provided_run_name:
+    # Log if output dir already exists
+    if results_dir.exists():
         if overwrite:
-            parser.error(
-                f"Output directory already exists: {results_dir}\n"
-                f"Use --overwrite false to resume, or delete the existing directory."
-            )
+            logger.info(f"Re-running existing run with overwrite: {run_name}")
         else:
             logger.info(f"Resuming existing run: {run_name}")
 

{clear_eval-2.0.1 → clear_eval-2.0.2}/src/clear_eval/agentic/pipeline/setup/default_agentic_config.yaml

@@ -25,7 +25,7 @@ separate_tools: false
 max_files: null                 # Maximum number of files to evaluate (null = all)
 
 # Execution
-overwrite: true                 # If true: requires fresh run_name (fails if exists). If false: resume mode.
+overwrite: false                # If true: re-run steps even if outputs exist. If false: skip completed steps.
 max_workers: 10                 # Number of parallel workers
 run_name: null                  # Unique identifier for this run (used in output path)