# 📑 Metadata Files Generated by Executions

Each method execution in CCP produces a consistent set of **metadata files**.  
These support traceability, reproducibility, and alignment with the **FAIR principles**.

This page summarizes their role and content.

---

## 📁 Metadata Summary

The metadata files are grouped into three main areas:

---

### 🔧 Method Definition

| File                    | Description |
|-------------------------|-------------|
| `metadata_method.json`  | Method definition: inputs, outputs, docker image, parameters |
| `metadata_request.json` | Specific values used in this execution (e.g., file paths, parameters) |

---

### 🖥️ Execution Process

| File                        | Description |
|-----------------------------|-------------|
| `metadata_jobStatus.json`   | Current status (`running`, `successful`, etc.), timestamps, messages |
| `metadata_infrastructure.json` | Infrastructure used for execution |
| `auth_jwt.json`             | Token used by the user (opaque, for audit only) |

---

### 🧬 Provenance

| File                | Description |
|---------------------|-------------|
| `metadata_provo.xml`| Semantic trace of execution using W3C PROV-O vocabulary |

For details, see 📜 [Execution provenance (PROV-O)](./05_metadata_provo)

---

## 🧠 Why These Matter

These files enable:

- **Reproducibility**: knowing exactly how a result was generated
- **Validation**: confirming the configuration used at runtime
- **Debugging**: identifying failures or inconsistencies
- **Traceability**: supporting FAIR data principles and long-term reuse

---

## 🔗 Related Pages

- ⏯️ [ Understanding Executions](./01_executions)

- 📂 [Execution Outputs and Logs](./02_outputs_and_logs)

- 🌀 [Execution Status and Lifecycle](./03_execution_status)

- 📜 [Execution provenance (PROV-O)](./05_metadata_provo)