Add a --signal mode to fast-gate for detector-named findings #1237

Open
opened 2026-10-22 19:18:43 +00:00 by jared · 0 comments
Owner

Problem

plugins/os-sdlc/bin/fast-gate --target T --cop COP PATH... gates a finding by cop name plus paths. A detector-named finding has source detector/<name> and no rubocop cop. It has no direct input. The fast-batch brief works around this with --cop Sdlc/Structural/InwardDependency plus a second detector run.

Reproduce

n/a: design ticket; the workaround is in plugins/os-sdlc/skills/fast-batch/references/batch-brief.md line 31.

Approach

Add --signal. It reads Signal TSV rows on stdin. It asserts that the named detector reports no signal at those sites.

Required work:

  1. Add the --signal mode to fast-gate — check: present --signal in plugins/os-sdlc/bin/fast-gate
  2. Drop the workaround from the fast-batch brief — check: absent --cop Sdlc/Structural/InwardDependency in plugins/os-sdlc/skills/fast-batch/references/batch-brief.md

Acceptance criteria

  1. Given Signal TSV rows on stdin for a detector, when fast-gate runs with --signal and the detector reports no signal at those sites, then the gate passes.
  2. Given a site that still has a signal, when fast-gate runs with --signal, then the gate fails and names the site.
  3. Given the fast-batch brief, when a detector finding is gated, then the brief uses --signal and has no InwardDependency workaround.

Origin

  • Trigger: fast-gate shipped in 05e4e1b7 (merged cde8a6b6); detector-named findings have no input.
  • Improvised this session: the brief uses --cop Sdlc/Structural/InwardDependency plus a second detector run.
  • Chain: workaround in brief ← fast-gate accepts only cop names ← DESIGN (plugins/os-sdlc/bin/fast-gate).
  • Root candidate: none found; searched fast-gate, --signal, detector, fast-batch, Signal TSV, brief
  • Where: plugins/os-sdlc/bin/fast-gate
  • Session: 3ff277d2-0942-49d9-8ac0-4e778200b1e2
  • Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/3ff277d2-0942-49d9-8ac0-4e778200b1e2.jsonl

VERDICT: CREATE

## Problem `plugins/os-sdlc/bin/fast-gate --target T --cop COP PATH...` gates a finding by cop name plus paths. A detector-named finding has source `detector/<name>` and no rubocop cop. It has no direct input. The fast-batch brief works around this with `--cop Sdlc/Structural/InwardDependency` plus a second detector run. ## Reproduce n/a: design ticket; the workaround is in `plugins/os-sdlc/skills/fast-batch/references/batch-brief.md` line 31. ## Approach Add `--signal`. It reads Signal TSV rows on stdin. It asserts that the named detector reports no signal at those sites. Required work: 1. Add the `--signal` mode to fast-gate — check: present `--signal` in `plugins/os-sdlc/bin/fast-gate` 2. Drop the workaround from the fast-batch brief — check: absent `--cop Sdlc/Structural/InwardDependency` in `plugins/os-sdlc/skills/fast-batch/references/batch-brief.md` ## Acceptance criteria 1. Given Signal TSV rows on stdin for a detector, when fast-gate runs with `--signal` and the detector reports no signal at those sites, then the gate passes. 2. Given a site that still has a signal, when fast-gate runs with `--signal`, then the gate fails and names the site. 3. Given the fast-batch brief, when a detector finding is gated, then the brief uses `--signal` and has no InwardDependency workaround. ## Origin - Trigger: fast-gate shipped in 05e4e1b7 (merged cde8a6b6); detector-named findings have no input. - Improvised this session: the brief uses `--cop Sdlc/Structural/InwardDependency` plus a second detector run. - Chain: workaround in brief ← fast-gate accepts only cop names ← DESIGN (plugins/os-sdlc/bin/fast-gate). - Root candidate: none found; searched fast-gate, --signal, detector, fast-batch, Signal TSV, brief - Where: plugins/os-sdlc/bin/fast-gate - Session: 3ff277d2-0942-49d9-8ac0-4e778200b1e2 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/3ff277d2-0942-49d9-8ac0-4e778200b1e2.jsonl VERDICT: CREATE
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#1237
No description provided.