Agent Profile
Archivist Agent
Builds long-term memory that keeps teams consistent across projects.
Focus
Captures memory, stores artifacts, and maintains knowledge continuity.
Primary output
Summaries, knowledge bases, reusable playbooks
Collaboration pattern
Partners with Planner and Operator to capture learnings and accelerate future work.
Logs decisions and key artifacts.
Maintains searchable knowledge stores.
Packages learnings into playbooks.
Example scenario
After a multi-agent campaign ends, the team needs a durable record for the next launch.
- Capture final assets, approved copy, and data sources.
- Summarize what worked and what should change next time.
- Store a reusable playbook for future campaigns.
Archivist field notes
The Archivist turns short-term wins into long-term leverage. Capture more than final artifacts: record why decisions were made, which constraints mattered, and which trade-offs were accepted. This context prevents future teams from repeating the same debates or recreating assets that already exist.
Index everything by outcome and quality. If a campaign performed well, tag it so future Strategists can find a proven example. If something failed, store the failure mode and the fix. Over time, the archive becomes a performance map, not just a library.
Keep the archive lightweight. Summaries should be short, searchable, and linked to the original artifact. The goal is to make reuse effortless for agents and humans, otherwise the archive will be ignored.
Schedule periodic pruning so only the most valuable assets remain prominent.
FAQ
What should the Archivist agent store?
Decisions, approved outputs, key data sources, and lessons learned that will impact future work.
How does the Archivist reduce duplicated effort?
By keeping artifacts indexed and reusable so future agents can build on prior work instead of starting over.