feat(observatory): ship modular AI inference labs

docs/18_APPLICATION_COMPONENT_ARCHITECTURE.md

@@ -227,9 +227,13 @@ Mission Core already has three semantic mechanisms:
 3. `docs/domain-model/mission-core-experimental-vocabulary-v0alpha2.md` for
    meanings that are not yet stable enough for Platform Ontology.
 
-These mechanisms are sufficient before A3. A new RDF/graph store, ontology
-service, or parallel entity catalog would introduce duplicated identity and
-migration work without a current query or integration consumer.
+These mechanisms were sufficient before A3. Observatory modular compositions
+crossed the gate on 2026-09-04: planning, Worker dispatch, LAB publication and
+replay presentation require the same module/composition/result/layer relations,
+and typed single-result traversal lost the TGS member of a composed run. The
+bounded local package is defined by
+`docs/domain-model/observatory-domain-ontology-v1.md`. It keeps identity in the
+existing stores and has no Platform Ontology runtime dependency.
 
 A formal local runtime ontology is introduced only when:
 
@@ -239,8 +243,10 @@ A formal local runtime ontology is introduced only when:
 - the graph answers named queries used by the product or automation;
 - promotion or synchronization with NODE.DC Platform Ontology is defined.
 
-Until those conditions hold, new stable meanings extend the versioned local
-vocabulary and executable contracts. They do not create a second runtime model.
+Other domains continue to extend the versioned local vocabulary and executable
+contracts until they independently satisfy these conditions. The admitted
+Observatory package projects existing store identities and cannot become a
+second authority for them.
 
 ## Automated boundary gate