E.11:3 - Forces · fpf.tools

Force	Pressure on the solution
Project recognizability	Public entry starts from situations engineers recognize, not internal pattern topology.
First value before apparatus	The first useful result or blocker appears before schemas, PatternIDs, quality vocabulary, or exact reliance fields.
Technical precision	The direct pattern, result kind, identity or obtaining basis, and neighboring boundary remain recoverable when they change the choice; ordinary wording need not expose every exact field.
Low burden	A newcomer should not fill forms or fabricate project values before seeing what the direct pattern can do.
Bounded search	Several entries may remain plausible, so comparison needs a stop and a recoverable wrong-turn return rather than one perfect first guess.
Durable reliance	Only a named later review, replay, audit, automation, or costly decision justifies addressable comparison history.
No duplicate canon	README, Preface, ToC, retrieval, expanded cases, and local `Problem frame` sections keep different jobs.
Didactic continuity	A public entry gives a readable example or walkthrough, not only a PatternID list.
Corpus evolution	Repair the smallest affected entry and its true consumers when a direct pattern’s result, boundary, or recognition condition changes.