Escalation procedure has no recovery for a wrong verdict when the behavior already exists #951

New issue

Open

opened 2026-10-05 12:56:38 +00:00 by jared · 0 comments

jared commented

2026-10-05 12:56:38 +00:00

Owner

Problem

plugins/os-sdlc/references/escalation-procedure.md gives no recovery for a wrong verdict when the behavior already exists. A fresh run in the same worktree hits unexpected_pass again.

Reproduce

n/a: procedure gap in a reference document; seen in implementation 29 of ticket #947.

Approach

Step 4 allows os-sdlc-reroute-request only for a map misfit. For any other cause, including a wrong verdict, it says to start a fresh implementation-open or abandon. A wrong-verdict fail means the production behavior is already in the worktree. A fresh run then gets unexpected_pass from the first test-writer round. Add a rule for the wrong-verdict cause.

Required work:

Add a wrong-verdict recovery rule to the procedure, with the reroute or other route it allows — check: present wrong verdict in plugins/os-sdlc/references/escalation-procedure.md

Acceptance criteria

Given an escalation whose cause is a wrong verdict and whose behavior already exists in the worktree, when the procedure is followed, then it names a recovery that does not hit unexpected_pass.

Owner sketch

# references/escalation-procedure.md step 4: wrong-verdict branch

Origin

Trigger: os-sdlc implementation 29 of ticket #947, escalation 10.
Improvised this session: orchestrator reroute back to behavior-verifier.
Chain: no clean recovery ← procedure allows reroute only for map misfit ← DESIGN (plugins/os-sdlc/references/escalation-procedure.md step 4).
Where: plugins/os-sdlc/references/escalation-procedure.md
Session: ab599e53-dbf5-4953-b8bf-c598a9c5c16e
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-crc-os-adr-2026-10-04/ab599e53-dbf5-4953-b8bf-c598a9c5c16e.jsonl

VERDICT: CREATE

## Problem `plugins/os-sdlc/references/escalation-procedure.md` gives no recovery for a wrong verdict when the behavior already exists. A fresh run in the same worktree hits `unexpected_pass` again. ## Reproduce n/a: procedure gap in a reference document; seen in implementation 29 of ticket #947. ## Approach Step 4 allows `os-sdlc-reroute-request` only for a map misfit. For any other cause, including a wrong verdict, it says to start a fresh `implementation-open` or abandon. A wrong-verdict fail means the production behavior is already in the worktree. A fresh run then gets `unexpected_pass` from the first test-writer round. Add a rule for the wrong-verdict cause. Required work: 1. Add a wrong-verdict recovery rule to the procedure, with the reroute or other route it allows — check: present `wrong verdict` in `plugins/os-sdlc/references/escalation-procedure.md` ## Acceptance criteria 1. Given an escalation whose cause is a wrong verdict and whose behavior already exists in the worktree, when the procedure is followed, then it names a recovery that does not hit unexpected_pass. ## Owner sketch ```ruby # references/escalation-procedure.md step 4: wrong-verdict branch ``` ## Origin - Trigger: os-sdlc implementation 29 of ticket #947, escalation 10. - Improvised this session: orchestrator reroute back to behavior-verifier. - Chain: no clean recovery ← procedure allows reroute only for map misfit ← DESIGN (plugins/os-sdlc/references/escalation-procedure.md step 4). - Where: plugins/os-sdlc/references/escalation-procedure.md - Session: ab599e53-dbf5-4953-b8bf-c598a9c5c16e - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-crc-os-adr-2026-10-04/ab599e53-dbf5-4953-b8bf-c598a9c5c16e.jsonl VERDICT: CREATE

jared added the

plugin/os-sdlc

filed-by/agent

labels

2026-10-05 12:56:38 +00:00

jared referenced this issue

2026-10-05 12:56:49 +00:00

inward-dependencies lint crashes on reroute/; take roles from a map, not the folder #947

jared referenced this issue

2026-10-05 13:05:49 +00:00

os-adr: three copies of path and file-name knowledge (A12) #948

jared referenced this issue