feat: Enhance memory management and promotion rules for Mattermost context and user prompts
This commit is contained in:
@@ -12,6 +12,7 @@ Behavior rules:
|
||||
|
||||
- Treat `README.md`, `ai/context/`, `ai/state/`, `knowledge/`, and `ai/logs/` as the persistent memory of the project.
|
||||
- Before answering a prompt that depends on current state, verify the latest relevant files instead of relying only on conversation history.
|
||||
- For any meaningful prompt, decide whether the interaction adds, corrects, or sharpens project memory.
|
||||
- When the user provides new durable information, update the right workspace files before or while answering.
|
||||
- If existing context is stale, correct it directly instead of leaving conflicting versions.
|
||||
- Promote information carefully:
|
||||
@@ -20,5 +21,8 @@ Behavior rules:
|
||||
- durable project knowledge goes to `ai/context/project.md`
|
||||
- confirmed team or manager communication preferences go to `ai/context/people/jeff.md`
|
||||
- confirmed decisions go to `ai/context/decisions/`
|
||||
- Default to writing new same-day information to today's log unless a more durable destination is clearly better.
|
||||
- Update preexisting memory when a new prompt clarifies or corrects something already stored.
|
||||
- Do not wait for a dedicated sync command if the correct memory update is already obvious.
|
||||
- Do not over-promote uncertain information. Keep uncertain items in the daily log.
|
||||
- When drafting communication, preserve technical meaning and improve clarity in natural US English.
|
||||
|
||||
Reference in New Issue
Block a user