From 63b62b28a24d0f1e33e9e69d846fc4efed569add Mon Sep 17 00:00:00 2001 From: aruo <40362743+zyongxin@users.noreply.github.com> Date: Sun, 5 Jul 2026 14:01:33 +0800 Subject: [PATCH] docs: archive aiops lightweight verifier change --- .../.openspec.yaml | 0 .../design.md | 0 .../proposal.md | 0 .../aiops-traceable-diagnosis-entry/spec.md | 0 .../tasks.md | 0 .../aiops-traceable-diagnosis-entry/spec.md | 21 +++++++++++++++++++ 6 files changed, 21 insertions(+) rename openspec/changes/{aiops-lightweight-verifier => archive/2026-07-05-aiops-lightweight-verifier}/.openspec.yaml (100%) rename openspec/changes/{aiops-lightweight-verifier => archive/2026-07-05-aiops-lightweight-verifier}/design.md (100%) rename openspec/changes/{aiops-lightweight-verifier => archive/2026-07-05-aiops-lightweight-verifier}/proposal.md (100%) rename openspec/changes/{aiops-lightweight-verifier => archive/2026-07-05-aiops-lightweight-verifier}/specs/aiops-traceable-diagnosis-entry/spec.md (100%) rename openspec/changes/{aiops-lightweight-verifier => archive/2026-07-05-aiops-lightweight-verifier}/tasks.md (100%) diff --git a/openspec/changes/aiops-lightweight-verifier/.openspec.yaml b/openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/.openspec.yaml similarity index 100% rename from openspec/changes/aiops-lightweight-verifier/.openspec.yaml rename to openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/.openspec.yaml diff --git a/openspec/changes/aiops-lightweight-verifier/design.md b/openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/design.md similarity index 100% rename from openspec/changes/aiops-lightweight-verifier/design.md rename to openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/design.md diff --git a/openspec/changes/aiops-lightweight-verifier/proposal.md b/openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/proposal.md similarity index 100% rename from openspec/changes/aiops-lightweight-verifier/proposal.md rename to openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/proposal.md diff --git a/openspec/changes/aiops-lightweight-verifier/specs/aiops-traceable-diagnosis-entry/spec.md b/openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/specs/aiops-traceable-diagnosis-entry/spec.md similarity index 100% rename from openspec/changes/aiops-lightweight-verifier/specs/aiops-traceable-diagnosis-entry/spec.md rename to openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/specs/aiops-traceable-diagnosis-entry/spec.md diff --git a/openspec/changes/aiops-lightweight-verifier/tasks.md b/openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/tasks.md similarity index 100% rename from openspec/changes/aiops-lightweight-verifier/tasks.md rename to openspec/changes/archive/2026-07-05-aiops-lightweight-verifier/tasks.md diff --git a/openspec/specs/aiops-traceable-diagnosis-entry/spec.md b/openspec/specs/aiops-traceable-diagnosis-entry/spec.md index d5b8a88..2f0c1c1 100644 --- a/openspec/specs/aiops-traceable-diagnosis-entry/spec.md +++ b/openspec/specs/aiops-traceable-diagnosis-entry/spec.md @@ -59,3 +59,24 @@ When an AIOps request includes alert payload fields, the system SHALL include a - **WHEN** an AIOps request does not include alert payload fields - **THEN** the generated task prompt SHALL remain in auto-discovery mode - **AND** it SHALL not include a payload-derived recommended knowledge query + +### Requirement: AIOps sessions SHALL persist lightweight rule evaluation +When an AIOps final report is persisted, the system SHALL evaluate it with deterministic AIOps-specific quality rules and store the result in session self-evaluation. + +#### Scenario: Payload-focused report is evaluated +- **WHEN** an AIOps session has alert payload fields and a final report is persisted +- **THEN** the system SHALL evaluate whether the report mentions the supplied alert and service +- **AND** it SHALL store the result under `self_evaluation.aiops_rule_evaluation` + +#### Scenario: Evidence coverage is evaluated +- **WHEN** an AIOps final report is evaluated +- **THEN** the system SHALL check whether evidence tool invocations such as `lookup_knowledge`, `query_metrics`, or `query_logs` were persisted for the session + +#### Scenario: Evaluation is traceable +- **WHEN** the diagnosis trace API returns an AIOps session +- **THEN** the session self-evaluation payload SHALL include `aiops_rule_evaluation` when it has been generated + +#### Scenario: Evaluation uses stable verdicts +- **WHEN** AIOps rule evaluation completes +- **THEN** it SHALL produce a verdict from `PASS`, `WARN`, or `FAIL` +- **AND** it SHALL include check details and a human-readable rationale