sorokin.oleg.edu/ARCADIA-Studio
1
0
Fork 0
Code Issues 37 Pull Requests 2 Packages Projects Releases 9 Wiki Activity

Record verified mixed rename planning and execution boundary evidence

Browse Source
This commit is contained in:
sorokin.oleg.edu
2026-09-24 16:56:54 -07:00
parent dc87babf0f
commit 81ab373f8e
24 changed files with 1621 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
harness/DECISIONS.md
+28
View File
@@ -586,3 +586,31 @@ with separately reported new usage and aggregate live-storage accounting. An
independent fresh ledger must not hide retained output or old state. Execution
ownership/readmission seams remain separate required implementation; this
decision does not label a read-only plan as accepted rewritten source.
## 2026-09-24 — carry output storage through actual verification
The [execution source map](analysis-mixed-rename-execution-20260924/RENAME-EXECUTION-SOURCE-MAP.md)
identifies the next boundary: output buffers already coexist with parsing, so
adding a retained-output baseline only at resolution checks too late. Preserve
the exact per-snapshot Limits and ProjectLimits, explicitly drop consumed old
auxiliary state, and carry surviving output storage through verification.
The final comparison must include aliases and parameter names; the planning
gate deliberately omits them and cannot establish accepted rewritten output.
We considered authenticating exact output bytes, then reserving a conservative
parser envelope derived from the unchanged syntax topology. The
[independent feasibility investigation](analysis-mixed-rename-execution-20260924/RENAME-EXECUTION-ENVELOPE-FEASIBILITY.md)
found useful partial bounds but no complete safe, useful aggregate formula.
Finishing it would duplicate parser lifecycle knowledge across expression
tasks, name sets, projection buffers, string decoding and include traversal.
Select explicit carried storage accounting at actual growth/handoff seams for
the next bounded design instead. Revisit an envelope only if a small, stable
source-derived proof demonstrates useful caps; do not use unexplained byte or
node multipliers. This chooses a direction, not an implemented execution API.
The [domain audit](analysis-mixed-rename-execution-20260924/CARRIED-STORAGE-DOMAIN-AUDIT.md)
keeps the declared metric explicit: logical auxiliary slots/text are distinct
from model/serde/raw-validator heap, allocator capacity and process RSS. The
exploratory allocation inventory is not a requirement to meter all heap usage.
The successor contract must reconcile that domain before selecting growth
hooks or claiming an aggregate pre-allocation guarantee.