Fix verifier-fail routing that cannot reach green in implement map #1100

New issue

Open

opened 2026-10-18 14:53:28 +00:00 by jared · 0 comments

jared commented

2026-10-18 14:53:28 +00:00

Owner

Problem

A behavior-verifier fail on a green increment sends the run back to a red-first test-writer round. The test-reviewer round_tests rule needs each new test to be red. Tests for behavior that the green production code already has cannot be red. So the loop can only end with a bound escalation.

A second problem: gate briefs judged against more than the AC text. Behavior-verifier (542) and test-reviewer (546) asked for things that the AC text does not ask for, such as lib_root on Project and a new --ticket option with a TSV ticket column.

Observed

Implementation 63, dispatches 542-550, ended with escalation 35 bound_exhausted:test-reviewer/fail.
Test-reviewer at 550 said "no test change can make the concept-brief tests red. The runner must decide."

Reproduce

n/a: the evidence is implementation 63 in the pipeline database.

Approach

Expected: a verifier fail on green work routes to a node that can add the missing behavior. Or round_tests leaves out tests for behavior that already exists. Gate briefs judge against the AC text only.

Required work:

Route a behavior-verifier fail on green work to a node that can add missing behavior, or exempt already-green behavior from the round_tests red rule, in the poodr-ticket-implementation map.

Acceptance criteria

Given a green increment that the behavior-verifier fails, when the run continues, then it reaches a node that can change production code or a round that does not require red tests for existing behavior.
Given a gate brief, when a verifier or reviewer judges the work, then the brief names the AC text as the only spec.

Origin

Trigger: Follow-up from #1094 (implementation 63, hand-finish commit 17d4c688), session 6f78b932-f117-4bd7-bbed-524776dbb719.
Improvised this session: none
Chain: bound escalation <- red-only round_tests rule <- map routes verifier fail to test-writer (map poodr-ticket-implementation)
Where: poodr-ticket-implementation map; os-sdlc test-reviewer round_tests rule
Session: 6f78b932-f117-4bd7-bbed-524776dbb719
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/6f78b932-f117-4bd7-bbed-524776dbb719.jsonl

## Problem A behavior-verifier fail on a green increment sends the run back to a red-first test-writer round. The test-reviewer round_tests rule needs each new test to be red. Tests for behavior that the green production code already has cannot be red. So the loop can only end with a bound escalation. A second problem: gate briefs judged against more than the AC text. Behavior-verifier (542) and test-reviewer (546) asked for things that the AC text does not ask for, such as lib_root on Project and a new --ticket option with a TSV ticket column. ## Observed Implementation 63, dispatches 542-550, ended with escalation 35 `bound_exhausted:test-reviewer/fail`. Test-reviewer at 550 said "no test change can make the concept-brief tests red. The runner must decide." ## Reproduce n/a: the evidence is implementation 63 in the pipeline database. ## Approach Expected: a verifier fail on green work routes to a node that can add the missing behavior. Or round_tests leaves out tests for behavior that already exists. Gate briefs judge against the AC text only. Required work: 1. Route a behavior-verifier fail on green work to a node that can add missing behavior, or exempt already-green behavior from the round_tests red rule, in the poodr-ticket-implementation map. ## Acceptance criteria 1. Given a green increment that the behavior-verifier fails, when the run continues, then it reaches a node that can change production code or a round that does not require red tests for existing behavior. 2. Given a gate brief, when a verifier or reviewer judges the work, then the brief names the AC text as the only spec. ## Origin - Trigger: Follow-up from #1094 (implementation 63, hand-finish commit 17d4c688), session 6f78b932-f117-4bd7-bbed-524776dbb719. - Improvised this session: none - Chain: bound escalation <- red-only round_tests rule <- map routes verifier fail to test-writer (map poodr-ticket-implementation) - Where: poodr-ticket-implementation map; os-sdlc test-reviewer round_tests rule - Session: 6f78b932-f117-4bd7-bbed-524776dbb719 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/6f78b932-f117-4bd7-bbed-524776dbb719.jsonl

jared added the

plugin/os-sdlc

filed-by/user

category/code-change

labels

2026-10-18 14:53:28 +00:00

jared referenced this issue

2026-10-18 14:54:51 +00:00

collaborator-pass: prescribe per concept with an owners-that-exist list #1094

jared referenced this issue

2026-10-25 20:06:32 +00:00

Add os-sdlc routes for deletion tickets and search-check criteria over pinned tests #1339