docs: archive rag and aiops query changes
This commit is contained in:
@@ -93,3 +93,23 @@ The offline RAG retrieval baseline SHALL remain runnable after the main retrieva
|
||||
#### Scenario: Baseline is checked during migration
|
||||
- **WHEN** the VectorStore integration change is implemented
|
||||
- **THEN** the existing offline baseline evaluator SHALL be run and its generated report noise SHALL not be committed unless the baseline intentionally changes
|
||||
|
||||
### Requirement: Retrieval evaluation SHALL provide live post-reindex acceptance
|
||||
The retrieval evaluation system SHALL provide an opt-in live acceptance flow for validating retrieval behavior after embedding input changes require a knowledge-base reindex.
|
||||
|
||||
#### Scenario: Live acceptance requires a running service
|
||||
- **WHEN** live retrieval acceptance is run
|
||||
- **THEN** it SHALL call the configured Spring Boot retrieval endpoint
|
||||
- **AND** it SHALL not be required by the offline fixture baseline
|
||||
|
||||
#### Scenario: Live acceptance records retrieval evidence
|
||||
- **WHEN** a live retrieval case is executed
|
||||
- **THEN** the report SHALL include the query, requested topK, result count, top candidate titles or sources, score labels, and raw response fields needed for review
|
||||
|
||||
#### Scenario: Reindex prerequisite is documented
|
||||
- **WHEN** a developer prepares to validate breadcrumb-aware embedding behavior
|
||||
- **THEN** the repository SHALL explain that existing vectors must be reindexed before live validation can reflect the new embedding text
|
||||
|
||||
#### Scenario: Live report is reviewable
|
||||
- **WHEN** the live acceptance script completes
|
||||
- **THEN** it SHALL write JSON and Markdown outputs that can be inspected or attached to interview evidence
|
||||
|
||||
Reference in New Issue
Block a user