27 lines
1.6 KiB
Markdown
27 lines
1.6 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Executor SHALL avoid duplicate playbook reads in one diagnosis path
|
|
The system SHALL prevent repeated reads of the same selected diagnosis playbook during a single Executor diagnosis path unless a new retry round explicitly requests a fresh playbook read.
|
|
|
|
#### Scenario: Executor has already read the selected skill
|
|
- **WHEN** the Executor has already called `read_skill` for the selected skill in the current diagnosis path
|
|
- **THEN** the Executor SHALL continue using the already loaded playbook instructions
|
|
- **AND** it SHALL NOT call `read_skill` again for the same skill in that path
|
|
|
|
#### Scenario: Retry round may read selected skill again
|
|
- **WHEN** ChatService starts a distinct retry round after Verifier requests evidence supplementation
|
|
- **THEN** the Executor MAY call `read_skill` again for the selected skill
|
|
- **AND** the repeated read SHALL be attributable to the new round rather than the same Executor path
|
|
|
|
### Requirement: Live traces SHALL expose skill selection boundaries
|
|
The system SHALL make the Planner and Executor skill boundary auditable from persisted agent steps and logs.
|
|
|
|
#### Scenario: Planner selects without reading skill body
|
|
- **WHEN** a Planner step selects a diagnosis playbook
|
|
- **THEN** the persisted Planner output SHALL include the selected skill name
|
|
- **AND** the Planner step SHALL NOT include a `read_skill` tool call
|
|
|
|
#### Scenario: Executor reads selected skill
|
|
- **WHEN** the Executor starts a playbook-backed diagnosis
|
|
- **THEN** the persisted Executor step SHALL show `read_skill` for the selected skill before evidence-tool execution
|