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.3.3 - KindBridge and CL^k — Correspondence between Distinct Kinds

Summary. A changed practice, source, team, or scheme first triggers a comparison of kind definitions. If the same kind continues, reuse it without a KindBridge. When the receiving use is candidate-bearing, evaluate the candidate under the receiving declaration. When two independently identified kinds are distinct and a directional correspondence predicate holds, one KindBridge direct relation may obtain. A separate bridge-assertion episteme states direction, paired declaration editions, preservation or loss, evidence, and admitted use, with CL^k when the consumed assurance or calibration account requires it. It never transfers source classification truth.

Normativity: Normative in Part C. Identifier C.3.3.

Status: Stable Audience. Engineering managers, architects, assurance leads, editors.

Depends on.

  • C.3.1 — U.Kind and U.SubkindOf: kind identity follows candidate domain and membership distinction; subkind facts form a preorder; locality and scheme editions are not identity keys.
  • C.3.2 — Kind intent, admissibility, judgment, and extension: check admissible | not-applicable before a fresh true | false | unknown receiving judgment.
  • A.2.6 — USM: Claim scope and selected context slices remain separate from kind identity and kind correspondence.
  • C.2.2 — F–G–R: justified bridge penalties affect reliance R, not F or G.
  • C.2.3 — Formality assessment: the assessed expression properties belong to the declaration or assertion episteme.

Use boundary. Kind correspondence leaves scope translation and local-sense correspondence to their own patterns when needed. CL^k is an ordinal assessment for a declared kind-correspondence use, not a universal interoperability score.

C.3.3:1 - Purpose and Audience

Typed reuse can fail because a claim’s scope changed, because the receiving use employs another kind, or because wording changed meaning. These are separate questions. C.3.3 handles only a claimed directional correspondence between two distinct kind individuals. It lets a team state, for example, that source Vehicle corresponds to target TransportUnit, which distinctions are preserved or collapsed, and what loss a receiving use accepts.

C.3.3:2 - Context

Different sources or practices may use the same kind, or different kinds may coexist inside one source. Names, source labels, compatible schemes, and matching current extensions decide neither. First compare the candidate domains and membership distinctions under C.3.1. Same-kind reuse needs no bridge. Distinct-kind reuse may need a KindBridge when its correspondence predicate can be established. F.9 is additional only when distinct local senses and their bounded use are current.

C.3.3:3 - Problem

  1. False splitting. A locality change creates two apparent kinds and a bridge even though the membership distinction is unchanged.
  2. Semantic drift. A different receiving kind is treated as the source kind because names or extensions look alike.
  3. Hidden order loss. Subkind facts collapse, invert, or become unsettled without being reported.
  4. Entangled channels. Scope, sense, and kind correspondence are bundled into one score or record.
  5. Classification transfer. A source judgment is copied as receiving truth without checking receiving admissibility and criterion satisfaction.
  6. Unreplayable use. An unspecified mapping or implicit latest edition leaves a guard with no stable basis for deciding whether the bridge use is current.

C.3.3:4 - Forces

ForceTension to resolve
Same-kind reuse vs bridge disciplineDo not invent a bridge for provenance, but make real distinct-kind correspondence explicit.
Minimal disclosure vs precisionState only what the receiving use consumes while keeping direction, definedness, and loss inspectable.
Local autonomy vs reuseReceiving kinds keep their membership distinctions; correspondence does not merge them.
Separate channels vs workloadScope, sense, and kind correspondence remain separate without forcing all three into every use.
Fresh truth vs useful supportSource results may support reliance but never substitute for receiving admissibility or judgment.

C.3.3:5 - Solution — Compare Identity, Then Relate Distinct Kinds

  1. Compare kind definitions. Recover source and receiving candidate domains, membership distinctions, and continuity rules. A changed locality or scheme prompts this check; it does not decide it.
  2. Stop on same-kind reuse. If the same kind continues, use the declaration edition selected for the receiving use. When that use is candidate-bearing, check admissibility and evaluate the candidate afresh. No KindBridge obtains merely because source, practice, team, wording, or scheme changed.
  3. Open a bridge only for two distinct kinds. A KindBridge occurrence is an obtaining direct relation between one source kind and one target kind. Its directional predicate states the correspondence and definedness required by the named receiving use. Identify each kind independently under C.3.1.
  4. Keep the assertion separate. A C.2.1 bridge-assertion episteme designates the relation when needed and carries paired KindSignature editions, mapping rule, selected order-preservation results, loss notes, evidence, and admitted use. Include CL^k when the consumed assurance or calibration account requires it. A card, row, F.9 relation, or publication does not make the bridge obtain.
  5. For candidate-bearing use, evaluate the receiving candidate. First return admissible or not-applicable under the receiving signature and slice. Only an admissible request returns true, false, or unknown. A source judgment may support the bridge assertion or reliance but is never copied as receiving truth.
  6. Route consequences narrowly. When a receiving claim relies on the obtaining bridge, apply only the justified CL^k consequence to R. Scope and any sense relation retain their own objects and rules; F and G do not change.

The kinds are the direct relation participants. Scheme and signature editions qualify interpretation, applicability, and the assertion. They do not identify the occurrence. For the ordered kind pair, the direct relation is participant-determined. An aligned scheme-edition change prompts reevaluation of whether the same relation still obtains; it does not mint another occurrence.

KindBridge is the direct relation kind governed here under A.6.REL. This spelling does not by itself admit a public dependent U-kind named U.KindBridge. If admission later matters, E.24.UK must close it separately.

C.3.3:6 - Norms & Invariants (normative)

The KB‑01…KB‑12 rules below govern kind correspondence.

C.3.3:6.1 - Direct Relation Subject and Scope

KB-01 (Distinct participants and obtaining). One KindBridge occurrence has exactly two ordered participants: an independently identified source kind and an independently identified distinct target kind. It obtains only when its directional correspondence predicate holds within declared definedness. A different locality, label, scheme, or extension supplies no bridge. Signatures, assertions, evidence, CL^k, loss notes, and slices are not participants.

KB-02 (No Scope or sense substitution). A KindBridge maps neither Claim/Work scope nor local wording. Scope translation uses A.2.6 when the receiving claim consumes it. An F.9 relation is added only for a current distinct-sense use. Neither channel is required merely because a kind bridge exists.

No blended score. Scope congruence, sense-relation loss, and kind congruence remain separate. Do not aggregate them into one interoperability score.

C.3.3:6.2 - Settlement, Assertion, and Identity

KB-03 (Direct settlement). The C.3.3 settlement SHALL make recoverable:

  1. ordered source-kind and target-kind participants and the proof that they are distinct;
  2. the directional correspondence predicate, applicability, and definedness; and
  3. participant-determined occurrence identity for that ordered pair.

The separate bridge assertion states whether obtaining is affirmed, denied, or unresolved; only an affirmative assertion may designate an obtaining occurrence. It also names the declaration and scheme editions used to interpret the predicate, selected source and target subkind facts, preservation/collapse/non-preservation/unknown results, loss, evidence, and admitted use. Include CL^k when the consumed assurance or calibration account requires it.

Another assertion, mapping expression, card, signature, scheme edition, or publication does not create another relation occurrence. A changed interpretation prompts a renewed obtaining test. If the same ordered participants and correspondence continue, the same relation continues; if not, the prior obtaining claim is no longer current.

KB-04 (Fresh receiving classification). With fixed receiving candidate, signature edition, and slice, check admissibility first. not-applicable forms no classification judgment. An admissible request is evaluated reproducibly as true, false, or unknown. A source judgment or bridge assertion may support reliance but is never copied into the receiving result. An unavailable bridge dependency blocks that bridge use without rewriting an independently evaluated receiving result.

C.3.3:6.3 - Order & Monotonicity

KB-05 (Monotone order). To claim that source fact SubkindOfObtains(k1, k2; sourceRS) survives transfer, identify its two target endpoints. For each endpoint that changes kind, establish the directional KindBridge from source to target. For an endpoint that remains the same kind, establish identity under the two declarations. Establish SubkindOfObtains(k1', k2'; targetRS) using the target criteria or its closed-domain test (C.3.1). If another claim relies on that order, check separately that the premises it needs survive the transfer. Identify a target R_sub : U.SubkindOf occurrence only when its identity matters to the receiving use. KB-06 (No inversions). A bridge assertion MUST NOT state preservation when the mapped target order is inverted. If SubkindOfObtains(k2', k1'; targetRS) holds for distinct mapped kinds and the required forward fact SubkindOfObtains(k1', k2'; targetRS) is established not to hold, state non-preservation and the loss. If the required target order cannot be settled, state unknown; do not turn non-settlement into either preservation or inversion. KB-07 (Collapse semantics). A bridge assertion may classify selected source subkind distinctions as collapsed when several source kinds correspond to one target kind. The assertion SHALL designate the affected obtaining U.SubkindOf relations and state the lost properties; the direct bridge relation does not alter either local order.

C.3.3:6.4 - Congruence & Assurance

KB-08 (Anchor reuse and AT neutrality). CL^k reuses the ordinal anchor semantics of CL but assesses the declared bridge use over kind intent and order. The bridge-assertion episteme labels it kind-congruence. KindAT remains editorial under C.3.5 and independent of CL^k. KB-09 (Effect on R only). After receiving admissibility has been checked and an admissible candidate has received a fresh target judgment, a claim that relies on both that result and an obtaining KindBridge may apply only the bridge assertion’s justified monotone Ψ(CL^k) consequence to R, alongside any independently established scope-relation consequence. A not-applicable candidate forms no judgment; unknown stays unknown; F and G do not change. KB-10 (Chaining). A minimum over comparable link assessments reports the lowest link rank on their common scale and calibration question. It does not by itself assess the composed correspondence. For a receiving use that depends on preservation through the chain, recover the mappings and intermediate interpretations, establish their joint definedness, and check that the required source distinctions survive every link and the composition. Keep each obtaining KindBridge and its assertion distinct. Return the preserved structure, losses and unresolved requirements; use another correspondence, narrower application or additional basis when an essential distinction is unavailable.

Two locally useful mappings can lose different distinctions. For a finite order test on 0 < 1 < 2, let both monotone maps have values f(0)=0, f(1)=0, f(2)=1 and g(0)=0, g(1)=0, g(2)=1. Each preserves a nontrivial distinction in its own domain, but their composition maps every source value to 0. The lowest link rank cannot establish preservation of the source distinction the final use needs.

Conversely, an established composition that preserves the required common structure remains usable. A local law may derive a composition characteristic from a minimum when its domain and preservation argument justify that law; there is no universal chain-minimum rule. Any numerical consequence for R still requires the receiving model under C.2.2 and B.3.

C.3.3:6.5 - Loss Notes & Definedness

KB-11 (Loss notes). The bridge-assertion episteme SHALL state which KindSignature invariants are not preserved, which obtaining source U.SubkindOf relations are collapsed or not preserved, and any higher-equality caveats. These claims do not rewrite the source or target kinds. KB-12 (Definedness and guard use). The bridge predicate and assertion SHALL state definedness. Outside it, a receiving guard declines that bridge use. Independently, receiving classification keeps not-applicable or its admissible true, false, or unknown result; bridge inapplicability rewrites none of them.

C.3.3:7 - Interactions (informative)

C.3.3:7.1 - With Scope and Sense Relations

A receiving use may need none, one, or several independent relations:

  • an A.2.6 scope relation when the claim’s admitted extent is translated or compared;
  • a C.3.3 KindBridge when two distinct kinds are directionally related; and
  • an F.9 relation when distinct local senses are related for a bounded use.

Open only the channels the receiving claim consumes. Keep their definedness, losses, and R consequences separate.

C.3.3:7.2 - With Receiving Classification

After same-kind reuse or an obtaining bridge, use the receiving KindSignature edition. Check candidate and slice admissibility. If admissible, evaluate the receiving judgment. If a mapping motivates another signature, author that declaration episteme separately. A source judgment can support a claim but never supplies receiving truth.

C.3.3:7.3 - With Kind-use Adaptations

For same-kind reuse, select the receiving C.3.4 declaration without a bridge; evaluate the receiving candidate afresh when that use is candidate-bearing. For distinct-kind use, recover the obtaining KindBridge, bridge assertion, receiving adaptation declaration, and any adaptation-correspondence declaration needed for differing constraints or bindings. Source adaptation results are not receiving truth.

C.3.3:7.4 - With Guards

A typed receiving guard first determines whether the same kind continues or a distinct-kind bridge is current. When the guard’s use is candidate-bearing, it checks receiving admissibility and, when admissible, the fresh judgment. It independently checks any scope or sense relation the claim consumes and applies only justified consequences to R. not-applicable, unknown, absent bridge, and guard refusal remain different results.

C.3.3:8 - Authoring, Review & Rating Guidance (informative)

C.3.3:8.1 - Authoring a KindBridge assertion

  • Compare identity before authoring a bridge. For a changed locality, source, team, spelling, or scheme, first repeat the kind-definition comparison under C.3.1. Stop without a bridge when the same kind continues.
  • Declare the needed correspondence and order facts. For two distinct kinds, declare only the directional correspondence and subkind facts the receiving use relies on; mark any required but unsettled order result unknown.
  • Prefer an existing suitable target kind. If the target already has a suitable kind and declaration edition, relate that kind directly. If a new target declaration is required, author it separately before asserting bridge obtaining; list what the mapping predicate preserves, relaxes, or drops.
  • Write loss notes in plain language. Example: “EV vs ICE subkinds collapsed; battery‑health invariants dropped.”
  • Fix the definedness area. Bind to target Standards/versions and any environment selectors essential to classification.
  • When CL^k is required, assess it from exemplars. Calibrate on concrete counter-examples and preserved properties; resist optimistic ratings.

C.3.3:8.2 - Review prompts

  1. Identity checked first? Same kind reused without a bridge, or two distinct kinds and the obtaining correspondence shown? Add Scope or F.9 relations only when the receiving use consumes them.
  2. Check the order claims. Any ⊑ inversions? Collapses disclosed?
  3. When CL^k is used, is it plausible? Based on preserved properties, not name similarity?
  4. Loss consequences clear? Do they change the justified inference, require more basis or leave the intended use adequate?
  5. Definedness area clear? Outside it, does the guard decline this bridge use while preserving the independent classification result?
  6. Reliance consequence justified? Any numerical change to R needs its receiving model; F and G remain unchanged.

C.3.3:8.3 - Rating CL^k (rules of thumb)

  • High CL^k: signature equivalence or up‑to‑iso; ⊑ fragment preserved; only cosmetic losses.
  • Medium CL^k: some invariants relaxed or lost; selected subkinds collapsed; the source-order facts required by the use remain preserved.
  • Low CL^k: name-only correspondences; properties diverge; order not preserved. Establish that the KB-01 correspondence predicate holds before bridge use, even for a name-only match. Determine which inferences remain justified; narrow the use or repair the correspondence if a required distinction is lost. A numerical R penalty requires the receiving model under C.2.2/B.3.

C.3.3:9 - Worked Examples (informative)

C.3.3:9.1 - Vehicle → TransportUnit (manufacturing)

Source kinds Vehicle and PassengerCar, target kinds TransportUnit and PassengerTransportUnit, and their declaration editions are independently identified. One KindBridge relation obtains from Vehicle to TransportUnit and another from PassengerCar to PassengerTransportUnit under the pinned scheme editions.

The bridge assertion states that source fact SubkindOfObtains(PassengerCar, Vehicle; sourceRS) is preserved by target fact SubkindOfObtains(PassengerTransportUnit, TransportUnit; targetRS), while the EV distinction is collapsed; it records CL^k=2, the lost battery-health invariants, and definedness limited to registryAPI v1.4 in the selected time window.

A candidate is first checked for admissibility and, if admissible, then classified by the receiving declaration; source classification is not copied. If the receiving claim also relies on an independently established scope translation, that relation’s consequence remains separate from the kind-bridge consequence; the kind-bridge consequence leaves F and G unchanged.

C.3.3:9.2 - Same AuthenticatedRequest kind across services — no bridge

Frontend and gateway services use the same AuthenticatedRequest kind: the candidate request domain, signature-validity condition, and intended member/non-member distinction are aligned. Each service uses its selected declaration edition and evaluates the request afresh. The gateway spelling x-auth may require a C.3.4 vocabulary binding when that wording use is relied on; an F.9 sense relation is added only if that use also needs a relation between distinct local senses. The service boundary and spelling alone create neither another kind nor a KindBridge.

C.3.3:9.3 - AdultPatient across jurisdictions (clinical)

The obtaining bridge relates source kind AdultPatient to independently identified target kind AdultPerson_Y. Its assertion gives CL^k=1, states the 18-versus-21 boundary loss, and limits definedness to the declared jurisdictional editions. The target classification uses its own signature edition. For an admissible candidate, missing DOB support yields unknown. That result and a separate guard refusal can suffice for the present decision. If later classification is needed, obtain the required birth-date support; a claim restricted to an independently supported subset is another possible use. Neither narrowing the claim nor applying a justified R consequence turns the candidate’s unknown classification into a true one.

C.3.3:10 - Anti‑patterns & Remedies (informative)

Anti‑patternWhy it’s wrongRemedy
One interoperability score, or mandatory scope-plus-kind bridgesBlurs independent channels and invents unused relationsOpen only the Scope, kind, and sense relations consumed by the receiving use; keep their losses and R consequences separate
Claiming preserved ⊑ while inverting orderMakes typed reasoning unsoundMark as not preserved; add loss note; consider adapter or subkind redesign
Hiding collapsesOverstates coverageState the collapsed subkinds and their consequence for the receiving use; apply only a justified R consequence.
Implicit latest mappingNon-deterministic and non-auditablePin both scheme editions and the mapping-rule edition in the bridge assertion; outside bridge definedness decline that bridge use without changing an independently obtained receiving result.
Using KindBridge to widen GConflates kind correspondence with claim-scope translationKeep Scope edits in USM (ΔG±); KindBridge never widens Scope
Adjusting F/G for poor CL^kViolates F–G–R & USM separationRoute consequences to R only; consider narrowing Scope or adding adapters

C.3.3:11 - Conformance Checklist

IDRequirement
KB-01A locality or scheme change first triggers kind-definition comparison. A bridge has ordered, independently identified distinct kind participants and an obtaining directional correspondence predicate.
KB-02A KindBridge maps neither Scope nor sense; add A.2.6 when the receiving use needs a scope relation, and F.9 when it needs a sense relation.
KB-03Participants, distinctness, direction, predicate, applicability, definedness, and participant-determined identity are recoverable. Scheme/signature/assertion/card/publication editions qualify interpretation or reliance but do not reidentify the occurrence.
KB-04Receiving classification checks admissibility before a fresh three-valued judgment. Source truth is never copied; bridge refusal does not rewrite the receiving result.
KB-05An order-preservation assertion names the source and target subkind facts and establishes identity or a directional bridge at each endpoint.
KB-06Inversion is non-preservation with loss; unsettled order remains unknown.
KB-07Collapse designates affected source order facts and lost distinctions without rewriting either kind order.
KB-08CL^k is an assessment in the bridge assertion and does not alter kind identity, formality, scope, or abstraction facet.
KB-09Reliance applies only justified CL^k consequences to R; admissibility, F, G, and classification truth stay unchanged.
KB-10A comparable-link minimum remains a link summary; a claim about composed correspondence establishes joint definedness and preservation of the distinctions required by the receiving use, keeping occurrences and assertions distinct.
KB-11Loss notes state non-preserved criteria or subkind facts and do not change either kind.
KB-12Definedness is explicit; outside it the guard declines that bridge use while independent receiving classification keeps its own result.

C.3.3:End

Referenced in the corpus

86 literal mentions in other sections. Read their context to establish the relation.