Skip to content

Commit a789b27

Browse files
thymikeeclaude
andcommitted
docs(adr): keep target-drag motion inapplicable under admission
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent dabbf5f commit a789b27

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/adr/0039-pre-dispatch-admission.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,6 @@ A refusal before any send reports `dispatched: no`. A failure after a send repor
5757
## Consequences and open gaps
5858

5959
No wait loop for these interactions exists outside admission; the moving-target gate's schedules move into it. New pre-dispatch checks and platform facts join admission instead of adding their own loop or carrier.
60-
Long-press, fill, hover and drag gain the motion check. Their accept-path latency must not grow.
60+
Long-press, double-tap, fill and hover gain the motion check. Their accept-path latency must not grow. Target-authored drag runs admission without the motion check: ADR 0011 marks its target stability inapplicable, because re-pointing one endpoint would split the gesture plan.
6161
An app-timed overlay that appears with no preceding mutation is not detected on an idle press. This is the cost rule's trade-off and matches the gate's existing blind spot.
6262
Partial custom covers (#4347) and safe regions for coordinate-authored trajectories stay open. Admission gives them a place; it does not solve them.

0 commit comments

Comments
 (0)