Rule how a CRC run applies a predicted deletion or merge #1272

New issue

Open

opened 2026-10-23 18:30:56 +00:00 by jared · 0 comments

jared commented

2026-10-23 18:30:56 +00:00

Owner

Problem

crc-refactor phase 5 says a merge or deletion is never a verdict: it goes into the row's question cell. The final judgment round predicts those rows, and the run prompt says "apply the predictions". standing-rules.md "Stops" says a deletion stops the run. No rule says which text wins. In CRC run 4 the predictor chose delete for 10 rows and merge for 2 rows. The run applied none of them and filed them as follow-ups.

Reproduce

n/a: a rule conflict in the skill text.

Approach

Jared rules on one of two options. Option A: the final round may apply a predicted deletion or merge in one separate commit that a revert can undo. Option B: such a prediction always becomes a follow-up ticket. Then SKILL.md phase 5 and phase 7 and standing-rules.md "Stops" say it.

Origin

Trigger: CRC run 4 final judgment round (commit 123ac007); Jared's kickoff handoff named the conflict and said "Report it, and do not invent a rule."
Improvised this session: filed the predicted deletions and merges as follow-ups
Chain: predicted deletions not applied ← SKILL.md phase 5 and standing-rules "Stops" disagree ← DESIGN (plugins/os-sdlc/skills/crc-refactor/references/standing-rules.md)
Root candidate: none found; searched crc-refactor, standing-rules, Stops, predicted deletion, merge, question cell
Where: plugins/os-sdlc/skills/crc-refactor/SKILL.md, plugins/os-sdlc/skills/crc-refactor/references/standing-rules.md
Session: c1bedec6-7e01-45ab-b9db-22d63652c19f
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-crc-os-sdlc-run-4/c1bedec6-7e01-45ab-b9db-22d63652c19f.jsonl

VERDICT: CREATE

## Problem crc-refactor phase 5 says a merge or deletion is never a verdict: it goes into the row's `question` cell. The final judgment round predicts those rows, and the run prompt says "apply the predictions". standing-rules.md "Stops" says a deletion stops the run. No rule says which text wins. In CRC run 4 the predictor chose delete for 10 rows and merge for 2 rows. The run applied none of them and filed them as follow-ups. ## Reproduce n/a: a rule conflict in the skill text. ## Approach Jared rules on one of two options. Option A: the final round may apply a predicted deletion or merge in one separate commit that a revert can undo. Option B: such a prediction always becomes a follow-up ticket. Then SKILL.md phase 5 and phase 7 and standing-rules.md "Stops" say it. ## Origin - Trigger: CRC run 4 final judgment round (commit 123ac007); Jared's kickoff handoff named the conflict and said "Report it, and do not invent a rule." - Improvised this session: filed the predicted deletions and merges as follow-ups - Chain: predicted deletions not applied ← SKILL.md phase 5 and standing-rules "Stops" disagree ← DESIGN (plugins/os-sdlc/skills/crc-refactor/references/standing-rules.md) - Root candidate: none found; searched crc-refactor, standing-rules, Stops, predicted deletion, merge, question cell - Where: plugins/os-sdlc/skills/crc-refactor/SKILL.md, plugins/os-sdlc/skills/crc-refactor/references/standing-rules.md - Session: c1bedec6-7e01-45ab-b9db-22d63652c19f - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-crc-os-sdlc-run-4/c1bedec6-7e01-45ab-b9db-22d63652c19f.jsonl VERDICT: CREATE

jared added the

plugin/os-sdlc

filed-by/agent

category/owner-ruling

labels

2026-10-23 18:30:56 +00:00