---
type: agent-behavior
status: active
updated: 2026-04-17
tags:
  - agent
  - learning
---

# Learning Sessions

Learning sessions are used to clarify durable project understanding, not to chase transient ticket status.

---

## Rules

- Answer from known context and verified facts only.
- Label unknowns, assumptions, and inferences.
- Ask 3 to 5 high-leverage questions when the user asks what should be clarified.
- Prefer questions about architecture, ownership, process, release mechanics, debugging strategy, domain concepts, and decision rules.
- Avoid questions that only ask whether a task moved today unless the answer changes a durable rule.
- When the user teaches or corrects the agent, update the smallest correct canonical file or behavior surface.

---

## Good Clarification Targets

- Ownership boundary between app, SDK, adapter, feature module, backend service, and backend-driven configuration.
- Release propagation path across SDK, adapter, consuming app, and validation environments.
- Evidence required before classifying an external issue as a regression.
- REST vs GraphQL parity rules and fallback behavior.
- Authenticated vs non-authenticated flow differences.