# Brief: aiops-traceable-diagnosis-entry

## Background

The MVP chat diagnosis path is now traceable through `diagnosis_session`, `agent_step`, `tool_invocation`, and `GET /api/diagnosis/{sessionId}/trace`. The older `/api/ai_ops` endpoint still acts like a standalone SSE demo: it accepts no alert payload, generates an internal session id, and does not make trace replay obvious to callers.

## Goal

Turn AIOps into an alert-triggered diagnosis entry point that shares the same evidence and trace story as the main MVP, without rewriting the whole AIOps flow.

## Scope

- In scope:
  - Optional AIOps alert request body.
  - Stable request/session id propagation.
  - Persisted AIOps query summary and final answer.
  - SSE session id event.
  - Demo documentation and focused tests.
- Out of scope:
  - Full AIOps and ChatService unification.
  - AIOps Verifier integration.
  - Database schema changes.
  - Sensitive configuration cleanup.
  - Fully offline runtime.

## Related OpenSpec

`openspec/changes/aiops-traceable-diagnosis-entry/`