docs(lab): plan the post-E29 research cycle

2026-07-26 18:24:59 +03:00
parent f50405d907
commit 2ffaf94052
2 changed files with 55 additions and 0 deletions
@@ -157,6 +157,29 @@ A LAB run may be shown as diagnostic evidence with `legacy-partial` method
 metadata. It may be called reproducible or promoted only when the method is
 `complete` and its experiment-specific acceptance gates pass.

+## Planning discipline
+
+A planned LAB number is not a placeholder page. Before execution it must name:
+
+1. one decision question or falsifiable hypothesis;
+2. the exact immutable source and admitted derivative inputs;
+3. the method identities and the one configuration allowed to vary;
+4. the required visual evidence;
+5. measurements, exclusions and predeclared thresholds;
+6. the exit decision and the authority that remains forbidden.
+
+After execution, the planned definition is retained in the immutable result.
+Changing the source, algorithm, model weights, preprocessing, thresholds or
+runtime creates a new LAB run. A failed or blocked experiment remains useful
+only when its missing evidence and failure reason are explicit; an empty
+viewer or invented metric is never a laboratory result.
+
+The accepted E30–E36 camera-first/K1 research sequence is maintained in
+`docs/13_LIDAR_WORKER_PRODUCT_AND_ROADMAP.md`. It deliberately starts with the
+E29 disagreement audit and recorded evidence already available in Mission
+Core. It does not require a connected K1 or new data collection before the
+existing recording has exhausted its admitted questions.
+
 ## Storage and Git

 Raw captures, model weights, generated RRD, videos and large derived arrays stay