Public Access
Strengthen workflow automation diagnostics
This commit is contained in:
@@ -8,6 +8,8 @@ The local rules file SHALL be ignored by source control.
|
||||
|
||||
Rules SHALL be evaluated against the latest meeting note data read from disk for each event.
|
||||
|
||||
Meeting Assistant SHALL expose a diagnostic endpoint that reloads application configuration so workflow automation configuration changes can be picked up without restarting the application.
|
||||
|
||||
#### Scenario: Missing rules file is ignored
|
||||
- **WHEN** Meeting Assistant handles a meeting event and no configured rules file exists
|
||||
- **THEN** it leaves the meeting note and assistant context unchanged
|
||||
@@ -17,6 +19,12 @@ Rules SHALL be evaluated against the latest meeting note data read from disk for
|
||||
- **WHEN** Meeting Assistant creates a meeting note without attendees
|
||||
- **THEN** it adds the configured attendee to the meeting note
|
||||
|
||||
#### Scenario: Workflow configuration is reloaded diagnostically
|
||||
- **GIVEN** the workflow automation configuration has changed on disk
|
||||
- **WHEN** the diagnostic workflow reload endpoint is called
|
||||
- **THEN** Meeting Assistant reloads application configuration without restarting
|
||||
- **AND** future workflow events use the reloaded workflow automation configuration
|
||||
|
||||
### Requirement: Meeting automation rules support lifecycle triggers
|
||||
Meeting Assistant SHALL support rule triggers for `created`, `state_transition`, and `speaker_identified`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user