FPF.Reference:9 - Thinking Through Writing
Preface node
heading:fpf-reference-9-thinking-through-writing:1295
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
Writing can help obtain an understanding as well as make its grounds inspectable. Putting claims beside one another, making a relation explicit or trying a provisional formulation can reveal a distinction that conversation or memory had left unclear. The useful result may be a better question, an alternative worth considering, a reasoned decision or a precise limit on what is known.
Choose the written form by the work it should help perform. When the subject is unclear, compare the relevant statements and what each would imply; use the difference to develop the question. When choosing, keep the alternatives and grounds comparable. When another participant must continue or a premise may change, retain enough of the subject, reasoning and conditions to recover the affected conclusion. Revise the form if it hides the distinction that this work needs.
Conversation, memory, chat logs, sketches or tool outputs can suffice for immediate work. Addressable records become useful when delegation, review, reuse, publication, AI assistance or delay requires durable access. An exploratory note can help develop the subject even when it does not constitute one episteme under C.2.1. A filled card can be an episteme; its selected layout can serve as a publication form under E.24.PUB. The claims and their form of expression remain different objects.
Written forms support different reasoning actions. For example:
- developing a problem card can turn an initial complaint into a formulation whose subject, constraints and unresolved relations later work can use;
- a TaskSignature makes an accepted problem usable by later eligibility, acceptance, and method-family selection without selecting the method or planning the work inside the problem record;
- a comparison frame makes explicit what is being compared, by which characteristics and under which conditions;
- declaring a CharacteristicSpace makes its selected characteristics and Scales recoverable before their values are used in an evaluation or comparison;
- a term sheet keeps local meanings from being flattened across teams;
- a DRR makes the decision, its reasons and its intended consequences inspectable;
- a pattern body explains reusable guidance for a recurring problem, with the conditions and limits of its use.
Consider two handover statements that use the word complete. Placing them side by side may show that one refers to sending and the other to acceptance. The writer can now formulate the question of which event the receiving work requires and what supports the claim that it occurred. C.22.2 develops this move from an initial signal to a usable problem formulation. If examination shows that both statements mean the same event, the proposed contrast loses its ground: revise the question. The written comparison helps obtain the next inquiry, and a changed premise sends that choice back.
The medium is not prescribed. Use paper or a digital tool that keeps the needed claims and relations recoverable. Changing the layout can preserve this work; removing a comparison or its grounds can lose it even when all the old field names remain.
For an AI-generated proposal that needs inspection or reuse, identify what result it offers and its grounds—for example, an option comparison, an architecture question or a qualified model-use claim. Choose a form that keeps the necessary distinctions recoverable. The next section explains when the recovered subject needs classification or shared ontological coordination, and when an ordinary statement already suffices.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)