# Insufficient Evidence Query Suggestions

## Problem

Operators can reach a case where external search has run, but the evidence is still too thin to make a confident approval, hold, or rejection decision. Today the console shows raw evidence and query history, but it does not suggest a concrete next action when the evidence is insufficient.

## Goal

Add a lightweight workbench guide that detects insufficient evidence and generates safe follow-up query suggestions. The system must not run external searches automatically. It should only prepare likely useful queries and let the operator decide whether to execute one.

## User Experience

When the selected case has weak or sparse evidence, the evidence workbench shows a "근거 보강 추천" panel above the evidence groups. The panel explains that the current evidence is insufficient and shows a few suggested Naver query buttons.

Clicking a suggestion:

- switches to the workbench query tab;
- fills the existing manual query input;
- selects the normalized operator search provider;
- leaves execution to the operator through the existing submit button.

If evidence is already sufficient, the panel stays hidden.

## Evidence Sufficiency Rule

The first version uses a conservative client-side heuristic:

- direct image/page matches are strong evidence;
- Naver or Google searchable evidence is supporting evidence;
- a case is insufficient when it has no strong direct match or has fewer than two searchable evidence items;
- query suggestions are only shown when there is at least some indication that search has run, such as query history, provider state, or searchable evidence.

This avoids blocking decisions and avoids adding backend state.

## Query Generation

Suggestions are generated from the selected submission title and deduplicated against existing query history. The initial templates are:

- title
- title + " 저작권"
- title + " 공식"
- title + " 이미지 출처"

The list is capped at four suggestions.

## Scope

In scope:

- static operator GUI markup, script, and styles;
- client-side insufficient evidence assessment;
- query suggestion rendering;
- click behavior that fills the manual query form;
- static tests for the UI contract.

Out of scope:

- automatic external search execution;
- backend API changes;
- hard decision blocking;
- machine-learned query generation.

## Verification

Run the operator static suite:

```powershell
python -m pytest tests\operator_gui\test_static_workbench.py
```
