refactor(platform): bound lab canon and contour identity

docs/18_APPLICATION_COMPONENT_ARCHITECTURE.md

@@ -179,6 +179,15 @@ Legacy/integrated diagnostic viewers may keep a result interaction inside the
 evidence slot only where that viewer is already the admitted result instrument.
 This exception does not apply automatically to a new LAB.
 
+ADR 0039 adds a lifecycle distinction to this code shape. A `canonical` LAB
+enters through the reusable registry and must not add another experiment-named
+branch to `App.tsx`, the generic workspace or the advanced dispatcher. An
+`experimental` LAB may have a bounded adapter or renderer when the current graph
+cannot express its evidence, but the adapter remains feature-local, declares its
+classification and cannot change generic product behavior. A `legacy` LAB keeps
+its existing read-only projector and is not rewritten solely to satisfy the
+latest code shape.
+
 ## Local ontology decision
 
 Mission Core already has three semantic mechanisms:
@@ -216,6 +225,11 @@ vocabulary and executable contracts. They do not create a second runtime model.
 `test/laboratoryProductUi.test.mjs` additionally enforces the versioned LAB
 report fields and shared result component across bounded LAB modules.
 
+The next executable laboratory architecture gate extends these tests to reject
+new unclassified experiment branches while allowing a declared bounded
+experimental adapter. The gate protects core composition; it does not forbid a
+novel research stack.
+
 The line limits are ratchets, not quality targets. When a file reaches a limit,
 split a feature; do not raise the limit to accommodate unrelated behavior.