feat(perception): stabilize pre-capture methodology

docs/15_LABORATORY_RUN_CANON.md

@@ -32,12 +32,24 @@ candidate is accepted:
 
 - new perception and product iterations use RAVNOVES00;
 - each iteration creates a new immutable LAB and never rewrites an older one;
-- TEST007, E36 and new physical collection are deferred, not required gates;
+- TEST007 and E36 replay are deferred, not required current gates;
 - no agent may initiate or imply a new capture without explicit operator
   authorization;
 - the active quality target is at least `90%` on each frozen task-level
   validation dimension, never one unqualified aggregate accuracy number.
 
+ADR 0032 corrects the present validation meaning. E37's 146-row slice is
+historical evaluated visible engineering validation: its labels are not
+independent truth and its development/evaluation groups overlap. It remains an
+immutable comparison contract, but it cannot close a blind accuracy gate.
+Prediction packages must exclude truth, split, severity and scoring material,
+and evaluation must join those artifacts only after prediction.
+
+The owner has authorized preparation for a later same-K1/new-route recording,
+not agent-initiated collection. E43 freezes that future protocol before data
+exists. Until the recording is supplied, no LAB result, metric or transfer
+claim is created for it.
+
 This policy is a development priority, not a universality claim. Later
 second-source transfer remains required before any cross-route or cross-camera
 generalization statement.