fpf.tools
Library / Method Engineering Principles Framework
Jump to passage
In this reading
Source · lines 5395–5402

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:25:10 UTC

ME.24:1 - Problem frame

Use this when. A Method-description language claims to preserve useful source contributions, but you need to find out whether a user can actually recover the promised action, conditions and source basis. Use it again when a source or use changes and you must identify the affected repair without discarding supported work.

The working reader is a Method engineer maintaining a source-grounded description or pattern language. Begin with one promise: which source contribution should a user be able to reconstruct for this action, and what would count as a consequential loss?

The first useful result is one reconstruction answer: the contribution recovered, a deliberate omission with a usable return, or the missing or contradicted element and its next repair. A known one-claim contradiction already owned by ME.12 needs no additional reconstruction exercise.