docs: archive rag and aiops query changes
This commit is contained in:
@@ -42,3 +42,20 @@ The system SHALL continue using existing `agent_step` and `tool_invocation` pers
|
||||
#### Scenario: AIOps uses evidence tools
|
||||
- **WHEN** the AIOps flow calls available evidence tools
|
||||
- **THEN** existing hooks and recorders persist agent steps and tool invocations under the resolved AIOps session id
|
||||
|
||||
### Requirement: AIOps payload prompts SHALL include a recommended knowledge query
|
||||
When an AIOps request includes alert payload fields, the system SHALL include a deterministic recommended knowledge retrieval query in the prompt sent to the Agent flow.
|
||||
|
||||
#### Scenario: Payload-targeted prompt includes knowledge query
|
||||
- **WHEN** an AIOps request contains alert name, service, severity, or description
|
||||
- **THEN** the generated task prompt SHALL include a recommended `lookup_knowledge` query derived from the supplied payload fields
|
||||
|
||||
#### Scenario: Query skips blank fields
|
||||
- **WHEN** some AIOps payload fields are blank
|
||||
- **THEN** the recommended knowledge query SHALL omit those blank fields
|
||||
- **AND** it SHALL preserve the non-blank alert-specific terms
|
||||
|
||||
#### Scenario: Auto-discovery prompt does not invent payload query
|
||||
- **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
|
||||
|
||||
Reference in New Issue
Block a user