F.9.1:4 - Solution
F.9.1:4.1 - Recover the claim before writing the gloss
Before adding a stance note, check four things:
- the two exact F.17 local senses are known;
- an F.9 Bridge between them obtains;
- one separate bounded-use claim identifies the proposed use, direction, rule, tolerated loss, and polarity; and
- the stance note has a named reader benefit that the claim does not already express plainly enough.
If items 1 or 2 are missing, return to F.9. If item 3 is missing, write and test the bounded-use claim. If item 4 is missing, stop: no stance note is needed.
F.9.1:4.2 - Write one bounded reading
Write the note in this order:
- cite the bounded-use claim it explains;
- state one plain reading of that claim;
- name one primary stance when a reusable label helps;
- state the nearest likely overread; and
- emphasize a material loss only when that emphasis changes how the reader should understand the claim.
The stance note may cite evidence or a current A.10 or B.3 reliance result, but it does not create either. If the proposed direction, rule, tolerated loss, polarity, or reliance result changes, repair that object under F.9, A.10, or B.3 rather than editing the stance as a proxy.
F.9.1:4.3 - Starter stance vocabulary
| Stance | Plain reading | Nearest overread to reject |
|---|---|---|
localRename | For this use, the receiving expression is being read as a near-renaming within the stated local boundary. | Cross-local identity or unrestricted replacement. |
operationalizes | For this use, the receiving expression gives a procedural, observable, or measurable reading of the source. | Enactment, implementation, work authority, permission, or type-structure equivalence. |
partialAnalogy | For this use, the two senses share one stated explanatory pattern and differ elsewhere. | Admissible substitution or equivalence. |
projection | For this use, the receiving expression keeps one stated aspect and drops others. | Completeness, reversibility, recoverability, or permission to ignore the dropped distinctions. |
nonEquivalent | For this use, read the comparison as an explicit warning against equivalence. | A claim of disjointness, a negative Bridge claim, or a general ban beyond the stated use. |
These labels are optional local designations inside the stance episteme. They are not Bridge kinds, levels, scores, permissions, or a second taxonomy. If a plain sentence is clearer, use the sentence without minting a label.
A stance word carries no direction by itself. Direction belongs to the bounded-use claim it explains: a projection reading in one direction never establishes the reverse reading or use.
F.9.1:4.4 - Keep Bridge, use, reliance, and packaging separate
- A practitioner uses F.9 to test and record whether the Bridge obtains.
- The bounded-use claim says whether that Bridge suits one named use.
- A practitioner uses A.10 or B.3 to judge whether current evidence or assurance supports relying on that claim.
- The stance note says how to read that one claim.
- A claim that a comparison, translation, publication, Work occurrence or other downstream act occurred uses that object’s subject pattern and evidence. When authorization is needed, recover it under the pattern that defines the permission or authority claim. The stance note establishes neither.
A Bridge Card is optional claim-bearing packaging. A Card may publish the Bridge description, bounded-use claim, evidence references, reliance result, and stance note together, but the Card is not a prerequisite for any of them. The Card’s layout and edition, and any publication occurrence or file carrying it, remain separate from the objects it brings together.
CL is optional F.9 shorthand for evidence strength about a stated correspondence. It is not a substitution threshold and does not rank the stance. A stance note may not turn CL, a loss note, or friendly wording into suitability or permission.
F.9.1:4.5 - Preserve source return and coarsening boundaries
A projection or nonEquivalent stance can highlight loss, but it does not provide the source tether, narrower admissible use, blocked downstream use, or return trigger required for controlled coarsening. When those duties are live, use A.6.3.CSC and keep the stance note only if it still helps explain an independently established bounded-use claim.
Publication does not cure a missing source. If a reader must return to a source episteme or source publication before the Bridge or bounded-use claim can be checked, perform that return first.