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

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 06:50:10 UTC

ME.21:4.3 - A compact retained answer

For a reusable allocation, this amount of information is normally enough:

PositionQuestion answered
Receiving useWhich Method-description or pattern-language question does this allocation settle?
Source contribution and roleWhat is being carried from which passage, edition or returned account?
Current supplyWhich existing result answers the reusable part, under what limits?
ReconciliationWhat is shared, different, merged, split or still unresolved, and why?
Destination and remainderWhat changes in the receiving description or pattern, and what remains elsewhere?
ReturnWhich changed premise reopens the allocation, and where should the reader return?

Use ordinary prose instead of a table when it is clearer. A retained allocation is a claim-bearing account about the named allocation question; its claim content, subject and effective reference scheme determine its C.2.1 identity. Its locator is a recovery aid, not a Method identity or an acceptance decision.