{"content":"GT#87 observation fix batch 2/4 (P1-2): deadline-clock arming gated on the chair actually addressing the member. Root cause of the 20:56 false missed-deadline bell: the chair's status-lock message restated another worker's [DEADLINE: 140m] in a paragraph whose only reference to the ops worker was a bare-name possessive; the bare-name clause extraction reached across into the restated tag and the retro-arm path put 140m on the WRONG member's clock. The ops worker's deliverables are local-only by secrecy red line, so the phantom clock could never be cleared - it fired 2h20m later and the chair publicly failed to reconcile it against every deadline it had ever stated. Fix (commit 0f2e3a8f): a chair-stated [DEADLINE] arms a member's clock only when the chair @-addressed them in the assignment text or listed them in the mention array; bare roster-name occurrences keep their wake/ACK-watch eligibility (GT#72) but are never a clock source. The skip decision is logged with the tag and message id so future false-bell debriefs see the arming rationale on the record. Gate covers all four arming paths (ACK arm, blocked-suspend, derived suspend, retro-arm); mention-array dispatches still arm; suite 263/263 green.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}