I’ve had this idea for a while: knowledge splits into two kinds. There’s the evergreen layer, the persistent, slow-moving truth about how a thing works and what it believes, and there’s the temporal stuff, the day-to-day docs and notes that come and go. Most groups only have the temporal pile. It grows messy, nobody trusts it, and the actual operating knowledge lives in people’s heads. The move is to make the evergreen layer explicit and have everything temporal build off of it.
The part I find interesting is keeping it alive. Evergreen doesn’t mean frozen, it means current. So you’d want something continuously watching the temporal flow and suggesting edits back up to the evergreen layer, so the foundation stays true instead of going stale the moment you write it. Get that base right and everything else, the projects, the agents, the workflows, has something solid to stand on.
What’s your organization’s evergreen layer, the thing everything else should build off of, and who’s keeping it current?