E.8.ML:2 - Problem

Source order, a procedure diagram or a repository taxonomy can become the pattern architecture without a separate decision. Every chapter is then treated as a Method part, every pattern as a MethodDescription, and every link as the next step in Work.

The opposite failure is a bag of useful patterns with no explanation of when they contribute together. A user must reconstruct prerequisites, alternatives, conflicts and source returns from private authoring notes. A whole-framework introduction can hide the same problem when it gives only labels and no practical answer.