Evergreen record

An evergreen record is a small, reusable lesson or fact written to stay useful over time, lifted out of its original source so future work can reuse it without carrying the temporary detail forward.

An evergreen record is a small, reusable lesson or fact written to stay useful over time, lifted out of its original source so future work can reuse it without carrying the temporary detail forward. The point is to keep the durable idea and drop the one-time context around it. Say a long planning call ends with the realization that your team approves changes faster when each request lists its rollback step. The raw transcript is full of names, tangents, and timing that will not matter next month. You ask the assistant to pull out the durable rule as one standalone note titled by the lesson, keep a link back to the call, and discard the rest. That one note now applies to the next request, and the one after that.

Builder example

If your assistant only ever reads raw transcripts and chat logs, it keeps rediscovering the same lessons and pasting back stale specifics. Tell it to write each recurring insight as its own short, titled record that names the lesson plainly. A support team that turns every repeated fix into one evergreen record builds a base the assistant can answer from directly, so the next similar question gets the settled answer instead of a fresh guess from noisy history.

Common confusion: An evergreen record holds a durable lesson written to be reused on its own. A raw note or transcript holds the original moment with all its one-time detail. What separates them is the rewrite: an evergreen record has been lifted out and titled by the idea, so it stays useful long after the source moment is forgotten.