refactor(platform): bound lab canon and contour identity

2026-08-05 12:00:27 +03:00
parent de12e96297
commit 6d0abbc569
10 changed files with 199 additions and 8 deletions
@@ -216,6 +216,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.

+## Lifecycle classes and bounded canonicalization
+
+ADR 0039 separates the value of laboratory evidence from the maturity of its
+execution architecture:
+
+- `canonical` is the ordinary reusable path through versioned source, provider,
+  graph and run contracts;
+- `experimental` is an admitted bounded adapter or package for a novel stack or
+  method which the current graph cannot honestly express;
+- `legacy` is immutable historical evidence retained through its existing
+  validator/projector without retroactive provenance.
+
+An experimental LAB is not rejected merely because it does not fit the current
+canonical stack. It still must retain real source/configuration/runtime/artifact
+identities, visual evidence, terminal outcome, limitations and forbidden
+authority. It may not silently become a core dependency. Promotion occurs only
+after repeated value justifies a reusable provider or graph contract.
+
+Mission Core does not bulk-migrate the archive. E33, E35 and E46J are the bounded
+execution canaries. Once they prove one automatic run-to-evidence path, the LAB
+canonicalization slice closes and remaining historical work stays `legacy` unless
+an integrity or product need justifies a targeted migration.
+
 ## Planning discipline

 A planned LAB number is not a placeholder page. Before execution it must name: