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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:10:20 UTC

A.6.P.WMR:1 - Problem Frame

Use this when. Practitioners SHOULD use this pattern after A.6.P generic relation recovery has isolated one current method-or-work boundary claim and the exact entity is already in view, but words such as input, raw material, source data, source material, output, result, outcome, deliverable, or handoff still do not reveal the direct relation that makes the sentence true. They SHOULD also use it when method, intended-work, actual-work, production, evaluation, delivery, acceptance, transfer, or receiving-use wording leaves that claim’s participant meaning or orthogonal claim dimensions unclear.

The primary EntityOfConcern is one relation-bearing claim in an episteme. The trigger word helps a practitioner notice the problem; it is not the governed object, a participant kind, a relation kind, or a universal family of inputs and results.

Primary working reader, concern, and viewpoint. The primary reader is a practitioner or engineer whose current task is to make one boundary-word claim safe for a named use. Their concern is which exact relation and claim dimensions can be stated safely for that use now; the viewpoint is that use. The SubjectPatternLocator identifies the pattern description containing the defining or constraining ClaimGraph, while current case facts determine whether the relation obtains.

First useful result. Start at the boundary-word sentence and answer three ordinary questions: what exact thing is being named, relative to what exact method, plan, work, operation application, transformation, delivery, or receiving use, and what direct verb can safely be said now—or why can it not yet be said.

For example, a note says, inspection report R-17 is the result of inspection. R-17 is an exact report episteme. If the current related object is independently identified inspection application P-17 and its declaration-local result-binding predicate actually holds, write: Inspection application P-17 returned report R-17. Then stop unless the current use separately asks about report inception, inspection Work, evidence, publication, delivery, or acceptance.

The nearest three failures keep the same thing and related object while changing only the deciding deficit:

  • if the binding governor is known and the case facts fail its positive predicate, the proposed positive binding is factually unsupported;
  • if the governor is known but the fact needed to decide whether P-17 returned R-17 is unavailable, return missing-information;
  • if no current result-binding predicate or direct report relation governs that pair, return missing-governor and name the exact participants, proposed predicate, affected use, and absent definition; name a future pattern or declaration need only when one is actually identifiable.

Only when another reading could change the answer should the practitioner make the formal distinctions explicit: reusable declaration versus intended, committed, current, or historical subject relation; exact extent; polarity; and whether the claim is assertable. A direct relation additionally names its exact RelationKind and resolving direct pattern or relation-declaration episteme. An operation binding or local claim instead names its declaration-local or admitted predicate and defining declaration. These assurance details check the ordinary answer; they are not prerequisites for understanding a simple positive past-tense sentence.

What changes in practice. The engineer stops debating which broad word is correct. They name the thing, the exact object it is relative to, and the direct verb they can safely say now; if no verb is yet justified, they state the exact failed fact, unavailable fact, or absent governor. Formal claim dimensions and assurance apparatus appear only when they can change or check that answer. Planning, actual participation, production, evaluation, delivery, acceptance, and transfer no longer inherit one another through vocabulary.

Adoption test. Given one compressed sentence, the reader can replace it with either the shortest direct sentence under its exact governor or an exact factually-unsupported, missing-information, or missing-governor result, without turning a plan, description, binding, record, or label into actuality.

What goes wrong if missed. A plan is read as actual participation; a method description is treated as a work occurrence; an operation result binding is mistaken for a produced entity; a changed continuing entity becomes a new output; a delivery or handoff package is treated as the transfer; or a convenient missing relation is replaced by a new universal kind.

Ordinary non-use boundary. Practitioners SHOULD NOT use this pattern when the exact direct relation and all claim dimensions needed by the receiving use are already readable; they SHOULD apply that direct pattern and stop. They SHOULD use C.2.P first when the unresolved question is which source expression, episteme, publication, or source-to-use relation is current; A.15.PROD directly when the only current question is production-work participation, entity-identity inception, or production completion and its participants are already exact; and the direct measurement, evaluation, commitment, delivery, acceptance, transfer, resource, premise, transformation, method, planning, or work pattern when that relation is already selected.