Public Access
Validate workflow rule writes
This commit is contained in:
@@ -18,11 +18,11 @@ The settings/logs agent SHALL be configured from the summarizer agent settings b
|
||||
|
||||
The settings/logs agent SHALL include the workflow engine documentation in its system prompt and SHALL receive read, write, and search tools scoped to the configured workflow rules file.
|
||||
|
||||
The rules editor `write_rules` tool SHALL append to the configured workflow rules file by default and SHALL validate the complete resulting YAML document before writing it.
|
||||
The rules editor `write_rules` tool SHALL append to the configured workflow rules file by default and SHALL validate the complete resulting YAML document as supported workflow rules before writing it.
|
||||
|
||||
The rules editor `write_rules` tool SHALL replace the whole configured workflow rules file only when `replace_file` is true.
|
||||
|
||||
The rules editor `write_rules` tool SHALL refuse invalid YAML without changing the configured workflow rules file.
|
||||
The rules editor `write_rules` tool SHALL refuse invalid YAML, unsupported workflow rule shape, or workflow step Razor templates that fail against the workflow template model without changing the configured workflow rules file and SHALL return enough detail for the agent to fix and retry.
|
||||
|
||||
The settings/logs agent SHALL receive speaker identity tools to search/list, read, create, update, delete, and merge identities in the local speaker identity database.
|
||||
|
||||
@@ -115,11 +115,12 @@ Meeting Assistant SHALL provide a diagnostic endpoint that opens the settings/lo
|
||||
- **WHEN** the rules editor writes valid YAML with `replace_file` set to true
|
||||
- **THEN** Meeting Assistant replaces the complete rules file with the supplied YAML
|
||||
|
||||
#### Scenario: Rules editor refuses invalid YAML
|
||||
#### Scenario: Rules editor refuses invalid workflow rules
|
||||
- **GIVEN** a configured workflow rules file with valid existing rules
|
||||
- **WHEN** the rules editor writes YAML that would make the file invalid
|
||||
- **WHEN** the rules editor writes YAML that would make the file invalid, unsupported by the workflow engine, or contain a malformed step value Razor template
|
||||
- **THEN** Meeting Assistant refuses the write
|
||||
- **AND** keeps the existing rules file unchanged
|
||||
- **AND** returns the invalid rule or field plus supported values when available
|
||||
|
||||
#### Scenario: Rules editor can manage speaker identities
|
||||
- **GIVEN** the speaker identity database contains speaker identities and samples
|
||||
|
||||
Reference in New Issue
Block a user