Public Access
feat: use assistant context as meeting memory
PR and Push Build/Test / build-and-test (push) Successful in 9m34s
PR and Push Build/Test / build-and-test (push) Successful in 9m34s
This commit is contained in:
@@ -362,3 +362,16 @@ Meeting Assistant SHALL provide a diagnostic endpoint that opens the workflow ru
|
||||
- **GIVEN** the rules editor chat window content fits without scrolling or is already near the bottom
|
||||
- **WHEN** a new user or assistant message is appended
|
||||
- **THEN** the conversation scrolls to the bottom of the newly rendered message content
|
||||
|
||||
### Requirement: Interactive agent uses assistant context as meeting memory
|
||||
The interactive agent window instructions SHALL identify each assistant context file as meeting-specific memory.
|
||||
|
||||
When the user asks the interactive agent to fix or investigate a meeting or summary, the instructions SHALL direct the agent to read the matching assistant context for clues about problems, missing information, assumptions, prior fixes, and conclusions.
|
||||
|
||||
After repairing a meeting or summary, the instructions SHALL direct the agent to append a concise record of its fixes and conclusions to the matching assistant context.
|
||||
|
||||
#### Scenario: Interactive agent repairs a meeting artifact
|
||||
- **GIVEN** a meeting has an assistant context file
|
||||
- **WHEN** the user asks the interactive agent to fix that meeting or its summary
|
||||
- **THEN** the agent instructions direct it to inspect the matching assistant context for relevant meeting-specific memory
|
||||
- **AND** direct it to append its fixes and conclusions to that assistant context
|
||||
|
||||
Reference in New Issue
Block a user