F.9:10 - Invariants
- Exact endpoints first. A Bridge has exactly two F.17
SchemeSenseCellparticipants. - No context object. Semantic context is recovered from endpoint content and is not a relation participant.
- Different context is not enough. Different projections trigger the question but do not establish the relation.
- Profile contains relation semantics only. The proposed use, its direction, its correspondence rule, loss tolerance, polarity, reliance, authorization, and receiving objects are absent from profile identity.
- Obtaining before occurrence reference. A positive Bridge reference appears only after the fixed predicate is true and its dependencies are present.
- Use claim is separate. Every proposed use names
u,d,r,t, and polarity in a C.2.1 claim about the exact Bridge. - Reliance is separate. A.10 says whether ordinary evidence supports relying on the bounded-use claim. When an actual named assurance claim is current, B.3 supplies its bounded
AssuranceResult. Neither answer comes from F.9 or the Card. - Proposed use is not an occurrence. The
udesignation in the ClaimGraph names the proposed use; any actual Work, assertion, publication, relation, or operation application keeps its own identity; apply the relevant pattern to each claim about it. - Card separation. Card identity, completion, approval, registration, and publication neither make the relation obtain nor make the use happen.
- Loss separation. Observed semantic loss is evidence; permitted loss is tolerance inside the bounded-use claim.
- No authorization by implication. Semantic suitability, evidence reliance, and assurance are not legal, policy, or deontic permission.
- No silent inverse or composition. An inverse asymmetric relation and any direct A-to-C relation are tested independently.
- Two-SlotSpec declaration. The reusable RelationSignature declares only source and receiving SenseCell participant meanings;
CL, Loss Notes, scope/admitted use, evidence, counterexamples, policy, time, model-use structure, description, publication, and registry values remain qualifiers or neighbors. - Recurrence and identity. The non-optional identity rule uses the canonical exact endpoints and exact profile; one fixed tuple/profile is non-recurrent, and a changed applicability/as-of basis changes the profile before another candidate is admitted.
- Description and publication separation. A Bridge description/Card is independently constituted under C.2.1, and E.24.PUB independently governs any selected edition’s publication occurrence, form, and carrier. None establishes relation truth or identity.