From dbb0554288cca46cfe1067bc3eaca0104f576bd7 Mon Sep 17 00:00:00 2001
From: Andriujose <43181885+andriujoseba@users.noreply.github.com>
Date: Mon, 3 Aug 2026 19:07:08 +0000
Subject: [PATCH] docs: clarify attention target

---
 TRIAGE.md          | 5 ++++-
 changelog.d/230.md | 5 +++++
 2 files changed, 9 insertions(+), 1 deletion(-)
 create mode 100644 changelog.d/230.md

diff --git a/TRIAGE.md b/TRIAGE.md
index 75e1b6d..e2cbe53 100644
--- a/TRIAGE.md
+++ b/TRIAGE.md
@@ -68,7 +68,10 @@ is the failure this whole flow exists to prevent.
    agreement is reached, record the ruling as a decision in one comment,
    remove the label, and return the issue to its flow in that same comment;
    when that ruling or any directive or answered builder question delivers
-   the assignee's next move in prose, set `attention` in the same comment.
+   the assignee's next move in prose, set `attention` in the same comment on
+   the assigned issue that owns the claim — never on the pull request, even
+   when the comment lives there. An unassigned issue is a board bug, not a
+   demand; repair the board rather than setting `attention`.
    This is not a substitute for minting work or for `needs-ruling`.
 4. **Decline.** Real idea, wrong repo or wrong time. Say why plainly, link
    where it belongs if anywhere, close. A refusal with reasons is a good
diff --git a/changelog.d/230.md b/changelog.d/230.md
new file mode 100644
index 0000000..159ce2b
--- /dev/null
+++ b/changelog.d/230.md
@@ -0,0 +1,5 @@
+### Fixed
+
+- Triage now puts `attention` on the assigned issue that owns a claim, never
+  on its pull request, and treats an unassigned issue as a board bug rather
+  than a demand (#230).