F.9:4.2 - Judge a bounded use separately

Once exact Bridge b obtains, state the proposed use in ordinary language before introducing FPF terms. Name:

• u: what the reader proposes to compare, substitute, translate, publish, or otherwise do;
• d: the exact source-to-receiving direction for that use;
• r: the use-specific correspondence rule;
• t: the semantic-loss tolerance for that use; and
• whether the claim is affirmative or negative.

The resulting C.2.1 claim asks whether b is suitable for <u,d,r,t>. Its exact EntityOfConcern is b; its ClaimGraph designates u, d, r, t, and polarity; its effective ReferenceScheme makes those designations interpretable. That C.2.1 triple identifies the claim episteme. Changing u, d, r, or t changes the claim, not the Bridge.

An affirmative claim is one premise for the proposed use. It is not a permission, authorization, evidence-provenance relation, reliance classification, assurance claim, decision, or occurrence of that use. A negative claim says that the Bridge is not suitable for the named use; it does not make the Bridge cease to obtain.

For ordinary evidence reliance, recover the descriptive A.10 evidence-provenance path, the independently established direct relations it cites, and local RelianceDisposition for the same bounded use. Only pass supports reliance on the affirmative claim for that use; degrade supports only its named narrower use, while abstain, reopen, evidence-needed, assurance-needed, or blocked-current-use supplies no passing classification.

Use B.3 only when an actual named assurance claim about the proposed use is current. Require its result for the same bounded assurance use; a non-positive disposition stops or narrows that use. A direct domain rule may require the claim, but the Bridge, display, consequence, or A.10 disposition does not create it.

Neither an A.10 passing disposition nor a B.3 AssuranceResult with disposition=supported-for-use is legal, policy, or deontic authorization. If authorization is needed, recover it under its direct pattern. If a later claim says the use happened, recover the actual Work, assertion episteme, publication occurrence, direct relation, operation application, or other object under its own pattern; the u designation in the ClaimGraph names the proposed use and is not that occurrence.