Principlev1

Document not only what tools you use but the complete

Document not only what tools you use but the complete routing rules, processing workflows, decision principles, and evolution history of your knowledge management system, because undocumented systems cannot be debugged, improved, transferred, or rebuilt after failure.

Why This Is a Principle

Grounds to Externalization Exposes Hidden Structure (externalization exposes gaps and assumptions), Knowledge that exists only in tacit form degrades without (tacit knowledge degrades without detection), and Double-loop learning requires questioning the framework (double-loop learning requires questioning framework itself). The principle prescribes documenting the meta-level—not just content but the system that manages content. This is what distinguishes system documentation from mere tool inventory.

Source Lessons

L-0198

Externalize your system itself

Document your process for managing knowledge — not just the knowledge itself. Your system should be explicit enough that you could rebuild it from documentation alone.

Connections

Derived From (3)

AxiomExternalization Exposes Hidden Structure AxiomKnowledge that exists only in tacit form degrades without AxiomDouble-loop learning requires questioning the framework

Back to Concepts