| Pattern list as guidance | IDs do not show the recognizable situation, first useful result or blocker, choice-changing distinction, or return. | Publish those ordinary values and point to the direct pattern; add an exact expansion only when the prose cannot remain truthful without it. |
| Internal vocabulary as the front door | The entry starts with PatternIDs, FPF kinds, or quality and conformance terms before the reader can recognize the work. | Put the ordinary working situation and first useful result first, then add only the precision the branch uses. |
| Ungrounded public value | The entry promises broad help but shows no concrete result or blocker and no direct-pattern distinction that changes the next action. | Name the need, imaginable first result or blocker, direct pattern, and ordinary boundary. |
| Card unit, guidance, key, and form collapsed | A heading, semantic key, six fields, or mantra is treated as proof that a card unit was honestly selected or that the form is the guidance or direct pattern. | Apply the mnemonic-gain test, keep the four claims separate, and return substantive authority to the direct pattern. |
| Card-per-pattern, card-by-length, or example-set-as-coverage | Every pattern receives a card, phrase length decides the form, or the displayed topics are treated as the product’s usable scope. | Compare the same truthful content without a mantra. Select a card only when repeating it restores a choice-changing cross-pattern path; otherwise keep the smaller entry or locator. State that examples are non-exhaustive and use the index or direct patterns for coverage. |
| Fixed three-entry shortlist | Interface convenience becomes ontology. | Use any finite inspected set bounded by the current question and stop condition. |
| Walkthrough as workflow | Presentation order becomes a fixed work sequence. | State continuation conditions and use CGUS only when its structure is actually admitted. |
| README as pattern body | Public copy accumulates methods and conformance doctrine. | Link to the expansion and direct pattern; keep method authority there. |
| Build manifest as reader front matter | Anchors, source paths, digests, machine identity fields, or generation warnings delay the first working choice and make the publication read like compiler output. | Keep reproducibility evidence in builder output, package evidence, or a separately justified manifest; use E.11.PFP for the reader-facing edition and dependency fields and their position. |
| ToC as a mini-method catalogue | Separate Use when, first-move, result, and boundary columns copy changing pattern semantics into navigation and drift from the bodies. | Use E.11.PFP’s index-row profile; put practical entry and first-result guidance in the Readme and authoritative method content in the pattern body. |