feat: add spring ai retrieval sidecar
This commit is contained in:
@@ -62,3 +62,23 @@ The system SHALL preserve generated baseline reports in JSON and Markdown format
|
||||
#### Scenario: Baseline regeneration is documented
|
||||
- **WHEN** a developer changes golden cases, fixtures, or evaluator logic
|
||||
- **THEN** the repository SHALL explain how to regenerate the retrieval baseline reports
|
||||
|
||||
### Requirement: Retrieval evaluation SHALL compare current and sidecar retrieval paths
|
||||
The retrieval evaluation system SHALL provide an opt-in comparison between the existing retrieval path and the Spring AI sidecar retrieval path.
|
||||
|
||||
#### Scenario: Sidecar comparison report
|
||||
- **WHEN** sidecar comparison is run for the golden case set
|
||||
- **THEN** the report SHALL include per-case current-path top candidates and sidecar top candidates
|
||||
- **AND** it SHALL highlight source, breadcrumb, category, rank, and score-label differences
|
||||
|
||||
#### Scenario: Offline baseline remains unchanged
|
||||
- **WHEN** the fixture-based offline baseline evaluator is run
|
||||
- **THEN** it SHALL not require live Milvus, Spring Boot, or Spring AI sidecar configuration
|
||||
|
||||
### Requirement: Retrieval evaluation SHALL make sidecar readiness visible
|
||||
The sidecar comparison report SHALL show whether the Spring AI sidecar was runnable for the current environment.
|
||||
|
||||
#### Scenario: Sidecar unavailable
|
||||
- **WHEN** sidecar comparison is requested but the sidecar is disabled or unavailable
|
||||
- **THEN** the report SHALL mark sidecar status as unavailable
|
||||
- **AND** it SHALL keep current-path baseline results available for review
|
||||
|
||||
Reference in New Issue
Block a user