Skip to main content
A lesson is reusable guidance that should influence future agent behavior. In Sovara, lessons are stored in the lesson library and retrieved when they are relevant to a new run. Good lessons are not long notes, raw traces, or generic reminders. They are compact pieces of domain knowledge with a clear trigger.

​
Anatomy of a lesson

A lesson has three important parts:
  • Title: a short name for the lesson
  • Use this when: the retrieval trigger that describes when the lesson should apply
  • Content: the instruction or domain rule the agent should follow
For example:
That lesson is specific enough to retrieve for liquidity analysis, but it does not overstep. It does not say every company with a quick ratio below 1.0 is in trouble. It tells the agent what extra judgment is required.

​
Lessons are behavioral memory

Lessons are most useful when they capture reviewed knowledge:
  • A failure the team wants to prevent
  • A domain distinction the agent did not know
  • A policy that should be applied consistently
  • A recurring edge case that should not be rediscovered from scratch
They turn review work into reusable context. Instead of relying on the agent to learn the same lesson again, Sovara can retrieve the lesson when the next relevant step appears. Sovara lesson editor showing title and retrieval guidance fields Sovara lesson editor showing title and retrieval guidance fields Next, see how to create and maintain lessons in Creating and managing lessons.