Memory, documents, and the shared library
Gezel memory
Each gezel keeps a diary. As you work together they save notes — decisions you made, preferences you expressed, lessons learned — into daily memory files they can search later. Ask your copywriter for "that tagline direction we agreed on in March" and they can actually look it up.
Memories are per-gezel and per-project: your reviewer's notes about code style don't leak into your researcher's notes about sources.
The document library
Documents are shared knowledge — the things every gezel should know. Your company boilerplate, your house style guide, the family holiday schedule. The library has two levels:
The shared library — available to every gezel in every project.
Project documents — the About and Mission Objectives of each project, plus anything else scoped to just that work.
Gezels can read and (where you allow it) write documents themselves, so the library grows as your crew works.
The history log
Gezel keeps an audit log of meaningful events: who created which gezel, when a project's mission changed, which tools ran. The History tab lets you filter and search it — and your gezellen can search it too, which means "did anyone change the mission this week?" is a question they can answer truthfully rather than guess at.
Everything is a file
Memories are markdown files. Documents are files. The history log is a file. If you ever want to see exactly what gezel knows, open the gezel home folder and read it — nothing is hidden inside a database you can't inspect. The Where files live article maps it all.