Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:00:10 UTC

C.20:4.9 - Crossing, comparison, evidence, health, and publication are conditional branches

Open these branches only when the named discipline use needs them.

Cross-field or cross-sense use. A cross-field use may use independently governed claims without a semantic crossing. When an exact cross-context semantic relation is claimed, first resolve two exact F.17 SchemeSenseCell values; F.9 identifies an obtaining Bridge only when their semantic-context projections differ and the direct predicate and dependencies are satisfied. A field, scheme, cell, or plane difference alone creates no Bridge. For an obtaining Bridge, keep a separate current C.2.1 bounded-use proposition whose EntityOfConcern is that Bridge and whose ClaimGraph names the proposed action u, exact direction d, use-specific correspondence rule r, tolerated semantic loss t, and affirmative or negative polarity. Observed loss and counterexamples remain evidence; the permitted-loss tolerance remains claim content. Neither one reidentifies the Bridge.

For ordinary evidence reliance, recover the descriptive A.10 evidence-provenance path and the independently established direct relations it cites for the same bounded use. Only RelianceDisposition=pass supports that affirmative use; degrade supports only the named narrower use, while abstain, reopen, evidence-needed, assurance-needed, or blocked-current-use does not pass the attempt. Use B.3 only when a named assurance claim is current, and require its result for that same bounded assurance use. Authorization and any actual comparison, substitution, translation, publication, or Work occurrence remain with their subject patterns.

Crossing visibility and presentation checks. Keep an exact Bridge and separate bounded-use proposition discoverable in an account that relies on that obtaining semantic relation. For a ReferencePlane-only crossing, keep the applicable plane relation and policy discoverable instead; if both facts are current, keep both under their own predicates. Materialize an E.18 CrossingBundle only when an independently current E.18 structural GateCrossing exists and a named downstream use relies on durable evidence for that structural crossing; if it also relies on cross-semantic correspondence, add E.18’s separate F.9 block. E.17 governs publication packaging and A.21 governs any actual GateCheck or GateDecision.

For lane purity, inspect the current B.3 result by value: every characteristic keeps its bearer and scale, and any aggregation cites its domain model and assumptions; there is no universal F-G-R-CL fold. Apply E.10 lexical checks to the published labels, keep normative prose notation-neutral, and treat every discipline column as didactic only.

Comparison or aggregation. Identify the exact Characteristics under A.17 and their Scales, applicable Units and legal operations under A.18; C.16 supplies measurement results when the inputs are measured. A mean over an ordinal Scale and an aggregation that mixes unconverted or incommensurable Units are inadmissible: stop that operation, establish a lawful transformation or comparison scheme, or retain the separate values. When using A.19.CPM, bind its required profile pair, comparator, claim scope and selected slices, predicate when used, reference scheme and plane, evaluation point or interval, and evidence policy; retain its set-valued result. CPM does not aggregate. A numeric or profile aggregation uses its own justified combining rule and recoverable inputs and contributors; a selected A.19.ULSAM or B.1 Γ-fold retains that interface’s arguments and result binding.

Ordinary comparison or folding mathematics needs no asserted dated U.Work. When the account asserts dated comparison or aggregation Work, or the receiving use consumes it, recover its A.13 core and independent A.15.1 admission; use F.6 only for precise assignment-bound attribution. A calculation application and its qualification window do not by themselves establish a dated Work occurrence.

When a comparison or aggregation is governed by a G.0 CG-Spec, its pre-operation check names the Characteristic ids, ScaleComplianceProfile with applicable Unit, polarity and legal-operation conditions, MinimalEvidence, and the admitted comparator or declared Γ-fold and contributors. Missing or unknown required declarations or evidence block that governed operation. Ordinary comparisons and aggregates still need compatible inputs and a lawful operation; they need no CG-Spec unless the receiving use selects that interface.

If the operation relies on an obtaining F.9 Bridge between exact F.17 SchemeSenseCell values, use the separate Bridge, bounded-use-claim and reliance branch above. A ReferencePlane crossing instead uses its applicable relation and policy; when both relations matter, retain both. These relations do not supply the operation’s scope, comparator, inputs or result.

Evidence, currentness, and assurance. Use A.10 for source use and the evidence-provenance path, and G.11 for selected-edition currentness. When an imported source claim supports a construction, classification, comparison, publication, or assurance use, keep the exact source and edition plus only the lane tags, freshness window, or validity conditions that the receiving use consumes. Use this apparatus only for claims that need such reliance.

Open B.3 only for a named assurance claim. Its AssuranceResult identifies the target claim, assurance use, basis, disposition, limits, and reopen condition. If the argument consumes a characteristic or calculation, name its bearer, property, scale, unit, interpretation, basis, dependency model, assumptions, rule, and rival as applicable. C.20 supplies no default F/G/R/CL lanes, weakest-link fold, SpanUnion, congruence penalty, plane penalty, or assurance arithmetic. A Bridge-related penalty is current only when a named B.3 assurance claim uses an applicable declared domain model whose current facts and rule yield it; that value belongs only to the calculated AssuranceResult for that named use.

State ReferencePlane only when it changes an exact input or interpretation; when an exact plane crossing is current, cite the applicable plane relation and policy. The selected plane and its relation identify neither a discipline part nor a part relation.

Insufficient or unknown support narrows, abstains, requests evidence, reopens, or blocks the attempted assurance use under B.3; it does not make a part relation or whole obtain or cease.

Health or state view. C.21 can evaluate typed discipline-health characteristics. Local values such as emerging, consolidating, codified, or fragmenting need their defining criteria and support, with Scale, observation period and currentness conditions as required by the claim. A decision threshold belongs to the applicable decision rule; represent it as a G.4 AcceptanceClause when that formal acceptance interface is used. A state label, health vector, score, or dashboard transition does not itself reidentify the discipline.

Description and publication. The claim-bearing whole expressed by a discipline description, construction trace, comparison report, health series, card, or registry row is identified as an episteme under C.2.1 when that pattern’s constitution test holds. E.24.PUB governs any actual publication occurrence and keeps selected episteme edition, audience, bounded-use declaration, particular expression, carrier, and availability interval distinct. Updating or publishing the account changes neither the field assembly nor its past.