Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:25:05 UTC

C.39:4.6 - Change the affected way and retain what still works

Begin with the difference that matters: an input value, intended result, tolerance, available means, performer preparation or condition of use. Identify which action, connection or claim relied on the old condition. Follow its result uses and shared constraints far enough to determine what the change can affect. A changed whole condition may alter a constituent action; a changed receiving condition may leave another independent use intact.

Distinguish doing the same Method again with permitted inputs from changing the Method, and both from correcting its description or revising a claim about it. Use A.3.1:4.7–4.8 when identity or directed refinement affects the decision. Repeating an inadequate preparation does not by itself develop a better preparation method.

Construct the missing adaptation through section 4.3, or use a qualified alternative. For a constituent replacement, B.1.5.RS compares the affected encompassing uses, including shared or simultaneous demands. Do not infer that a local improvement preserves the whole or merely moves its burden elsewhere. If the changed result can alter which problem is worth pursuing, C.40.CD develops that question with the way.

Follow the proposed change through a complete affected use. Reuse a calculation, observation or earlier judgement only while its inputs, meanings, conditions and claim remain applicable. A numerical bound may remain valid while a tighter requirement makes the receiving use fail. Retain independently usable branches whose conditions still hold; neither reject them with the failed branch nor infer that every branch survives.

Update the explanation that later work actually uses: the changed action or relation, the reason, its supported conditions and what calls for another return. A reader should be able to reconstruct the changed case from that account. If no adequate replacement is available, return the precise unresolved operation, a useful narrower result or a justified stop. Development can finish with that answer; it does not guarantee invention.