F.9:21 - Conformance Checklist

An F.9 use conforms iff:

1. both endpoints resolve to exact F.17 SchemeSenseCell values;
2. their semantic-context projections differ;
3. the Bridge has exactly two participants and one relation-semantic profile;
4. the profile contains no receiving-use or reliance content;
5. the profile applies, its Boolean predicate is true, and its dependencies are present before a positive occurrence is cited;
6. every proposed use is a separate C.2.1 claim naming u, d, r, t, polarity, and effective scheme;
7. observed loss stays in evidence while permitted loss stays in the bounded-use claim;
8. current ordinary reliance uses the exact A.10 branch for the same bounded use; when an actual named assurance claim is current, use its exact B.3 AssuranceResult;
9. no reliance or assurance statement is read as authorization;
10. any actual receiving object is recovered under its subject pattern;
11. description episteme, Card, registry record, E.24.PUB publication occurrence, form, and carrier remain distinct from Bridge occurrence and receiving-use occurrence;
12. inverse and composed relations are tested independently;
13. the reusable RelationSignature declares only two endpoint SlotSpecs, while every CL, Loss Note, scope/admitted-use, evidence, counterexample, policy, time, model-use, description, publication, or registry value remains a qualifier or neighbor;
14. the non-optional occurrence identity and non-recurrence rule is stated and applied before a Bridge occurrence is referenced; and
15. same-context designation remains outside F.9; claim-bearing source wording with role first uses E.10.ROLE, and each recovered system-role kind, assignment, access, permission, authority, Work, evidence-authority, status, U-kind, publication, structure-crossing, or other subject claim returns to its direct pattern.