jared/cc-os

Watch

Fork 0

Takedown relevance treats an ADR filename slug as binding after the ADR judge rules the change a habit #1435

New issue

Closed

opened 2026-10-27 17:58:55 +00:00 by jared · 2 comments

jared commented

2026-10-27 17:58:55 +00:00

Owner

Problem

The ticket-takedown relevance step blocks a ticket forever when it judges against an ADR filename slug and the ADR judge refuses to write a resolving ADR.

Observed

The relevance step in plugins/os-sdlc/eval/ticket-takedown returned needs_ruling on ADR-0055 with resolved_by: null.
Its reason was: "ADR-0055 is titled 'root is derived from its location, never stored' ... the title's wording is not settled by any later Accepted ADR".
The ADR body says only "It stores NO paths" about .sdlc/project.yaml.
The current H1 title is "...stores no paths". Only the filename slug says "never stored".
/os-adr:create rejected an ADR for the change as a habit, because only one plugin reads the column.
The relevance step accepts only a later Accepted ADR as a resolution. The judge refuses to write one. A ticket that hits this stays blocked forever.
Evidence: docs/takedown/1164-20261027-135509/02-relevance.reply.json.

Reproduce

Run the takedown for #1164. Runs docs/takedown/1164-20261027-134934 and docs/takedown/1164-20261027-135509 both blocked.

Approach

The fix is one of two options. (a) Let relevance accept a recorded os-adr judge rejection, or a ruling comment on the ticket, as resolved_by. (b) Judge the ADR body and title, not the filename slug.

Required work: none beyond the acceptance criteria.

Acceptance criteria

Given an ADR whose body does not state a claim and whose filename slug does, when relevance runs, then the slug alone does not produce needs_ruling.

Origin

Trigger: ticket-takedown runs on #1164
Improvised this session: proceeding with /os-sdlc:implement 1164 on the current body
Chain: ticket blocked forever ← relevance accepts only a later Accepted ADR as resolved_by ← DESIGN (plugins/os-sdlc/eval/ticket-takedown)
Root candidate: none found; searched takedown, relevance, needs_ruling, resolved_by, ADR-0055, filename slug, adr_causes
Where: plugins/os-sdlc/eval/ticket-takedown relevance step
Session: 82e65b81-56fa-4c14-acd0-f225c6f57314
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/fe2e7204-cf6e-4241-b776-f9c5f032f4a9.jsonl

VERDICT: CREATE

## Problem The ticket-takedown relevance step blocks a ticket forever when it judges against an ADR filename slug and the ADR judge refuses to write a resolving ADR. ## Observed The relevance step in `plugins/os-sdlc/eval/ticket-takedown` returned `needs_ruling` on ADR-0055 with `resolved_by: null`. Its reason was: "ADR-0055 is titled 'root is derived from its location, never stored' ... the title's wording is not settled by any later Accepted ADR". The ADR body says only "It stores NO paths" about `.sdlc/project.yaml`. The current H1 title is "...stores no paths". Only the filename slug says "never stored". `/os-adr:create` rejected an ADR for the change as a habit, because only one plugin reads the column. The relevance step accepts only a later Accepted ADR as a resolution. The judge refuses to write one. A ticket that hits this stays blocked forever. Evidence: `docs/takedown/1164-20261027-135509/02-relevance.reply.json`. ## Reproduce Run the takedown for #1164. Runs `docs/takedown/1164-20261027-134934` and `docs/takedown/1164-20261027-135509` both blocked. ## Approach The fix is one of two options. (a) Let relevance accept a recorded os-adr judge rejection, or a ruling comment on the ticket, as `resolved_by`. (b) Judge the ADR body and title, not the filename slug. Required work: none beyond the acceptance criteria. ## Acceptance criteria 1. Given an ADR whose body does not state a claim and whose filename slug does, when relevance runs, then the slug alone does not produce `needs_ruling`. ## Origin - Trigger: ticket-takedown runs on #1164 - Improvised this session: proceeding with /os-sdlc:implement 1164 on the current body - Chain: ticket blocked forever ← relevance accepts only a later Accepted ADR as resolved_by ← DESIGN (plugins/os-sdlc/eval/ticket-takedown) - Root candidate: none found; searched takedown, relevance, needs_ruling, resolved_by, ADR-0055, filename slug, adr_causes - Where: plugins/os-sdlc/eval/ticket-takedown relevance step - Session: 82e65b81-56fa-4c14-acd0-f225c6f57314 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/fe2e7204-cf6e-4241-b776-f9c5f032f4a9.jsonl VERDICT: CREATE

jared added the

plugin/os-sdlc

filed-by/user

category/code-change

labels

2026-10-27 17:58:55 +00:00

jared commented

2026-10-27 18:00:08 +00:00

Author

Owner

Work started on branch ticket-1435 (worktree .claude/worktrees/ticket-1435).

jared referenced this issue from a commit

2026-10-27 18:01:23 +00:00

fix(os-sdlc): relevance judge reads ADR title and body, not filename slug (#1435)

jared referenced this issue from a commit

2026-10-27 18:07:30 +00:00

docs(os-sdlc): takedown run records for #1164 (two relevance blocks, one stopped after the #1435 fix passed relevance)

jared referenced this issue

2026-10-27 18:30:29 +00:00

Pipeline briefs read the caller's directory, not the bound worktree root #1164

jared commented

2026-10-27 19:26:12 +00:00

Author

Owner

Resolution

Done: The relevance-judge card now says: judge an ADR only by its H1 title and its decision body; the filename slug is not part of the ADR.

Evidence: main 4c8265b6 (merged as c215631f). The #1164 takedown re-run passed relevance after the change (docs/takedown/1164-20261027-140130, step 02 relevance ok). Takedown harness suite green.

Follow-ups: none

## Resolution **Done:** The relevance-judge card now says: judge an ADR only by its H1 title and its decision body; the filename slug is not part of the ADR. **Evidence:** main 4c8265b6 (merged as c215631f). The #1164 takedown re-run passed relevance after the change (docs/takedown/1164-20261027-140130, step 02 relevance ok). Takedown harness suite green. **Follow-ups:** none

jared closed this issue

2026-10-27 19:26:13 +00:00

jared referenced this issue from a commit

2026-10-27 19:26:20 +00:00

docs(os-sdlc): History row for #1435