From 7fcbe0c8900421c46d80b7945f90d38ae4686e5e Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 15 Oct 2026 22:09:57 +0000 Subject: [PATCH 1/2] governance: apply agent 3 claim-ownership checks to OP-WORKFLOW MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Verbatim +26/−0 patch from main#419 comment 6203253357, written against base 7a7704fe. Author of record: Grok Bot agent 3. Co-authored-by: Dylan Roy --- governance/OP-WORKFLOW-20260930.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/governance/OP-WORKFLOW-20260930.md b/governance/OP-WORKFLOW-20260930.md index 08289c492..6643c999b 100644 --- a/governance/OP-WORKFLOW-20260930.md +++ b/governance/OP-WORKFLOW-20260930.md @@ -100,6 +100,32 @@ acknowledgement and activation stand alone; an unidentified second successor doe delay the first. Retained stops are carried by name. None of this adds a register, a scheduler, a permission gate, a forced release or independence credit. +Four checks bracket every claim, mutation and verdict: + +1. Before claiming, check whether the requested output has already landed on + the default branch; if it has, do not reselect the work. +2. Right after claiming, and again before substantive work, reread the + task-local and board claims and stop on overlap. There is no fixed wait. + "Earliest created_at wins" applies only to genuinely equivalent scopes, after + the already-landed check; a claimant withdraws only its own claim. +3. Before mutating, recheck current state and use an expected-head guard. For + unversioned configuration such as automation prompts, use one serial writer + with a readback after each write. +4. Before posting a verdict, reread the native review collection and stop if an + equivalent review already exists. + +A lease end is a checkpoint, not proof of release: an unknown predecessor goes +through explicit reassignment, successor acknowledgement and fresh activation, +with its closeout kept UNKNOWN. Do not post separate third-party collision +notices; reuse one existing notice and add only materially new evidence. Review +carry-over to a new head also needs unchanged hypotheses and consumed +dependencies, the current tested composition and checks, and the actual +Ready-triggered review, not just matching blobs. The checklist records the +reviewed head, the PR-reported base and the actually tested merge commit and its +parents as separate identities, never inferred from a green badge. A resolved +thread is UI state, not a finding disposition; AMEND history and successor +reviews keep both identities. + Maintain one short current disposition in the PR body or a linked comment: current head, owner, completed review scopes, unresolved finding IDs, validation and next action. Update it on material change; link detailed evidence instead From 1dba018e01edf085bc805ab128eba71c5d7a59b0 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 15 Oct 2026 22:40:01 +0000 Subject: [PATCH 2/2] governance: amend OP-WORKFLOW claim checks for M424-NOTICE-01 and M424-ORDER-02 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Verbatim +11/−4 patch from main#424 comment 6203729177 on head 7fcbe0c8. Author of record: Grok Bot agent 3. Co-authored-by: Dylan Roy --- governance/OP-WORKFLOW-20260930.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/governance/OP-WORKFLOW-20260930.md b/governance/OP-WORKFLOW-20260930.md index 6643c999b..9c433f415 100644 --- a/governance/OP-WORKFLOW-20260930.md +++ b/governance/OP-WORKFLOW-20260930.md @@ -106,8 +106,13 @@ Four checks bracket every claim, mutation and verdict: the default branch; if it has, do not reselect the work. 2. Right after claiming, and again before substantive work, reread the task-local and board claims and stop on overlap. There is no fixed wait. - "Earliest created_at wins" applies only to genuinely equivalent scopes, after - the already-landed check; a claimant withdraws only its own claim. + Each claim has one canonical pickup record, named in the claim; board or + task-local mirrors cross-link it and carry no priority of their own. + "Earliest created_at wins" compares canonical records only, applies only to + genuinely equivalent scopes, after the already-landed check; a claimant + withdraws only its own claim. If which record is canonical, or their order, + is ambiguous or tied, both actors stop the affected mutation and reconcile + in the existing thread; this does not reassign claims already released. 3. Before mutating, recheck current state and use an expected-head guard. For unversioned configuration such as automation prompts, use one serial writer with a readback after each write. @@ -116,8 +121,10 @@ Four checks bracket every claim, mutation and verdict: A lease end is a checkpoint, not proof of release: an unknown predecessor goes through explicit reassignment, successor acknowledgement and fresh activation, -with its closeout kept UNKNOWN. Do not post separate third-party collision -notices; reuse one existing notice and add only materially new evidence. Review +with its closeout kept UNKNOWN. Reuse an existing collision notice where +possible. If none exists, or it cannot reach the affected actors, post one +source-linked warning containing materially new conflict evidence; avoid +duplicate notices. Review carry-over to a new head also needs unchanged hypotheses and consumed dependencies, the current tested composition and checks, and the actual Ready-triggered review, not just matching blobs. The checklist records the