Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:45:20 UTC

F.19:4.3.2 - Restore a technical head when the meaning is still ambiguous

Precision before a coarsened rendering. When head kind, qualifier claim, or comparison basis remains unresolved in FPF-governed prose, use this working order:

Restore the head kind first. A narrowing qualifier such as comparative, safe, interactive, or reliable does not by itself restore that kind. Unpack the qualifier claim and then check whether the comparison or escalation basis is homogeneous. Only after that may a later Plain, didactic, or coarsened rendering relax the sentence, while keeping the more precise upstream interpretation recoverable.

Judge homogeneity against the comparison or condition rule actually used; recover distinct relations separately when that rule combines them. The basis may be a homogeneous claim-kind criterion, threshold, or named defining, constraining, or source-relation condition.

Treat exact, direct, current, governed, subject, owner, defining, and similar qualifiers as content only when they distinguish live alternatives. Remove them when no such contrast changes the truth, action, stop, or reliance.

A PatternID may remain an ordinary citation; expand it into a claim-bearing episteme, ClaimGraph, U.MethodDescription, U.Method, actor, assignment, U.Work, or another formal identity only when the current claim or a named later use depends on that distinction.

Keep ordinary practitioner action and instrumental pattern-use wording ordinary when it does not assert a particular dated Work occurrence. “Use E.9 to record the decision” and “the framework maintainer compares the editions” need no invented Method, MethodDescription, performer, assignment, or Work identity.

Open the identity-bearing branch only when the sentence deliberately asserts a particular dated U.Work occurrence. Then point to its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. Add a local system-role kind or a separate System-classification judgment only when that neighboring claim matters.

Treat a pattern episteme as a U.MethodDescription only after A.3.2 establishes that it has an already admitted Method as its exact EntityOfConcern and makes at least one substantive claim about that Method as a way of doing. Otherwise cite the applicable pattern content as guidance and use A.3.1 for the Method itself.