fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 93182–93197

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:30:10 UTC

E.15:4.7 - Keep one useful change account

Use the receiving workflow’s existing record. A compact change account normally needs only:

QuestionMinimum useful answer
What changed?Exact predecessor and candidate, changed loci, and ordinary-language actual effect.
How material is it?Delta-Class with the reason from §4.3, not the desired label.
What may be affected?Dependent loci and unresolved reach; mention-only citations need no repair recital.
What was preserved?Material predecessor functions and any intentional change, move, or retirement.
Why this repair?Direct repair reason, or alternatives and intended-use trade-off when a real choice existed.
What was checked?The focused or whole-pattern results required for the claimed conclusion.
What reopens?Only a source, premise, consumer, or condition whose change could invalidate the result.

These answers may live in a DRR, review package, campaign result, source-use account, or landing preservation result as that workflow requires. Cite an existing E.21 or E.22 evaluation, F.15 result, source-use record, or decision instead of copying it. Do not mint a dedicated authoring trace, publish a work log with the pattern, or treat a file or publication occurrence as proof that the change was performed well.