E.4.PFR:1.1 - Problem

Two opposite failures are common. Flattening everything into “related patterns” or “dependency” hides relation function and change effect. Requiring a PFR row for every load-bearing relation turns a readable assertion into a record-first ontology and encourages a fictitious fact that one pattern contains the defining content for or governs the other content.