107 lines
3.0 KiB
Markdown
107 lines
3.0 KiB
Markdown
# Memory Promotion Rules
|
|
|
|
## Goal
|
|
|
|
Keep workspace memory current automatically without asking the user what to promote after every successful sync.
|
|
|
|
---
|
|
|
|
## Default Rule
|
|
|
|
When new Mattermost context is explicit, project-relevant, and high-confidence, promote it automatically.
|
|
|
|
Do not ask for promotion confirmation by default.
|
|
|
|
If a fact is ambiguous, skip it or keep it only in the daily log with appropriate qualifiers.
|
|
|
|
---
|
|
|
|
## File Selection
|
|
|
|
### Promote to `ai/logs/YYYY-MM-DD.md`
|
|
|
|
Use the daily log for:
|
|
|
|
- concrete same-day work updates
|
|
- story creation, sizing, approval, and scope updates
|
|
- manager-approved wording or root-cause framing tied to current work
|
|
- confirmed version checks tied to active work
|
|
- reproduction findings that are useful now but may still evolve
|
|
|
|
Daily logs are the default destination for most promoted Mattermost facts.
|
|
|
|
### Promote to `ai/state/current.md`
|
|
|
|
Use current state only for facts that materially affect active work over the next few days, such as:
|
|
|
|
- approved active story scope
|
|
- confirmed current debugging constraints
|
|
- current reproduction conditions that change how the work is approached
|
|
- near-term priorities confirmed by manager communication
|
|
|
|
Do not copy every daily update into current state.
|
|
|
|
### Promote to `ai/context/project.md`
|
|
|
|
Use project context only for durable project knowledge that should survive beyond the current work window, such as:
|
|
|
|
- stable architecture constraints
|
|
- recurring debugging truths
|
|
- persistent testing limitations
|
|
- enduring behavior of REST, GraphQL, XFlow, auth, or entry points
|
|
|
|
Do not promote story-specific daily movement into project context unless it changes durable project understanding.
|
|
|
|
### Promote to `ai/context/decisions/*.md`
|
|
|
|
Use decisions only for explicit confirmed decisions with medium or long-term impact.
|
|
|
|
---
|
|
|
|
## Do Not Promote
|
|
|
|
Do not record these as project memory:
|
|
|
|
- tooling activity
|
|
- sync status
|
|
- missing dependencies
|
|
- empty inbox situations
|
|
- reminders or urgency without project substance
|
|
- unapproved drafts
|
|
- generic chat noise
|
|
|
|
---
|
|
|
|
## Confidence Rules
|
|
|
|
Auto-promote when the signal is high-confidence, for example:
|
|
|
|
- Jeff explicitly approves something
|
|
- a Jira story number, title, points, or scope is explicitly confirmed
|
|
- a version is stated directly and tied to the active project
|
|
- a reproduction condition is clearly stated with scope qualifiers
|
|
|
|
If confidence is mixed:
|
|
|
|
- prefer the daily log
|
|
- preserve qualifiers such as "appears", "currently", or "for authenticated users"
|
|
- avoid promoting to stable project context
|
|
|
|
---
|
|
|
|
## Example Policy
|
|
|
|
Given Mattermost updates like:
|
|
|
|
- PDIAP-15836 created and sized at 8 points
|
|
- Jeff approved a story title
|
|
- REST-removal scope was approved
|
|
- XFlowViewMaker 0.5.0 is already in Fid4
|
|
- AO DOB validation issue appears auth-only in TeenIdentityCheck
|
|
|
|
Automatic behavior should be:
|
|
|
|
- add all of them to today's log if they are relevant to today's work
|
|
- promote only the currently actionable subset to `ai/state/current.md`
|
|
- keep story-specific details out of `ai/context/project.md` unless they reveal a durable project rule
|