# Brief: aiops-alert-scope-control

## Background

After `aiops-traceable-diagnosis-entry`, AIOps can be triggered by payload and replayed through trace. Runtime verification showed one semantic gap: payload mode still produced a broad report over all active mock alerts.

## Goal

Make AIOps scope explicit:

- Payload present -> targeted diagnosis for the supplied alert.
- Payload absent -> automatic active-alert discovery and diagnosis.

## Scope

- In scope:
  - `AiOpsService.buildTaskPrompt(...)` scope rules.
  - Focused tests.
  - Demo acceptance wording.
- Out of scope:
  - Verifier integration.
  - Java-side filtering of tool results.
  - API shape changes.
  - Database changes.

## Related OpenSpec

`openspec/changes/aiops-alert-scope-control/`