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:
- Ordinary designation inside one semantic bounded context. If both expressions resolve to the same
<ReferenceScheme, LocalSenseClaim>projection, keep ordinary designation and stop; use F.18 only when a durable name is needed. When only the admitted extent of that claim changes, apply A.2.6widen,narrow, orrefit. No F.9 Bridge is current. - Lane or reference-plane repair. If the sentence confuses Object, Description, Carrier, or
CHR:ReferencePlane, restore the kinds under A.7 or the governing plane rule. - Identification or indexing. If the sentence means same id, key, code, or index target, apply the identification or indexing rule. Use A.6.6 when the relation or its participants remain hidden. Identifier equality does not establish meaning correspondence.
- Scope operation. A.2.6 is the pattern for
widen,narrow,refit, andtranslateover scope values; when the sentence concerns claim extent, recover theU.ClaimScope.translatemay consume an independently obtaining F.9 Bridge and a separate affirmative claim for that direction, rule, and tolerance; it is neither representation Work nor a structure crossing. - Other locality hidden by context wording. Route interpretation to the effective interpretation rules (
ReferenceScheme); claim extent toU.ClaimScope; empirical grounding to oneEpistemeEmpiricalGroundingRelation; time to the qualification window required by the temporal predicate; a deliberately asserted actual composite project Work to A.13, independent A.15.1 admission and A.15.6; viewpoint use to the E.17.0 viewpoint relation and oneU.ViewpointRefresolving 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. - 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, and supported use with its material limits. Add a source-return condition when a limitation, representation feature, misunderstanding or risk makes return necessary for that use, and name its destination. When a dependency across interpretation rules or another use makes claim identity material, independently constitute source episteme
Xand receiving epistemeY, requireEntityOfConcern(X)=EntityOfConcern(Y)exactly, and statev : X -> Ywith the relation between the endpoint interpretation rules, preservation, loss, and prohibited strengthening. AssertRepresentationTransitionRelation@Contextonly when every six-participant obtaining condition and actual dated representation-transformation Work are present; performed Work alone neither provesvnor makes that relation obtain. A Bridge supplies neithervnor the Work and makes no transition occurrence obtain. - Structure comparison or crossing. Identify the structures and what the comparison must establish under their direct rules; use A.22 for
U.Structureidentity. Apply §4.8 only when the receiving question depends on the organization of actual subject crossings among several independently identifiedBoundedModelUseStructurevalues. A SenseCell Bridge, label, diagram, shared participant, or reference alone supplies neither structure selection nor a crossing. For a required crossing without a direct governor, return the A.6.RCD missing-governor stop. - Cross-local semantic relation. Resolve two F.17
SchemeSenseCellvalues 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. - Proposed use of an obtaining Bridge. In a second sentence, name action
u, directiond, use-specific ruler, tolerated losst, 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. - Explanation or unresolved proposal. Say plainly what remains unestablished. A candidate or negative card carries no positive occurrence reference.
- 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 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 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 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 applicability or as-of basis.
Before testing a Bridge, check ontological strata. C.3.3 establishes only the 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, A.13 and independent A.15.1 admission for actual Work, with F.6 only for precise assignment-bound 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:
- Bridge occurrence. The direct relation has exactly two F.17 cell participants and obtains under one F.9 profile.
- 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.
- Bounded-use claim. An ordinary C.2.1 claim says whether the 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. - Optional Bridge Card. It packages claims and evidence when durable reuse pays. It neither creates the relation nor grants the use.
- 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 independently established relation cited by the A.10 path, the 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 - 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.
| Item | When required | Meaning and stop |
|---|---|---|
SourceSenseCellRef, ReceivingSenseCellRef | every Bridge candidate | F.17 addresses; unresolved endpoints stop the semantic branch. |
| semantic-context projections | every Bridge candidate | Derived <ReferenceScheme, LocalSenseClaim> pairs; they must differ for F.9. |
BridgePredicateProfile | every Bridge candidate | By-value relation semantics only; a label or id is insufficient. |
BridgeKind and relation orientation | profile and readable explanation | What semantic correspondence or difference is claimed; not a use licence. |
applicability / Γ_time, truth condition, dependencies | profile | When and how the direct predicate is tested; missing dependencies stop without inventing an occurrence. |
action u | every proposed use | What the reader proposes to compare, substitute, translate, publish, or otherwise do. |
direction d | every proposed use | Use-source to use-receiving order; relation symmetry supplies no direction by implication. |
rule r | every proposed use | The correspondence rule the action will follow. |
tolerance t | every proposed use | Which semantic loss is acceptable for this action; observed loss remains evidence. |
| polarity and effective ReferenceScheme | every bounded-use claim | Whether the claim is affirmative or negative and how its designations are interpreted. |
| A.10 or B.3 branch | when someone will rely on the claim | The descriptive A.10 path, the independently established direct relations it cites, and local disposition, or the B.3 claim or explicit disposition selected by its assurance trigger. |
| permission result | only when permission is required | Cite the A.2.8.PER result the use needs: an obtaining strong grant, weak non-prohibition finding, exercise relation, or conflict result. Policy and predicates supply grounds; they are not that result. |
| receiving-object ref | only when the use is said to have happened | Work, assertion, publication, relation, application, or other object under its subject pattern. |
ClaimMode and card EntityOfConcern | only when a card pays | Actual card concerns the obtaining Bridge; candidate or negative card concerns the admitted F.9 Bridge relation kind and carries proposed endpoints and profile in its ClaimGraph. |
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
State the F.9 kind warranted by the correspondence or difference at issue: 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-overlapcan support an affirmative label-use claim when its rule preserves the named differences; the Bridge does not grant that use automatically.Disjointcan support a contrastive explanation. A substitution that requires shared meaning receives negative polarity; other proposed uses still need their own rule and tolerance.Equivalenceis symmetric, butA -> BandB -> Aare different use claims.Narrower-thanandBroader-thanorient 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.- For a broader-to-narrower use, establish the target conditions required by that use. This may require fresh classification, a bounded use restricted to qualifying cases, or refined cells with a separately tested Bridge. Merely changing a profile cannot make an unsupported use safe.
- Type-structure reuse requires a separate claim naming the structural rule and loss tolerance. Matched invariants can support that claim; no
CLnumber 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:
- when an endpoint changes, identify the new source or receiving cell;
- replace the Bridge profile when its relation-semantic content changes;
- revise the bounded-use claim when
u,d,r,t, effective scheme, or polarity changes; - retest the fixed Bridge predicate when endpoint facts or dependencies change;
- reassess reliance when evidence, currentness, a direct relation cited by the A.10 path, the local
RelianceDisposition, or a B.3 claim, record, or disposition changes; - revise the Bridge Card when its package content changes;
- when reporting a publication occurrence, identify the published Bridge Card edition; and
- identify the actual receiving object 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
When normative or decision-carrying wording leaves its meaning unresolved, expose the action and any necessary stop:
| Intended meaning | Plain action | Follow-through |
|---|---|---|
| ordinary same-context designation | “Both expressions designate this local sense.” | Make the common interpretation recoverable; use F.18 only for durable naming. No Bridge is needed. |
| cross-family semantic interpretation | “Use A to explain B by rule R.” | Test the cross-family Bridge and the separate explanation-use claim. State a non-use restriction only when its independently grounded contrast changes this use. |
| naming convenience | “Use the label ‘actor’ in this comparison; keep account and customer eligibility distinct.” | Obtaining Bridge plus a C.2.1 claim naming direction, label rule, and zero tolerance for eligibility transfer. |
| directional substitution | “For calculation X, read A as B by rule R within tolerance T.” | Obtaining Bridge, affirmative claim for <X,A->B,R,T>, and current A.10 or B.3 reliance. A proposed reverse use requires its own claim. |
| type-structure reuse | “Reuse this subtype row only while invariants I remain true and loss stays within T.” | Obtaining Bridge plus a separately warranted structural-use claim. |
| contrast | “These senses differ in this stated way.” | An obtaining Disjoint or Partial-overlap Bridge can support the contrast. Judge any proposed substitution separately under its rule and tolerance; contrast alone supplies no blanket prohibition. |
| unresolved proposal | “The mapping is available, but the semantic relation is not established.” | Candidate card or plain stop naming the missing endpoint, predicate fact, or dependency. |
Keep clear same, align or map wording, including in technical prose. Add a non-inference only when the rejected reading has independent local grounds, a plausible intended reader could take it here, and the distinction changes truth, understanding or action. Use the smallest sufficient correction under F.19:4.
A.6.9:4.5 - Disambiguation guide
| Trigger | First question | Default route | Stop |
|---|---|---|---|
| “A is the same as B” | Same local sense or relation between distinct senses? | designation first; otherwise test the F.9 relation at issue | no cells or predicate -> explanatory only |
| “Align A and B” | Shared label, comparison, substitution, or structure use? | name the proposed action; test F.9 only if a semantic-correspondence claim remains | mapping score alone establishes neither relation nor use |
| “Map A to B” | Semantic reading or operational transformation? | operational only: use its defining operation rule, with Work only when performance is claimed; semantic as well: keep code or ETL as potential evidence and test F.9 | code direction is not use suitability |
| “Same ID/key/one-to-one” | What is equal or one-to-one: identifiers, index targets, a mapping, or local senses? | apply that relation’s rule; use A.6.6 when its relation or participants are hidden, and F.9 only for a remaining cross-local semantic claim | collision-free ids do not establish sense identity |
| “B is a view/projection of A” | View membership, representation, or sense reuse? | E.17.0 for View membership; the applicable representation pattern for construction; C.29 for an unresolved mathematical-lens choice, correspondence, or transfer question | dropped constraints block stronger use claims |
| “Equivalent” | Which local senses and relation predicate; if a use is proposed, what action, direction, rule, and tolerance? | test the claimed relation directly; assess another F.9 kind when the receiving question needs it | symmetry alone grants no use |
A.6.9:4.6 - Mapping witnesses are not Bridges
A lookup table, aligner model, transformation function, API or ETL step may implement or represent a mapping. Its content may express claims or supply grounds for a Bridge or a bounded-use judgment; its mere presence or successful execution does not establish either. Code may run A → B while the semantic relation is symmetric, oriented the other way or absent. Even an obtaining Bridge needs a separate judgment for the operation’s rule and tolerated loss.
Assess a mapping witness’s content and grounds against the F.9 predicate. Recover an A.10 account when provenance, currentness or reliance must remain replayable; use a Card when reusable packaging is warranted. 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 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 interpretation rules (
ReferenceScheme); A.2.6 is the pattern forU.ClaimScope,widen,narrow,refit, andtranslate. A.2.6 translation may consume a 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 temporal or subject predicate and assertion. F.9 profile applicability or
Γ_timedoes not become a generic context or time participant for another claim. - Project wording: keep an ordinary project label or plan under its own meaning. When an actual composite project Work is deliberately asserted, use A.13, independent A.15.1 admission, and A.15.6 with work parthood. A label, plan or Bridge alone establishes no such occurrence.
- Viewpoint: E.17.0 governs the direct
EpistemeViewpointConformanceRelation; oneU.ViewpointRefresolves 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 governs conformance-dependent View membership and E.24.PUB publication occurrence/form/carrier. Apply the direct representation rule; use C.29 for an unresolved mathematical-lens choice, correspondence, or transfer question. A.6.3.RT starts an ordinary same-concern representation move with content to survive, source comparison, material loss and supported use. Add a source-return condition and destination when return is needed for that use. Its triggered construction independently identifies
X,Y, andv; actual representation-transformation Work is required only for the six-participant occurrence. - Kinds and classifications: C.3.3 establishes the
KindBridgebetween source and target local kinds. C.3.2 separately judges the candidate under the target kind, targetKindSignatureedition, and target slice; the result may betrue,false, orunknown. F.9 supplies only local-sense correspondence needed by that use. - Structures: identify the structures under their defining rules and use A.22 for
U.Structureidentity. Ordinary comparison uses the criterion needed by the receiving question. When §4.8’s crossing-organization question is current, A.1.1/A.22 independently establish each participatingBoundedModelUseStructure; the conditional cross-structure rule additionally requires governed crossings and all four structure discriminators. A SenseCell Bridge cannot substitute for that architecture. - Direct subject relations, Work, and system-role claims: a world-side relation obtains under its own predicate and participant conditions, independently of whether an assertion describes it. A.2.1 governs assignment. Actual Work requires A.13 and independent A.15.1 admission; F.6 applies only for precise assignment-bound attribution, and A.15.6 for the separately claimed composite Work. A semantic relation or use claim establishes none of those occurrences by itself.
- Permission: apply A.2.8.PER and cite the 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 model episteme, its admitted model-use holons, the obtaining applicability, actual-use, and fixed-content model-expression-coherence occurrences, the 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 obtaining subject-crossing occurrence selected for the proposed organization. For each one, name its 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 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 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 independently selected BoundedModelUseStructure values; the selected relation organization as the obtaining crossing occurrences; the applied constraints and invariants; and the use frame as the question, admissible action and necessary use boundary. Those are the four A.22 discriminators. Include an explanatory forbidden reading only under the F.19:4 guard test. 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.
A selected structure can be described by its four discriminators without inventing a dated selection Work. If the claim concerns an actual selection judgment, identify that judgment and result under its own rule; preserve a C.2.1 result episteme with the structure as EntityOfConcern when persistence is needed. If a particular dated selection Work is deliberately asserted, establish its A.13 basis and independent A.15.1 admission, with F.6 only for precise assignment-bound attribution; identify the system, Method and participation or A.6.1 bindings required by that Work claim. An accountable decision additionally needs its own decision rule. These objects remain separate from the structure’s four discriminators; every selected crossing still needs its direct governor.