Skip to content

Commit ea9be72

Browse files
committed
docs(adr): scope landmark mode to wait in ADR 0017
The STE rewrite read as if `is` and `get` also record landmark-mode evidence. The base lists three read-only actions: `wait` in landmark mode, `is`, and `get`. Found in review round 2.
1 parent 85977d7 commit ea9be72

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/adr/0017-parameterized-recorded-inputs.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ Safe authoring emits one complete placeholder token.
116116

117117
The boundary above protects only the request/recording path of the originating fill itself.
118118
After [#1349](https://github.com/callstack/agent-device/issues/1349), a later read-only action records `target-v1` identity evidence and a result payload independently.
119-
These read-only actions are the landmark-mode evidence of `wait`, `is`, and `get`.
119+
These read-only actions are `wait` with landmark-mode evidence, `is`, and `get`.
120120
That capture comes from whatever the app renders at that later step.
121121
The capture has no memory of the literal of an earlier fill.
122122
Thus, an app-rendered echo of the literal can re-enter session state and publication through a completely different, unparameterized action.

0 commit comments

Comments
 (0)