added empty chapter for structure

Chapters/Methodology.tex

@@ -510,17 +510,64 @@ benchmark directories. This prevents cross-contamination between tests.
 
 \subsection{Data Provenance}
 
-Every test result includes metadata recording:
+Results are organized in the four-level directory hierarchy shown in
+Figure~\ref{fig:result-tree}. Each VPN directory stores a
+\texttt{layout.json} capturing the machine topology used for that run.
+Each impairment profile directory records the exact \texttt{tc}
+parameters in \texttt{tc\_settings.json} and per-phase durations in
+\texttt{timing\_breakdown.json}. Individual benchmark results are
+stored in one subdirectory per machine pair.
 
-\begin{itemize}
-  \item Wall-clock duration
-  \item Number of attempts (1 = first try succeeded)
-  \item VPN restart attempts and duration
-  \item Connectivity wait duration
-  \item Source and target machine names
-  \item Service logs (on failure)
-\end{itemize}
+\begin{figure}[ht]
+  \centering
+  \begin{forest}
+    for tree={
+      font=\ttfamily\small,
+      grow'=0,
+      folder,
+      s sep=2pt,
+      inner xsep=3pt,
+      inner ysep=2pt,
+    }
+    [date/
+      [vpn/
+        [layout.json]
+        [profile/
+          [tc\_settings.json]
+          [timing\_breakdown.json]
+          [parallel\_tcp\_iperf3.json]
+          [\textnormal{\textit{\{pos\}\_\{peer\}}}/
+            [ping.json]
+            [tcp\_iperf3.json]
+            [udp\_iperf3.json]
+            [qperf.json]
+            [rist\_stream.json]
+            [nix\_cache.json]
+            [connection\_timings.json]
+          ]
+        ]
+      ]
+      [General/
+        [hardware.json]
+        [comparison/
+          [cross\_profile\_*.json]
+          [profile/
+            [benchmark\_stats.json]
+            [per-benchmark .json files]
+          ]
+        ]
+      ]
+    ]
+  \end{forest}
+  \caption{Directory hierarchy of benchmark results. Each run produces
+    per-VPN and per-profile directories alongside a \texttt{General/}
+  directory with cross-VPN comparison data.}
+  \label{fig:result-tree}
+\end{figure}
 
-Results are organized hierarchically by VPN, TC profile, and machine
-pair. Each profile directory contains a \texttt{tc\_settings.json}
-snapshot of the exact impairment parameters applied.
+Every benchmark result file uses a uniform JSON envelope with a
+\texttt{status} field, a \texttt{data} object holding the
+test-specific payload, and a \texttt{meta} object recording
+wall-clock duration, number of attempts, VPN restart count and
+duration, connectivity wait time, source and target machine names,
+and on failure, the relevant service logs.