feat: Enhance learning session guidelines to prioritize durable understanding and high-leverage questioning
This commit is contained in:
@@ -38,6 +38,9 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
|
||||
## Ingestion Rules
|
||||
|
||||
- Treat Mattermost, Slack history, and direct prompts as potential memory sources.
|
||||
- Treat learning sessions as durable-understanding sessions, not status refreshes.
|
||||
- In learning sessions, prioritize architecture, ownership, release mechanics, debugging strategy, domain concepts, and process rules.
|
||||
- Avoid promoting transient ticket status from learning sessions unless it exposes a reusable rule.
|
||||
- Do not promote failed syncs or tooling errors as project facts.
|
||||
- Promote repeated durable patterns from historical archives into stable context when confidence is high.
|
||||
- Keep old status-only details archive-only unless they still change current understanding.
|
||||
|
||||
Reference in New Issue
Block a user