A.6.1:4.3 - State meaning and applicability without a generic context slot

Meaning and applicability answer different questions:

• the effective U.ReferenceScheme determines how the declaration content is interpreted;
• U.ClaimScope identifies the entities and relations to which the current use claim applies;
• the applicability interval states when that use is claimed;
• the selected CHR:ReferencePlane states the world, conceptual, or epistemic referent mode when that distinction is current;
• mechanism-specific conditions state assumptions that affect operation admission;
• optional modelUseStructureRef : U.StructureRef cites one selected BoundedModelUseStructure only when its relations delimit or change mechanism use.

Do not replace these values with one generic context field. Do not add modelUseStructureRef merely to preserve an old context column.

When one proposed receiving use spans different local senses, take these steps. First, use F.9 only to test the exact SchemeSenseCell correspondence and identify an obtaining Bridge. Second, state a separate current C.2.1 claim about whether that Bridge suits this use, in this direction, under this correspondence rule, and within this loss tolerance; give the claim affirmative or negative polarity. Third, choose the reliance branch from the consequence of the proposed use:

• for ordinary reliance with no actual assurance claim, use A.10. Name the exact evidence-provenance relation, bounded use, unsupported stronger use, window, and reopen or stop condition; proceed only with RelianceDisposition=pass;
• when an actual named assurance claim about this use is current, use B.3 and require its result for that same bounded assurance use. Whether a direct domain rule requires the assurance claim or it is otherwise current, identify it independently under B.3.

A.6.1 AdmissibilityConditions decide whether the proposed operation application is admitted. Its actual application and bindings remain under A.6.1, while dated Work remains under A.15.1; the Bridge, bounded-use claim, and reliance result retain only their own predicates and results.

For example, let BridgeDoseTerms-7 be the obtaining F.9 Bridge between exact cells WardDoseValueCell and ProtocolDoseValueCell under its exact BridgePredicateProfile. The separate C.2.1 claim for reusing the protocol mechanism in the ward-to-protocol prescribing direction is negative because the use rule cannot meet the ward’s zero tolerance for changing the dose unit or scale. That reuse stops before reliance. It also stops when the bounded-use claim is absent, when A.10 does not return RelianceDisposition=pass for an ordinary bounded use, or, when an actual named assurance claim is current, when B.3 has no AssuranceResult for the same use with disposition=supported-for-use. None of those outcomes makes the Bridge cease to obtain or makes an operation application admitted or actual.

A changed effective U.ReferenceScheme identifies another mechanism episteme through C.2.1. A changed selected CHR:ReferencePlane reopens the exact CHR assertion; a changed BoundedModelUseStructure requires exact A.1.1/A.22 assertions. If the project also claims that a plane transition or model-use change relation occurred, name its admitted predicate and participants or stop that claim. For any comparison or change relation actually claimed, name its source and target objects, the comparison or relation asserted, and the meaning or structure it preserves and loses. Any reliability claim, including its Formality and Guarantee, remains under its direct reliability relation.

Numeric comparison and aggregation use A.19 and the direct measurement and scale patterns. Orders are declared before arithmetic is applied, units are made compatible before values are combined, and any reduction to one score cites its governing scalarization relation.