overlays

docs/adr/0002-concurrent-foreach-policy-and-barrier-commits.md

@@ -95,11 +95,11 @@ Patch creation and commit must extract/reuse the existing node output
 validation, output binding, and reducer logic. Concurrent foreach must not
 create a second write system.
 
-Current sync V1 implements the barrier commit path only for `loop -> one node ->
-END` item bodies. The runtime includes an explicit no-op overlay seam
-(`state_view_for_frame`) so the next slice can add lineage-local reads without
-rewiring node execution. Until that seam becomes real, multi-step concurrent
-item bodies are rejected instead of reading stale parent state.
+Current sync execution supports item-local read overlays for concurrent foreach
+item frames. `RunState.state` remains committed parent state, while
+`state_view_for_frame` overlays the current item's buffered writes for reads by
+later nodes in the same item lineage. Sibling overlays remain invisible until
+the foreach barrier commits.
 
 ## Merge and Reducer Rules