F.9.1:6 - Conformance checklist

1. One exact F.9 Bridge obtains before the stance note is cited.
2. One separately constituted bounded-use claim names the proposed use, direction, correspondence rule, tolerated loss, polarity, and effective scheme.
3. The stance note is a separate C.2.1 episteme whose EntityOfConcern is that exact bounded-use claim.
4. The note states a plain reading and nearest likely overread; a stance token is optional.
5. The stance changes neither Bridge kind nor Bridge identity, claim identity or polarity, reliance, authorization, nor any downstream occurrence.
6. A Card is optional packaging, not a prerequisite or source of truth.
7. CL, observed loss, permitted loss, reliance, and stance remain distinct.
8. One primary stance is normally enough; additional cautions belong in plain boundary or loss wording.
9. Reusing a stance label for another claim requires a new local justification; equal labels do not identify the claims or their losses.
10. A coarsened rendering that needs source return, narrowed use, or blocked downstream use applies A.6.3.CSC.