Skip to main content
Memory is what a campaign leaves for the next agent: lessons, documents and the orchestrator’s journal. An orchestrator session that loses its context writes to the journal as it goes, and the next session reads it first:
A journal line has at most 280 bytes, and nobody can change it later. Without --campaign, it goes to the campaign of the current directory. The piloop-operate skill runs piloop wake first.

​
Lessons

A lesson is the conclusion about one family of ideas (ideas.family), such as “stronger generic compressor”. The closing watchdog writes one for each family that the campaign tried. An agent writes one with SQL:
A newer lesson for the same family replaces the older one. The briefs show the current lessons of every campaign on the same repo, also from other clones of it, in the lessons section.

​
Documents

Name the reports and notes that agents should be able to search:
piloop init and the stop of a campaign copy them into the documents table. An edited file is a new version.
Every agent of every campaign can read the documents. Never name one that comes from validation or test data.
[plugins.memory] selects the memory’s provider. The built-in local keeps it in the home’s database.