Record reviewed mixed syntax boundary and preserve Scenario contracts

2026-09-23 01:06:34 -07:00
parent 195ddbbba5
commit f9c5165cb9
6 changed files with 458 additions and 0 deletions
@@ -1,5 +1,31 @@
 # Architectural and product decisions

+## Private mixed syntax boundary — 2026-09-23
+
+Proceed with the [reviewed syntax-only slice](analysis-mixed-parser-review-20260923.md)
+on tested private source `10d7f334`, retaining current root `195ddbb` as an
+ordinary-compatibility reference. Direct comparison found the relevant ordinary
+syntax/include machinery equal or equivalent; whole-file drift chiefly concerns
+semantic/editor behavior. A full root merge is not a prerequisite for this
+private experiment, and neither whole language/updater file may replace the
+other during eventual integration.
+
+One opaque complete-bundle result borrows the actual original files and owns
+the shared budget, canonical file table, ordinary occurrence positions and typed
+unresolved syntax. It supplies no admitted Project, Index or edit authority.
+Explicit IDs are a staging restriction; missing IDs reject before generation.
+Retain duplicate syntax occurrences until semantic uniqueness is checked.
+Ordinary signed numbers require byte adjacency and complete value spans;
+typed subtraction retains its separate grammar. Bound aggregate syntax storage
+without silently reinterpreting caller model-record or ordered-step limits.
+Propagate phase-check failures even where the Budget does not latch them.
+
+The [proposal](analysis-mixed-parser-proposal-20260923.md) and review define the
+independent fixtures and rejected shortcuts. Same-pass unresolved syntax is a
+dependency of later mixed resolution/index/composition, not public source8
+activation or a substitute for whole-output admission. Source implementation,
+fresh review and runtime checks remain required.
+
 ## Private source composition decision — 2026-09-23

 Adopt the opaque validated original-span rename batch as the next private