A.6.9:4 - Solution

Treat an umbrella sameness sentence as a dispatch trigger, not as an automatic Bridge and not as a demand for a card. Recover the concrete subject and action first. Then choose the smallest truthful branch:

1. Ordinary designation inside one semantic bounded context. If both expressions resolve to the same exact <ReferenceScheme, LocalSenseClaim> projection, use the ordinary naming pattern and stop. When only the admitted extent of that claim changes, apply A.2.6 widen, narrow, or refit. No F.9 Bridge is current.
2. Lane or reference-plane repair. If the sentence confuses Object, Description, Carrier, or CHR:ReferencePlane, restore the exact kinds under A.7 or the governing plane rule.
3. Identification or indexing. If the sentence means same id, key, code, or index target, use A.6.6. Identifier equality does not establish meaning correspondence.
4. Scope operation. A.2.6 is the pattern for widen, narrow, refit, and translate over exact scope values; when the sentence concerns claim extent, recover the exact U.ClaimScope. translate may consume an independently obtaining F.9 Bridge and a separate affirmative claim for that exact direction, rule, and tolerance; it is neither representation Work nor a structure crossing.
5. Other locality hidden by context wording. Route interpretation to the effective U.ReferenceScheme; claim extent to U.ClaimScope; empirical grounding to one exact EpistemeEmpiricalGroundingRelation; time to the qualification window required by the temporal predicate; project wording to an exact composite U.Work under A.15.6; viewpoint use to the E.17.0 viewpoint relation and one U.ViewpointRef resolving exact P; and any world-side subject claim to the pattern that defines its relation predicate and obtaining condition. A bare context word supplies none of these governed objects or claims.
6. Representation transition. A representation change is not a Bridge. For ordinary A.6.3.RT use, name the same concern, content to survive, target representation, source comparison, admissible use boundary, and source-return trigger and destination. When cross-scheme dependency or reliance makes exact claim identity material, independently constitute source episteme X and receiving episteme Y, require EntityOfConcern(X)=EntityOfConcern(Y) exactly, and state exact v : X -> Y with scheme relation, preservation, loss, and prohibited strengthening. Assert RepresentationSchemeTransitionRelation@Context only when every six-participant obtaining condition and actual dated representation-transformation Work are present; performed Work alone neither proves v nor makes that relation obtain. A Bridge supplies neither v nor the Work and makes no transition occurrence obtain.
7. Structure comparison or crossing. Recover each exact BoundedModelUseStructure independently, then apply the conditional A.22 cross-structure rule in §4.8 only if exact governed subject crossings and a named receiving use remain. A SenseCell Bridge, label, diagram, shared participant, or reference supplies neither structure selection nor crossing; without an exact direct crossing governor, return the A.6.RCD missing-governor stop.
8. Cross-local semantic relation. Resolve two exact F.17 SchemeSenseCell values from different semantic bounded contexts, declare the F.9 relation-semantic profile, and cite a Bridge only when its predicate obtains. Scheme difference, same spelling, a mapping witness, or two endpoint references alone establishes no Bridge.
9. Proposed use of an obtaining Bridge. In a second sentence, name action u, direction d, use-specific rule r, tolerated loss t, and claim polarity under C.2.1. When someone will rely on that claim, recover A.10 or B.3 reliance for the same use.
10. Explanation or unresolved proposal. Say plainly what remains unestablished. A candidate or negative card carries no positive occurrence reference.
11. Claim that the use happened. Name the actual receiving object and use the rule that defines the claim about that object; the use position inside the C.2.1 claim is not that object.

For A.6.9, semantic bounded context is a Plain practice name for the local interpretation basis recovered from one exact cell’s <ReferenceScheme, LocalSenseClaim> projection. It supplies only that interpretation basis; each receiving object or relation remains governed by the applicable branch above. Representation transition, A.2.6 scope translation, F.9 local-sense Bridge, and direct structure crossing remain four independently governed moves.

A.6.9:4.0 - Trigger and endpoint recovery

Open the dispatch when same, identical, equivalent, align, map, match, correspond, treat as, reuse, share, unify, canonical source, synced, normalized, one-to-one, same ID, or mirrors could hide the current object or action. Apply equivalent triggers in any language.

If the dispatch leaves a semantic-correspondence question, resolve the local senses before deciding whether a Bridge is current. A shared semantic-context projection still exits through ordinary designation. Each candidate endpoint reference must be a SenseCellAddressRef resolving one exact F.17 SchemeSenseCell. Keep the cell distinct from each C.2.1 description episteme about it, each F.18 designator, and each address reference. A reference resolves the cell, a designator names it, and a description claims something about it; only the cell fills the Bridge endpoint. A string, system, table, class name, file, context label, card, or identifier may be the source expression or a neighboring evidence object from which that cell is recovered. If a token is metonymic — the system, the model, the service, that table — test only governed referents that a plausible intended reader could recover from the local span, then recover the intended local expression and claim. If either endpoint remains unresolved, keep the sentence explanatory and return unresolved SenseCell endpoint.

Pin the endpoint reference-scheme and local-sense-claim editions, or an exact as-of basis, when the correspondence can change with a canon or model edition. Γ_time may be used as a compact card label for that basis. It is not a participant. It contributes to profile identity only when it states the profile’s exact applicability or as-of basis.

Before testing a Bridge, check ontological strata. C.3.3 establishes only the exact KindBridge between source and target local kinds. C.3.2 makes a fresh target classification judgment under the target KindSignature edition and slice. Use the pattern that defines the measurement claim for value normalization, A.2.1 for system-role assignment, F.6 for performed-Work attribution, E.24.PUB for publication occurrence, form, and carrier, and A.6.3.RT for representation transition. F.9 can supply a semantic premise needed by one of those claims; each neighboring claim obtains only under its named subject pattern.

A.6.9:4.1 - Stable lens: relation, use claim, reliance, and receiving object

Keep these objects distinct:

1. Bridge occurrence. The direct relation has exactly two F.17 cell participants and obtains under one exact F.9 profile.
2. BridgePredicateProfile. It contains only Bridge kind, kind-defined symmetry or orientation, endpoint-sense readings, relation-specific correspondence or difference condition, applicability and as-of basis, Boolean truth condition, and stop dependencies.
3. Bounded-use claim. An ordinary C.2.1 claim says whether the exact obtaining Bridge is suitable for <u,d,r,t>. Its EntityOfConcern is the Bridge; its ClaimGraph designates the use, direction, rule, tolerance, and polarity; its effective scheme interprets them.
4. Optional Bridge Card. It packages claims and evidence when durable reuse pays. It neither creates the relation nor grants the use.
5. Separately governed receiving object. If the use happened, its Work, assertion, publication, direct relation, operation application, or other object keeps its own participants, obtaining or performance condition, and identity.

Bridge(SourceSenseCell, ReceivingSenseCell; BridgePredicateProfile)

Use that notation only after the F.9 predicate passes. For a proposal, write candidate Bridge(...) or use a candidate card with no positive occurrence reference.

Changing u, d, r, or t changes the bounded-use claim, not the Bridge. Changing evidence, an A.10 relation or local RelianceDisposition, or a B.3 claim, record, or disposition reopens reliance without reidentifying the Bridge or the bounded-use claim. A changed endpoint or relation-semantic profile identifies another Bridge candidate.

A.6.9:4.2 - Explicit claim skeleton

Use this table for the semantic branch. The action, direction, rule, and tolerance rows apply only to a proposed use of an obtaining Bridge.

Only the two endpoint cells fill the direct relation’s participant slots. Use content is ClaimGraph content, not another relation participant or profile component.

A.6.9:4.3 - Judgement and change

Choose the least-committing truthful Bridge kind: Equivalence, Narrower-than, Broader-than, Partial-overlap, Disjoint, or one declared cross-family relation kind. The kind settles relation semantics only.

If a Bridge obtains and a use is proposed, judge that use separately:

• Partial-overlap can support an affirmative label-use claim when its exact rule preserves the named differences; the Bridge does not grant that use automatically.
• Disjoint can support a contrastive explanation; a proposed substitution receives negative polarity.
• Equivalence is symmetric, but A -> B and B -> A are different use claims.
• Narrower-than and Broader-than orient the semantic relation. Narrower-to-broader is usually easier to warrant, but every use direction still needs its own rule, tolerance, and polarity; recover reliance when someone will rely on that claim.
• A broader-to-narrower proposal normally requires refined cells and a separately tested Bridge. Another profile over the same broad endpoints cannot make an unsafe use safe by declaration.
• Type-structure reuse requires a separate claim naming the structural rule and loss tolerance. Matched invariants can support that claim; no CL number grants it.

CL may remain optional evidence shorthand: 0 contradicted, 1 weakly comparable, 2 bounded support with counterexamples, 3 matched stated invariants with no current material counterexample. It is neither profile identity nor a suitability threshold.

Narrate changes by the object that changed:

1. retargetEndpoint for another source or receiving cell;
2. replaceBridgeProfile for changed relation-semantic content;
3. reviseBoundedUseClaim for changed u, d, r, t, effective scheme, or polarity;
4. retestObtaining for changed endpoint facts or dependencies under the fixed profile;
5. reopenReliance for changed evidence, currentness, A.10 relation or disposition, or B.3 claim, record, or disposition;
6. reviseBridgeCard for changed package content;
7. publishBridgeCardEdition for a publication occurrence; and
8. recoverReceivingObject when the use is claimed to have happened.

An inverse asymmetric relation and any direct A-to-C relation require their own profiles and tests. Two chained Bridges do not entail a third.

A.6.9:4.4 - Lexical guardrails

In normative or decision-carrying prose, replace the umbrella word with a sentence that exposes the action and stop:

Plain teaching prose may retain same, align, or map when the local sentence tells the reader what to do and what result would reopen the claim. Add a non-inference only when a plausible intended reader could otherwise overread the sentence and the guard changes understanding or action.

A.6.9:4.5 - Disambiguation guide

A.6.9:4.6 - Mapping witnesses are not Bridges

A lookup table, aligner model, transformation function, API, or ETL step is an implementation or evidence object. It may support the claim that a Bridge obtains or that one bounded use is suitable. It does not determine either claim by itself. Code may run A -> B while the semantic Bridge is symmetric, oriented the other way, or absent; and even an obtaining Bridge may be unsuitable for that operation’s rule or tolerance.

When the mapping witness is used to support a semantic-correspondence claim, keep it in the A.10 evidence path or optional card. Test the F.9 predicate; if a Bridge obtains and a use is proposed, state the C.2.1 bounded-use claim and recover reliance when someone will rely on that claim.

A.6.9:4.7 - Coordination boundaries

• Naming and endpoint objects: F.18 selects designators; F.17 governs exact scheme-based cells and rows. A SchemeSenseCell, C.2.1 description episteme, designator, and resolving reference remain distinct; none creates a Bridge.
• Reference scheme and scope: C.2.1 is the pattern for the effective U.ReferenceScheme; A.2.6 is the pattern for U.ClaimScope, widen, narrow, refit, and translate. A.2.6 translation may consume an exact Bridge plus its affirmative bounded-use claim but is not representation Work or structure crossing.
• Grounding: C.2.1 alone supplies an EpistemeEmpiricalGroundingRelation. Its grounding holon is the participant against which covered empirical claims are grounded; it is not assumed identical to the episteme’s EntityOfConcern.
• Time: the qualification window is part of the exact temporal or subject predicate and assertion. F.9 profile applicability or Γ_time does not become a generic context or time participant for another claim.
• Project wording: A.15.6 recovers an actual project as one exact composite U.Work after A.15.1 admission and exact work parthood. Project label, plan, situation word, or Bridge supplies no project identity.
• Viewpoint: E.17.0 governs the direct EpistemeViewpointConformanceRelation; one U.ViewpointRef resolves exact viewpoint episteme P. The viewpoint, its reference, candidate/View episteme, and evaluator remain distinct.
• Evidence and assurance: A.10 is the pattern for evidence provenance and local reliance; B.3 is the pattern for assurance claims, records, and explicit dispositions.
• Representations and publications: E.17.0 is the pattern for conformance-dependent View membership, E.24.PUB is the pattern for publication occurrence/form/carrier, and C.29 is the pattern for mathematical-representation objects. A.6.3.RT starts an ordinary same-concern representation move with content to survive, source comparison, loss, admissible use, and the source-return trigger and destination; its triggered exact construction independently identifies X, Y, and v; actual representation-transformation Work is required only for the six-participant occurrence.
• Kinds and classifications: C.3.3 establishes the exact KindBridge between source and target local kinds. C.3.2 separately judges the candidate under the target kind, target KindSignature edition, and target slice; the result may be true, false, or unknown. F.9 supplies only local-sense correspondence needed by that use.
• Structures: A.1.1/A.22 independently select each exact BoundedModelUseStructure; §4.8 applies the descriptive A.22 conditional cross-structure rule only after exact governed crossings and all four structure discriminators are recoverable. A SenseCell Bridge cannot substitute for that architecture.
• Direct subject relations, Work, and system-role claims: every world-side relation has its own exact predicate, participant bindings, and assertion. A.2.1, F.6, A.15.1, and A.15.6 define assignment and exact performed or composite Work predicates; semantic relation, context wording, and use claim have no enactment effect.
• Permission: apply A.2.8.PER and cite the exact result the proposed use needs—an obtaining strong grant, weak non-prohibition finding, exercise relation, or conflict result. Policy and direct predicates supply conditions or grounds but are not the permission result. Any required authority relation remains separate.

A.6.9:4.8 - Structure comparison and conditional cross-structure selection

Use this branch only when the receiving question depends on the organization of actual subject crossings among several bounded model-use structures. First recover every participating BoundedModelUseStructure independently under A.1.1/A.22: one exact model episteme, its admitted model-use holons, the exact obtaining applicability, actual-use, and fixed-content model-expression-coherence occurrences, the exact applied constraint claims, and one named bounded-model-use frame. A shared system, model, episteme, scope, or other participant does not merge two selected structures and proves neither overlap nor parthood.

Next enumerate every actually obtaining subject-crossing occurrence selected for the proposed organization. For each one, name its exact participants, relation kind and predicate, direction when asymmetric, applicability, obtaining result, occurrence identity, and recurrence rule, and test them against the pattern that defines those relation rules. An F.9 Bridge relates exact local senses only. Context labels, edge labels, Cards, registry rows, references, Views, diagrams, and common participants may help locate the proposed crossing’s objects or evidence; only an occurrence satisfying its direct governor establishes that crossing. If no current pattern defines a required crossing, stop through A.6.RCD at the exact missing-governor question; do not replace it with a vague edge family.

Only then apply A.22’s conditional cross-structure rule for one named receiving or crossing-analysis use. Declare the substrate as the exact independently selected BoundedModelUseStructure values; the selected relation organization as the exact obtaining crossing occurrences; the exact applied constraints and invariants; and the use frame as the question, admissible action, and forbidden overread. Those are the four A.22 discriminators. The A.22-local label CrossContextRelationStructure serves only as a retrieval aid under that rule; A.6.9 gives it no public-vocabulary use. The resulting U.Structure is the dependent organization identified by those four discriminators. Container or holon identity, context grouping, and the crossing occurrences remain governed separately. Any U.View, Context Map, diagram, Card, or publication that depicts, packages, or carries the organization retains its own identity and relation to it.

When a load-bearing claim says that this organization was selected, separately name the selecting system, exact Method, dated selection U.Work, and direct participation relations or A.6.1 bindings. Name the exact selection judgment and its result: when persistence is needed, a C.2.1 result episteme whose exact EntityOfConcern is the selected structure; when an accountable choice is claimed, the exact decision and its direct decision governor. A generic result reference, the dated selection Work, and visible mapping artifacts may designate or warrant the selection claim only through the named relations. They remain outside the structure’s four discriminators, and every crossing still obtains only under its direct governor.