G.8:5.3 - G.8:Ext.BridgeReuseWiring
PatternScopeId: G.8:Ext.BridgeReuseWiring
GPatternExtensionId: BridgeReuseWiring
GPatternExtensionKind: InteropSpecific
GoverningPatternId: G.7
Uses: {G.7, F.9, A.10, B.3}
⊑/⊑⁺: ∅
RequiredPins/EditionPins/PolicyPins (minimum; conditional on the stated use):
BridgeId/BridgeCardId(the obtaining Bridge used; aBridgeCardIdis needed only when that Card is relied on)CL/CL^k/CL^plane(when cited; the applicable values are mandatory when required by theG.7calibration or namedB.3assurance account)Φ/Ψ/Φ_plane policy-ids(only the policy ids and editions required by the actualG.7calibration or namedB.3assurance account; reference‑only and resolvable perF.8:8.1)BridgeCalibrationTableId?,RegressionSetId?(both required when calibration evidence is cited, together with the row locator and active policy pins required byG.7CC‑G7‑SCRLinkage‑1)
RSCRTriggerSetIds: {GCoreTriggerSetId.BridgeCalibrationKit} (only if the bundle/ledger explicitly binds calibration records by id)
Notes (wiring‑only):
- Present when
SoS-LOGBundle@Contextuses an F.9 sense correspondence. A combined kind or plane use retains its separate relation and receiving conditions under G.Core:4.2.3. - The wiring MUST keep the obtaining Bridge reference, the separate bounded-use claim (use, direction, rule, and tolerated loss), and the
A.10reliance basis citable. A separate named assurance use also cites its exact target claim, receiving use, andB.3assurance basis/result. Required CL values, policy editions, and evidence remain mandatory for that account; any numerical assurance penalty satisfies the model applicability and declared-result conditions ofCC‑GCORE‑PEN‑1. Ordinary supported reuse does not require a CL shorthand, calibration record, loss-policy id, or assurance claim merely to fill the package.