E11-1 | Situation first | Public wording begins with a recognizable working situation before PatternIDs, internal topology, or quality vocabulary. |
E11-2 | Useful result before apparatus | The reader can recover the first useful result or blocker, direct pattern or plausible set, and ordinary stop or return before any optional exact expansion. |
E11-3 | One publication job | README carries public first-entry situations and first results; Preface explains cross-cutting ideas; ToC and retrieval locate; local Problem frame sections recognize; expanded cases disambiguate. None maintains a competing canon. Use E.11.PFP for the common form, exact carrier order, and deterministic form checks rather than restating them here. |
E11-4 | Progressive explicitness | Short prose passes when situation, first result or blocker, direct pattern, and stop or return are recoverable. The internal ladder only helps choose whether deeper expansion, exact basis, worked case, comparison history, or refresh evidence is warranted. |
E11-5 | No fictitious context | Public entry, expansion, template, and walkthrough contain no fabricated reader-project @Context values. |
E11-6 | Conditional expansion completeness | When an exact expansion is opened, each candidate branch has one truthful result promise or blocker and only the result, basis, boundary, and receiver positions that change that branch. |
E11-7 | Bounded comparison | Worked comparisons remain optional examples and preserve the fact that changes the first result. Comparison exposes the choice-changing first-result difference and a stop or return; a materialized comparison account names the later use that relies on its history. |
E11-8 | Author and reader separation | An FPF author or maintainer publishes or refreshes the guidance; a practitioner, manager, or assisting agent reads it and opens a direct pattern without becoming the publisher. |
E11-9 | Plain Preface and local recognition | Preface gives ordinary engineering meaning before strict FPF terms and explains cross-pattern ideas without becoming an index; each pattern’s Problem frame keeps its own local recognition and first action. |
E11-10 | Thin projection and direct authority | ToC pattern rows expose the framework’s declared retrieval fields, including a recognizable working-question cue, without copying a first move, result, or boundary mini-method. E.11.PFP defines the exact index fields and form grammar. ToC, query phrases, compact locators, and retrieval remain finding aids. A selected card carries practical-use guidance; every substantive claim returns to the direct pattern whose content defines, constrains, or tests it. |
E11-11 | Representative, non-exhaustive public examples | Every displayed example names a concrete need, imaginable result or blocker, and choice-changing direct-pattern distinction. When both uses matter, the set shows cheap direct help and extended cross-pattern help, says that many other questions remain in the product, and returns unmatched questions to the index, guide, search, or direct patterns. Example inventory is not product coverage. |
E11-12 | Smallest change reach | When a direct result or boundary changes, repair the smallest affected entry plus determinate README, Preface, ToC, example, relation, and true-consumer wording; unrelated publication units remain unchanged. |
E11-13 | Cross-DPF Reference entry and direct-use bypass | A several-DPF, unclear-DPF, Suite-wide, or ecosystem-gap situation uses a current E.11.DSG DPF Suite Reference; a known sufficient DPF result uses that DPF directly. The Reference returns to the Suite collection and the product series, editions, results, states, or sources that change the answer. Use E.4’s inclusion rules for Suite membership; a reader or assisting System performs lookup Work, and no Suite edition is required. |
E11-14 | Honest card selection and distinct objects | Each declared card passes the same-content-without-mantra comparison, and at least one plausible direct entry is checked against the same test. Every card retains a real cross-pattern dependency; local reminders remain outside card selection. Card unit, published guidance, semantic key, selected form, optional expansion, direct pattern, ordinary walkthrough, and independently admitted CGUS demonstration remain distinct. |
E11-15 | Cross-pattern mnemonic carry-through and same-key return | After one read, a cold reader can repeat the selected card’s longer dependency in their own words, name the first result or blocker, identify the checks and returns that change continuation, reach the direct patterns, and recover the one optional same-key expansion. Form conformance alone does not satisfy this check. |