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.