Record analysis and Scenario version integration requirements

2026-09-12 22:00:33 -07:00
parent 29525d7823
commit 13f7e6b0d1
4 changed files with 224 additions and 0 deletions
@@ -426,3 +426,19 @@ that has not found a feasible candidate. Pure inverse-geometry experiments and
 native port/handle arbitration remain prerequisites for accepting production
 interaction. Process/scenario authored layouts retain their separate persistence
 dependency; the persisted-rectangle slice does not complete that broader need.
+
+## Pending analysis/Scenario version composition — 2026-09-13
+
+The isolated schema8 analysis and Scenario layout contributions must share explicit
+version and resource boundaries before adoption. The [source audit](scenario-analysis-version-integration-review-20260913.md)
+pins analysis6216cff and Scenarioaed07176; it does not establish combined execution.
+Older JSON/source versions must reject the new Diagram layout field by presence,
+including null, while retaining legal schema7 fields. Typed migration entrances
+must also reject a current-only payload rather than discard it. Count all stored
+layout rows and explicit address references together with existing model/analysis
+usage; visibility does not exempt stored data. Run both analysis and Scenario
+remap collision checks before any identity/reference mutation. Preserve distinct
+Scenario row, global definition, scoped parameter and call-site edit identities.
+The audit specifies failure cases and compatible implementation seams. Public
+source8, resource calibration, combined save/reopen and interaction acceptance
+remain separate requirements; neither isolated suite establishes their completion.