From ef5a13f7626c33198f1c5c4deea22289cac460d0 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 26 Oct 2026 16:44:07 +0000 Subject: [PATCH] workflow: no repeat availability notes when nothing changed (#283 option B) Dylan chose option B on #283 on 26 October. Item 2 lands as one sentence, the candidate wording from the #283 request, placed next to the existing "Availability notes ... are not pickups" lines. It does not change who may do what; it asks an invocation with nothing new not to repeat its own availability post on the current board. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01V3DF6ms7UTpj27UqDG4u5h --- governance/OP-WORKFLOW-20260930.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/governance/OP-WORKFLOW-20260930.md b/governance/OP-WORKFLOW-20260930.md index ca1142e03..40d123a4e 100644 --- a/governance/OP-WORKFLOW-20260930.md +++ b/governance/OP-WORKFLOW-20260930.md @@ -42,7 +42,11 @@ may begin the smallest disjoint stage after reading current claims and publishin an actual task-local pickup naming the source, scope, exclusions, checks and a finite checkpoint. Availability notes, offers and shared agent labels are not pickups; such routine work needs no extra coordinator acknowledgement unless a -specific task or existing rule requires one. This does not authorize an occupied +specific task or existing rule requires one. An invocation that finds nothing to +pick up does not post an availability or no-pickup note if its worker ID or lane +already has one on the current board and nothing material has changed since: a +task offered to it, its own claim, or the board itself. This does not +authorize an occupied role, private-access expansion, security-sensitive change, protected integration or an action stopped by a denial or unresolved finding.