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 exact 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 exact 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; a mask adapter or narrower Scope may support a later use, while the guard’s refusal and R penalty remain separate from target truth.