Adopt reviewed private original-span export boundary

This commit is contained in:
2026-09-23 00:03:33 -07:00
parent cc3d6a4875
commit c87a0c2bd9
3 changed files with 173 additions and 0 deletions
+33
View File
@@ -1,5 +1,38 @@
# Architectural and product decisions
## Private source composition decision — 2026-09-23
Adopt the opaque validated original-span rename batch as the next private
analysis adapter step, with the [independent review's clarifications](analysis-original-span-review-20260923.md).
The [original proposal](analysis-original-span-proposal-20260922.md) compares
this against replacing both ordinary and typed edit representations. The narrow
adapter preserves current ordinary compatibility and reduces migration risk;
a shared edit AST remains a candidate if structural composition demonstrates a
need. Neither sequentially applying producers with stale offsets nor canonical
rewriting is acceptable for authored-source preservation.
The immediate patch exports complete borrowed rename records and splits
ownership validation from standalone final-output size preflight. It may defer
only hypothetical typed-only output sizing; active inherited budget, plan/name
storage, qualified namespace, source equality and complete occurrence checks
remain mandatory. Standalone rename/apply semantics remain intact. This is
private staging, not a complete parse-session or public source8 boundary.
Before production composition, one checked parsed-bundle witness must bind the
complete source/entry/file map, ordinary model, typed index, profile and complete
target intent. Ordinary syntax-kind replacement currently emits same-start
insertion/deletion pairs; explicitly normalize such owned operations with exact
trivia oracles before admitting them, keeping cross-producer collisions errors.
Gate supported changes by a precise complete-model diff. Compile the actual
emitted full bundle, use normal admission, and compare the complete intended
Project before installation. Exact untouched bytes are an independent gate.
Subtree edits, parameter lifecycle, repaired deletion, reidentity, relocation,
missing-ID stabilization, migration/history and checked-save remain required
delivery work; passing the private rename slice cannot close those requirements.
The source-pinned proposal/review retain their original local provenance labels.
The accepted underlying repair contract is [r2 at analysis source 1b1c3e3](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/src/commit/1b1c3e3abb6fc3d0934c9dbfbd21fddc8ae4f594/harness/analysis-source8-20260913/analysis-source8-repair-design-r2-20260913.md).
## Current continuation decisions — 2026-09-06
- Saving under another source entry basename is destination bookkeeping, not an engineering edit. Adopt an exact current save receipt without adding Undo or clearing Redo; rebase uniform entry names across retained history after collision and compilation checks. Stale receipts cannot redirect newer raw source. Native discovery and eleven focused regression results are in release-save-as-runtime-packaging.md; updated native verification remains required.