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

Clarify applicable semantic review replay guarantees

Browse Source
This commit is contained in:
sorokin.oleg.edu
2026-09-06 05:34:35 +03:00
parent 02f99a9ac5
commit 29df024a7f
2 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/language.html
+6 -2
View File
@@ -1902,8 +1902,12 @@ bounded derived impact walk follows reusable definitions and interface allocatio
not arbitrary architectural neighborhoods, and does not copy them into every
referrer's baseline. Its limits are 4096 objects per side and 32768 edges; exhaustion
is a diagnostic. Successful review remains one undoable transaction. Replanning
already acknowledged unchanged values is a no-op; an old plan becomes stale after
an actual committed change.</p>
unchanged, already acknowledged leaf facts is a no-op only while their requests
remain applicable. A completed constructor switch MUST be removed from subsequent
requests; repeating it when no switch remains is rejected. After an artifact moves
to another owner, metadata review through the old owner's trace is no longer
applicable and is rejected. An old plan becomes stale after an actual committed
change.</p>
</section>
<section id="source-examples-and-historical-token-rules">
<h3>5.5. Source examples and historical token rules</h3>
docs/language.rst
+6 -2
View File
@@ -1239,8 +1239,12 @@ bounded derived impact walk follows reusable definitions and interface allocatio
not arbitrary architectural neighborhoods, and does not copy them into every
referrer's baseline. Its limits are 4096 objects per side and 32768 edges; exhaustion
is a diagnostic. Successful review remains one undoable transaction. Replanning
already acknowledged unchanged values is a no-op; an old plan becomes stale after
an actual committed change.
unchanged, already acknowledged leaf facts is a no-op only while their requests
remain applicable. A completed constructor switch MUST be removed from subsequent
requests; repeating it when no switch remains is rejected. After an artifact moves
to another owner, metadata review through the old owner's trace is no longer
applicable and is rejected. An old plan becomes stale after an actual committed
change.
5.5. Source examples and historical token rules
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~