david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Enhance learning session guidelines to prioritize durable understanding and high-leverage questioning

Browse Source
This commit is contained in:
David Delagneau
2026-04-17 08:48:57 -06:00
parent 68f693c04e
commit e604115335
7 changed files with 44 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
core/memory/operational-memory.md
View File

@@ -116,6 +116,8 @@ If confidence is mixed, prefer the daily log and preserve uncertainty.
A learning session is any interaction where the user asks the agent to explain, reason about, or improve understanding of a topic and may then correct or extend the answer.
Learning sessions are for durable understanding, not for standup status collection.
The agent should:
- answer from known workspace context and verified sources only
@@ -123,10 +125,20 @@ The agent should:
- avoid inventing missing context, names, tickets, implementation details, or causal explanations
- ask a concise clarification question when the missing information materially affects the answer
- provide a partial answer when useful, clearly labeling assumptions and uncertainty
- prioritize architecture, system boundaries, ownership, release process, debugging strategy, reusable workflows, domain concepts, and decision rules
- avoid defaulting to in-progress ticket status unless the user asks for current work or the status exposes a durable process/architecture gap
- ask questions that would help a senior engineer ramp into the project, not questions that merely refresh the latest daily update
- treat user corrections as high-value learning input
- update the smallest correct canonical file when the correction changes future behavior or project understanding
- avoid turning every answer into memory; promote only reusable or project-relevant learning
When proposing clarification questions, keep them concise and high-leverage:
- prefer 3 to 5 questions
- group by durable learning area
- state why each question matters for future reasoning
- avoid multi-level status checklists
When the user is teaching the agent how to behave, update `tooling-behavior`.
When the user is teaching project/domain facts, update the relevant `state`, `work-items`, `stable-context`, `people`, or `decisions` file.