E.18.3:4.1 - Connections to independently identified neighboring values

E.18.3 mints no universal neighboring-value relation. A neighboring Method, plan, Work, evidence, assurance, gate, decision, architecture, narrative, publication, evaluation, or currentness value must be independently identified. A claim about its kind, current status, or use obtains only when current facts or evidence satisfy the criterion supplied by the applicable definition, constraint, predicate, test, evidence rule, or assurance rule. A Method contributes its reusable way of doing and applicability or bounds; a MethodDescription may state that content, but any truth, result, evidence, assurance, or Work claim about using it still needs its separate applicable rule and current basis. A positive connection exists only through an exact already-obtaining relation. A stronger neighboring claim states its concrete contribution in ordinary content-bearing language; an exact content identity is added only when that identity changes the selected use.

Use this display row when a reader must recover the connection:

neighboringValueUseRow:
  admittedCGUSLocusBindingRef: CGUSLocusBinding already mapped by this E.18.3-qualified structure
  neighboringValueKindRef
  neighboringValueRef
  connectionQuestion: exact stated question
  exactSupportingRelationOccurrenceRef
  supportingRelationReferenceEpistemeRef?: ordinary C.2.1 episteme from 4.0a
  connectionRationaleClaimRef
  exactStrongerUseClaimOrRelationRef?: only when a separately governed stronger use is current
  concreteContribution?: ordinary content-bearing statement of what the neighboring content contributes; never a bare category label
  relevantPatternRef?: only when it locates that content

connectionQuestion is one exact free-text question, not a code, kind, relation, or closed question-type set. Non-exhaustive examples include questions about basis dependency, a result, a governing constraint, or a comparison. A basis-dependency question creates no obligation. A result question is positive only after the exact result entity or relation and what it is a result of or for are recovered. A governing-constraint question needs the exact current constraint claim or occurrence. A comparison question needs its comparator, participants, scope and exact comparison definition or test; juxtaposition supplies none. Every stated question still requires an exact supporting relation. Direction, participant order, applicability, occurrence identity, dependence and currentness come from its predicate definition, exact declaration when replay needs it, and current facts, not from the question wording.

When a stronger neighboring use is current, exactStrongerUseClaimOrRelationRef points to the independently governed claim or relation that establishes it; no broad use category substitutes for that ref. concreteContribution then says what the neighboring content actually does—for example, defines a term, constrains a claim, supplies a predicate or test, describes a Method’s way of doing, or supplies an evidence or assurance rule. Those are non-exhaustive verbs, not field values; definition, test, or method alone cannot fill the field. relevantPatternRef is only a locator. An exact claim-bearing episteme, ClaimGraph, edition, or other content ref is required only when that identity changes the selected stronger use. None of these fields creates a relation.

An ordinary stop uses stopCondition; reconsideration uses reconsiderationConditions[] to name the condition claim, affected structure and next question, with relevantPatternRef only when cited content supplies a needed contribution. Neither creates a receiver or connection relation. If the supporting relation is missing, keep the neighboring values separate and record the attempted question. Use the A.6.RCD missing-governor result only when no applicable rule can state or test the claim for the exact participants and question; otherwise distinguish missing facts or bindings (missing-information) from a positive test that fails on a sufficient case basis (factually unsupported). A failed positive test alone does not establish the negative. Recommendation, intended realization, rationale text, common EntityOfConcern and graph adjacency are not substitutes.