A living document — also known as a dynamic document — is a continually edited and updated document, in contrast to "dead" or "static" documents that are written once and locked against the evolving subject they describe.
Platforms like 📝Wikipedia and 📝MythOS are fluid compendiums built on the idea that 📝Knowledge Management is 📝A Process, Not An Activity — content is structured to invite ongoing revision rather than declared finished, and value compounds with each pass. The Encyclopedia Britannica, by contrast, exemplifies the static model: authoritative at publication but frozen against the evolving subject it describes.
The form maps to a broader set of "living" patterns in how knowledge, organizations, and software now operate. Open-source codebases, internal wikis, version-controlled spec documents, and personal knowledge graphs share the same posture — releasing fast, accepting revision, and trusting that the next edit will be better-informed than the last. As 📝Shura Kotlerman put it: "When it comes to living documents, 'ready' is better than 'done'."
"Living document" was the language that felt most resonant for what a MythOS memo actually is — short, informal, alive. It slots cleanly into a broader "living" schema I lean on: companies that mimic life, being a human being rather than a human doing. When the artifact is alive, the knowledge management around it gets to be alive too.