Why does inheritance hierarchy fail?

The most common reason inheritance hierarchy fails: Blind inheritance — accepting every property that propagates from parent to child without examining whether it fits the child context. This shows up as teams following organizational processes that make no sense for their specific work, as note-takers applying folder-level tags to notes where those tags are irrelevant, as thinkers adopting the assumptions of their intellectual tradition without testing them against their own experience. The opposite failure is equally dangerous: rejecting all inheritance and re-deriving every property from scratch at every level, which destroys the efficiency that hierarchy was supposed to provide.

The fix: Choose a hierarchy you operate within — your organization, your note-taking system, your file structure, or your belief system. Identify three properties that propagate from a higher level to a lower level. For each one, answer: (1) Is this property explicitly stated or implicitly assumed? (2) Does it serve the child level well, or does it create friction? (3) If you removed the parent, would you independently choose this property at the child level? Any property where the answer to question 3 is 'no' is an inheritance candidate for override — which you will learn to handle in L-0273.

The underlying principle is straightforward: Child items often inherit properties from their parent — be aware of what propagates.