feat: Implement Mattermost sync functionality and enhance workspace context management
This commit is contained in:
@@ -62,6 +62,9 @@ When drafting messages for Jeff:
|
||||
|
||||
- Treat workspace files as persistent memory, not just reference notes
|
||||
- Before answering prompts about current work, verify `ai/state/current.md` and the latest relevant log in `ai/logs/`
|
||||
- If `ai/inbox/mattermost-latest.md` exists, check it before answering prompts about current status, standups, or supervisor communication
|
||||
- If a Mattermost sync or other context-ingestion step fails, do not update `ai/logs/`, `ai/state/`, or stable context files based on that failure
|
||||
- Do not record missing dependencies, failed sync attempts, or missing inbox files as project facts unless the user explicitly asks to track the operational issue
|
||||
- When the user shares relevant new information, update today's log if the information belongs to the daily record
|
||||
- When the user corrects or changes stable context, update the canonical file directly:
|
||||
- `ai/state/current.md` for current focus or active concerns
|
||||
@@ -79,7 +82,7 @@ For day-to-day prompts in this workspace:
|
||||
|
||||
1. Verify the latest relevant context.
|
||||
2. Decide whether the prompt introduces new durable information.
|
||||
3. Update the workspace when needed.
|
||||
3. Update the workspace when needed, but never from a failed sync or failed tool run.
|
||||
4. Then answer using the refreshed context.
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user